Flowtranslate AI Learning System
A translation-first PWA that turns everyday translation history into personalized language learning.
Flowtranslate started from a real behavior: wanting to write or understand English quickly, then learn from those daily moments later. The product balances fast translation with a separate learning flow that can use the user history as material.
- Bidirectional translation flow
- Learning from history
- Quota-aware AI usage
- Study article direction
Most translation tools optimize for a single answer and forget the context. For a learner, the valuable material is the trail of real phrases they needed during the week, including what other people wrote to them.
- Keep the translation interaction fast and low-friction instead of forcing learning into every input.
- Treat saved translations as learning context that can later become study material.
- Use faster model paths for translation while leaving richer generation for study content.
- Make quota visible and account-based so AI cost can become a product boundary instead of an invisible risk.
Product surface
- Web PWA with translation as the primary flow.
- Separate learning surface that can open historical conversations into focused study.
- Study article direction designed around grammar, tense, syntax, and common mistakes.
AI and data flow
- Supabase Auth profiles and translation records in a dedicated schema.
- Server-side Gemini calls through the flowtranslate-generate Edge Function.
- Usage events and monthly quota checks before expensive AI work.
- A fast translation flow can conflict with a richer learning interface, so the product separates immediate output from deeper study.
- Autodetect and rewrite behavior can simplify the UI, but it requires careful feedback copy so users understand what happened.
- Saved history makes learning more personal, but it raises product responsibility around privacy and account data.
Solo product engineer owning the product concept, UX direction, frontend, Supabase integration, AI orchestration, quota behavior, and deployment path.
- Juan can turn a personal learning need into a product system with cost and data boundaries.
- He thinks about AI as product leverage, not decoration.
- He can connect frontend speed, backend constraints, and learning experience into one loop.