What we’re building next.
Every feature we're actively working on, with rough ETAs where honest. Plus: what we've decided NOT to build, and the specific reason each was cut. Public, dated, updated when scope moves.
Everything below is real.
If it’s on our pricing page, it’s live today. If it’s here, it’s on the workbench. If it’s neither, we haven’t decided yet. When we ship an item, it moves to the changelog.
Handwriting attempts
Attempt a problem by drawing on paper or a tablet, snap a photo, we OCR it and feed the tutor. The scaffolding is in the app — see the DRAW / PHOTO buttons on the Learn screen — but capture is still being wired.
Voice attempts
Hands-free tutor: verbalize your attempt, hear the Socratic response, keep working. The HOLD-TO-SPEAK button exists in demo state; live capture ships when we've solved the streaming ASR + guard flow.
EU data residency (Frankfurt)
Second Supabase region for institutional customers with hard EU-residency requirements. All new EU customers post-launch will default to the Frankfurt region. Existing customers can migrate on request.
SOC 2 Type I
Formal SOC 2 Type I attestation. Pre-cert package (control matrix, pen-test summary, remediation timelines) available now under NDA for institutional prospects.
Study group mode
Opt-in cohort view for classmates. Aggregate progress only — never each other's attempts. Educators can already do this via /for-schools; this brings it to peer groups.
Import syllabus / textbook chapter from URL
Paste a Coursera / OpenStax / school-hosted PDF; Haiku extracts concepts + seeds your recall queue. Text-paste flow already works on the class page.
Mobile app (native iOS + Android)
The web app is already installable as a PWA. Native wrappers with push notifications for recall reminders land next. Feature parity from day one.
AI-generated problems from your weak concepts
Nightly, we mint a fresh problem targeted at your worst-mastery concept. Currently the tutor works from a curated bank; this widens the surface without diluting quality.
Weekly wrapped
Friday recap: what you learned, what you struggled with, what to attack next week. Optional shareable card. Different from the Sunday Brain-score email.
K-5 age-tuned surface
A gentler, larger-type, image-heavy variant of Learn mode for elementary. Requires a different content-safety layer + parent co-pilot mode.
Language-learning surface
Grammar + conjugation practice is already good in Learn mode. What's missing is the vocabulary-acquisition surface (which Anki does well). Deciding whether to build it or partner.
In-app collaborative whiteboard
Multi-student real-time attempts on the same problem. Could be great; could be a distraction. Prototyping to see whether it protects the attempt-first workflow.
Six things not on the roadmap. Ever.
Every quarter we get emails asking us to build these. We don’t — not because they wouldn’t sell, but because each one would collapse a specific load-bearing part of the product. The refusal to build is as public as the roadmap.
why · It would collapse the refusal into a soft answer machine. Not for sale at any price.
why · Even with a 'don't submit this' checkbox, we'd be publishing the exact material we exist to withhold.
why · The ladder's cost is what makes hints intentional. Bypassing it destroys the mechanism.
why · There will never be ads on Brainback. The business model doesn't require it.
why · Even anonymized, it's a category of use that trains us to think about data as inventory. We won't.
why · See /parents/privacy. Content-blind is load-bearing, not a preference we'd flip for a bigger deal.
Nothing here is a promise. Ship dates in tech are rough estimates that slip; we publish them because slipping estimates are more useful than no estimates. When an item moves — up in priority, down in priority, or out entirely — we update this page and the changelog notes the move.
What’s worth trusting: the “won’t build” list is more stable than the “will build” one. Every item in the former has been rejected multiple times.
Tell us what you’d pay for.
A real human reads every feature request. If it’s a good one, we’ll say why we agree; if we disagree, we’ll say why we disagree. Either reply within 24 hours.
No auto-reply. A human reads every one.