¿Puedo vibecodear Loco?

PARCIAL · un fin de semana
precio $5.95/mesahorrarías $71.4/añotiempo de build un fin de semanacategoría 🌍 localizaciónreemplazada por 0 personas

The core of Loco is a keyed string store with a locale matrix on top, and that part is genuinely a one-sitting build: SQLite, a table view, an import and an export. What eats the weekend is the format layer, because gettext PO with plural headers, Apple .strings and .stringsdict, Android plurals XML, ICU messages and flat JSON all disagree about pluralization and escaping in ways that only show up in production. Machine translation fill-in is a single API call if you already have a DeepL or provider key. If you are the only translator, a local build is fine and arguably faster to work with. If you send links to freelance translators and rely on the hosted API in CI, you are rebuilding a service, not a tool.

el prompt
Build a local translation management app called Strings. No accounts, no cloud, no telemetry.

Stack, non negotiable:
- Node 20 with Express and TypeScript
- SQLite via better-sqlite3, file at ./data/strings.db
- Server rendered EJS templates plus a little vanilla JS, no React, no bundler
- Runs with `npm run dev` on localhost:4321

Data model:
- projects: id, name, source_locale
- locales: id, project_id, code (BCP 47)
- keys: id, project_id, name (dot notation allowed), context note, created_at
- translations: key_id, locale_id, plural_category (one of other, one, two, few, many, zero), value, updated_at
- history: translation_id, old_value, new_value, changed_at

UI:
- Project list, then a grid page per project: rows are keys, columns are locales, cells are inline editable textareas that save on blur via fetch
- Filters: untranslated only, search by key or value substring
- Per key detail drawer showing context note, plural forms, and history
- Progress bar per locale showing percent of keys with a non empty value

Import and export, implement exactly these three formats and be strict:
- Flat and nested JSON
- gettext PO, including Plural-Forms header parsing and msgid_plural
- Android strings.xml, including plurals blocks with quantity attributes
Use the CLDR plural categories for each locale code; hardcode a small lookup table for the twenty most common locales and fall back to other plus one.

Also ship a CLI: `npm run export -- --project=X --locale=fr --format=po --out=./out` so a build script can use it.

Optional machine translation: if DEEPL_API_KEY is set in .env, add a "fill empty cells" button per locale that batches untranslated source strings through DeepL and marks results as machine translated with a flag shown in the grid. If the key is missing, hide the button rather than erroring.

Out of scope: multi user auth, sharing links, webhooks, screenshots, glossary, TMX.

Include a README with setup, a `.env.example`, and seed data for one project with English, French and Polish so plural handling is exercised on day one.

$ ábrelo en tu agente (prompt listo, tú das enter) o cópialo crudo

Se puede en parte

Ahorro de referencia: US$71/año si dejas de pagar Loco.

Quiero que lo armen →
por qué la gente sigue pagando

Because localization is a pile of edge cases someone else already ate. Plural categories vary by language, every platform escapes strings differently, and one bad export ships mangled text to users in a language nobody on the team reads. Paying also buys a link you can send to a contractor and an API your build can hit, which a folder on your laptop cannot do. Solo developers with two or three locales tend to outgrow the need for that rather than into it.

qué pierdes

xFormat breadth: Loco reads and writes a long tail of formats, including the awkward Apple and Qt ones, with plural rules per locale already correct

xA shareable editor for non-technical translators, with roles, comments and progress tracking

xA stable public API and CLI that CI pipelines can pull from at build time

xTranslation history, who changed what, and the ability to roll a string back

xGlossary and translation memory suggestions that improve as the project grows

arte previo · úsalo en vez de construir, si prefieres

Nada que valga la pena señalar. Por eso existe el prompt.

compartir en X ↗"Acabo de reemplazar Loco ($5.95/mes) con un prompt"
preguntas
¿Puedo vibecodear Loco?

Parcial. El núcleo de Loco se arma en un fin de semana con el prompt de esta página, pero hay huecos reales: Format breadth: Loco reads and writes a long tail of formats, including the awkward Apple and Qt ones, with plural rules per locale already correct, A shareable editor for non-technical translators, with roles, comments and progress tracking. Lee la lista honesta arriba antes de comprometerte.

¿Cuánto cuesta Loco?

Loco cuesta unos $5.95/mes (Pro, revisado 2026-08-18), o sea $71.4 al año.

¿Qué pierdo si reemplazo Loco?

Con honestidad: Format breadth: Loco reads and writes a long tail of formats, including the awkward Apple and Qt ones, with plural rules per locale already correct; A shareable editor for non-technical translators, with roles, comments and progress tracking; A stable public API and CLI that CI pipelines can pull from at build time; Translation history, who changed what, and the ability to roll a string back; Glossary and translation memory suggestions that improve as the project grows. Si alguno de esos te sostiene el negocio, sigue pagando.

¿Hay una alternativa open source a Loco?

No hay una alternativa open source madura que valga señalar. Por eso existe el prompt de esta página.

Cada semana mueren más suscripciones.

Veredictos nuevos, prompts nuevos, las apps más condenadas de la semana.
Un correo. Te sales en un clic.

gratis para siempre · sin spam · el prompt se queda en el sitio, las muertes te llegan a ti

$semanal: qué recibió veredicto, qué murió.