Post-2.0 roadmap proposal: doubling down on offline-first as a product advantage #40
aynazar-sylyyew-dev
started this conversation in
Ideas
Replies: 1 comment 1 reply
|
Great roadmap! I especially love points 1 (TTS), 2 (SRS review mode), and 4 (adding Turkic language pairs like Turkish, Kazakh, and Uzbek). TTS and SRS will make learning so much more interactive, and expanding to regional language pairs is a fantastic vision for growth while keeping everything fully offline. Fully support this roadmap! |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Seydi, first of all — well done on shipping v2.0. The pivot to scenario-based dialogs was the right call, and the follow-up cleanup (removing the cloud AI client, deleting unused dependencies, closing the npm audit advisories, finalizing the Turkmen-first store listing) left the codebase in a visibly healthier state. I'd like to propose a focused roadmap for the next releases that builds on exactly this strength: a truly offline, real-life conversation companion.
The core thesis: our differentiator in the store is "works fully offline in real-life situations". Every item below strengthens that promise, requires no backend, and adds no maintenance burden.
1. On-device pronunciation (TTS) — highest impact, lowest risk
The dialog scenarios teach users what to say, but not how it sounds. Android ships a system TTS engine that works offline, so we can add per-phrase playback with zero network dependency and zero new infrastructure. This closes the biggest gap between a phrasebook and a real language companion — and pronunciation is exactly the kind of thing that shows up in 5-star reviews.
2. Spaced-repetition review mode for scenario phrases
A phrasebook is a reference tool; a review mode turns it into a daily habit. A minimal SM-2 scheduler over the phrases the user has already seen would improve retention and DAU without touching the content pipeline. Fully offline, small isolated module.
3. Favorites + in-scenario search
A low-cost UX win that users of reference apps expect: star phrases and find the right one in two taps during a live conversation. This directly supports the "hand the phone over" mode described in the README.
4. Two or three high-value language pairs (Turkish, Kazakh, Uzbek)
Turkmen speakers most often need pairs within the Turkic world. Adding 2–3 pairs expands the store reach across the region while reusing the existing scenario content structure.
5. Home-screen widget with quick phrases
Home-screen presence is the cheapest retention mechanism on Android. A small widget with the current scenario's key phrases keeps the app one tap away.
Suggested phasing (small, reviewable PRs):
I'm ready to take Phase 1 and open PRs item by item, keeping each change small and testable against the existing jest setup. Nothing here requires a backend or weakens the offline promise.
What's your view — which of these fit your vision for v2.1? If something doesn't fit, I'd rather hear it now, before writing code.
All reactions