Roadmap
Where YAKKI is heading In Development
Everything on this page is in development: designed, documented, partially built — but not yet in classrooms. We publish it because schools and partners deserve to see the direction, not just the present.
Status note: items on this page are plans, not commitments. Scope and timing may change as pilots teach us what actually works.
In development
Three assemblies, one platform
The same generation engine, games, and pedagogy — packaged for three very different contexts:
School Assembly In Development
The teacher-led configuration: class lessons, homework, progress reports per student, and curriculum-aligned topic planning. Grows directly out of today’s GuestDay.
Family Assembly In Development
For parents supporting a child’s English at home: simple setup, safe topics, visible progress, and sessions short enough for a school evening.
Individual Assembly In Development
For independent learners and adults: a guided daily mission instead of an empty menu, with free practice as the escape hatch — not the default.
Designed in detail
The individual learning track
The individual track is fully designed and committee-approved. Its core decisions:
Daily Mission, not an empty menu
Each day opens with a short generated mini-lesson of 3–4 games with rising challenge. One big button: Continue. Pedagogy survives self-study.
Mistakes first
A session starts by revisiting yesterday’s mistakes — spaced repetition built into the daily flow, not hidden in settings.
Constrained choice
The free-practice tab recommends a handful of games matched to the learner’s level and recent work. A hundred-plus formats are power, not a menu.
Transparent rules
Progression rules are explainable — no opaque adaptive black box. The learner can always see what they are training and why.
The deeper layer
The pedagogical matrix
In DevelopmentBeneath the assemblies sits the most ambitious piece: a dynamic model of how each learner learns best right now. Not a personality test, not a diagnosis, not a label — a working profile of learning regulation that changes over time and with context.
The matrix observes how a learner responds along five axes:
Response to difficulty
What happens when a task gets hard — and how much scaffolding helps.
Response to errors
Whether a mistake works as a signal or as a stop — and how feedback should be dosed.
Need for structure
How much step-by-step guidance the learner currently relies on.
Strategy flexibility
How format changes affect performance — and how to pace variety.
Need for external support
Hints, anchors, and checklists: how much, and when to fade them.
Teachers never see psychological labels or types. They see actionable presentation recommendations: smaller steps, softer feedback, more structure, gentler format changes. The learner is never the problem; the presentation is the variable.
The matrix’s measurement methodology and algorithms are proprietary and not published.
Order of release
Which platform comes when
Assuming things go well, the platforms arrive in this order. These are plans, not commitments, and we give no dates because we do not have them.
- YAKKI EDU for Android, which is what exists today
- YAKKI EDU for Windows — in advanced development
- YAKKI Family for Android — in advanced development
- YAKKI EDU for iPhone
- YAKKI Family for iPhone
A decision, not an omission
Why there is no browser version
The browser version was not skipped. It was built: a React version reached roughly half of its scope, and then we stopped it and dropped the work. Browsers behave differently from one another and keep changing underneath you, and half a version was enough to see what that costs.
The part that decides it for us is the microphone. Recording and playback are handled inconsistently across browsers, and for this platform the microphone is not a convenience: every student reads aloud and is assessed. A feature that works in one browser and fails in another is worse in a classroom than a feature that is absent.
So we chose Windows instead. It reaches fewer devices than the web, and we accept that. What it gives back is control: one environment we can test, one place where audio behaves the same way tomorrow as it did today. Many schools have laptops rather than Android tablets, and older machines are fine.
Also in development
Platform expansion
Public download In Development
Store-distributed Android release with self-service onboarding.
Windows version In Development
A desktop build for schools that have laptops rather than Android tablets. Older machines are fine.
Tutor mode In Development
Tools for private tutors to direct a learner’s practice remotely.
Help shape what comes next
Pilot schools and research partners directly influence the order in which this roadmap becomes reality.