u/Equivalent-Market-87

built an ai localization tool/management platform and now we need people to tell us why it sucks

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

reddit.com
u/Equivalent-Market-87 — 11 days ago
▲ 1 r/SaaS

are we overengineering i18n or is this actually a real problem

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

reddit.com
u/Equivalent-Market-87 — 11 days ago