u/Equivalent-Market-87

just launched ReadnType, basically a reading + typing gym

building it was honestly easier than figuring out distribution lol

for people who've done this before, where did your first real users come from? reddit, discord, x, communities, cold outreach?

trying to avoid just spamming links everywhere and actually find people who'd care

i started building a monkeytype-ish app but wanted reading to be just as important as typing and it kinda got out of hand

there are 3 main modes

type is basically the normal monkeytype style thing with wpm raw wpm accuracy consistency graphs replays personal bests missed word practice etc

read is rsvp so words show one by one at a speed like 200 300 500 or 800 wpm with pauses around punctuation

read + type mixes both

you can use random words quotes custom text actual books or upload your own pdf

random word reading ends with a recall test since comprehension doesnt really make sense there. with real text you can get comprehension questions and an effective reading score which is basically wpm x comprehension

the competitive reading part is a daily challenge. everyone gets the exact same passage and same 5 questions that day. you get one ranked attempt and need at least 80% comprehension to qualify for the leaderboard

books are probably the part i spent way too much time on lol. you can read a book by literally typing through it, use rsvp, or read a page and write what you remember. progress is saved and there are comprehension checkpoints around chapters/every few pages. pdfs turn into the same reader

there's also vocab with spaced repetition, translations inside the reader, typing duels, friends/dms, profiles, stats, xp, badges, leaderboards, clans, themes, community quotes and a bunch of profile customization

at this point my biggest question isnt what else to add

its what the hell should i make the main thing

would you position this around typing + reading together or mostly around the competitive reading/daily challenge part

i've been building an app that mixes reading practice with monkeytype style typing

you can do normal typing tests, type through quotes, or even open a book/pdf and basically read it by typing the text as you go

there's also rsvp reading where words show one by one at a speed you choose

if its random words you get a recall test after to see how much you actually remembered

if its real content like quotes or books you can get comprehension quizzes instead, and books have quiz checkpoints every few pages or at the end of a chapter

the main competitive reading thing is a daily challenge where everyone gets the same passage, reads it through rsvp at 200 300 500 or 800 wpm, then answers the same 5 questions

you need at least 80% comprehension to qualify and your score is basically wpm x comprehension, so just flying through at 800 wpm doesnt mean much if you didnt understand it

there are also typing duels, leaderboards, book progress and some social stuff around it

im mainly trying to figure out if combining typing, rsvp, recall and comprehension into one reading practice app actually makes sense to people who are into this

what would you change or add

we’ve been building something called LocIn AI and honestly we need people to destroy the idea before launch

you can test it here:

locin.dev

current app:

app.locin.dev

important note:

it’s not final at all. there are bugs, rough edges, unfinished parts etc. we mainly need honest feedback right now

context:

i spent ~8 months interning at an AI edtech startup, and one recurring problem was localization/i18n at scale. our CTO was constantly throwing huge 8k+ string localization tasks into Google AI Studio and Cursor, but context kept breaking apart and consistency got messy

at first we honestly looked at this as a simple side project. like “okay the idea is cool, we’ll build it and move on”

but while experimenting, we realized something more interesting:

for vibe coders or teams that never properly set up i18n, our unreleased CLI can scan the whole codebase, inject i18n keys, organize them, and generate translations automatically

the interesting part is that translations are generated based on selectable tone profiles. soon we’re adding style extraction too, where you can give a URL and it extracts the writing/product style automatically

so in theory it can handle some “too much context” workflows that tools like Claude Code struggle with

BUT:

we genuinely do not want to oversell this

we need criticism more than hype

tell us:

- why this is a bad idea

- what breaks technically at scale

- whether this is actually painful enough to be a company

the funny part is that a pretty important VC from turkey was actually the reason we started taking this seriously as a startup instead of “just another project”

recently we also talked with a VC scout from china who said they’d consider investing if we can pull off a genuinely strong launch. if that happens, we’d probably build a dedicated research team around the problem

to be honest:

for non-technical people this sounds “genius”

but we want this to become a real devtool that actually saves engineering time

and no matter what happens, we’re launching anyway because at the end of the day this is an EXPERIMENT

please be harsh, but constructive

founder here

during my internship at an ai edtech startup, one thing that kept becoming painful was large-scale i18n/localization workflows with llms

especially when dealing with thousands of strings, tools like Cursor or Google AI Studio kept losing consistency, tone, naming patterns, and overall context

we started experimenting with a different approach:

instead of “translate this file”, the system scans the entire codebase, injects i18n keys automatically, understands project structure, and generates translations with tone-awareness

we’re also experimenting with style extraction from existing products/websites so translations inherit the same writing style

the technical question is:

do you think localization/i18n is actually painful enough today to justify dedicated AI-native tooling?

or does this eventually become “just another feature” inside coding agents like Claude Code/Cursor/etc?

curious how engineering teams here currently handle localization at scale