Product Roadmap

Building the Future of Language Reading

Our strategic plan to make Ember a premium language reading environment where users can open real texts, understand them quickly, hear the language, and build long-term fluency.

Strategic Product Pillars

The roadmap is built around one core loop:

read real texts understand instantly hear the language save useful items review lightly return to reading
Phase 1

Core Completeness

What Ember needs to feel like a complete product. These are the highest strategic priority.

Very High

Broader Format Support

Add TXT, FB2, and basic PDF support. EPUB/FB2/TXT treated as native; PDF as supported with limitations.

format support import
Very High

TTS for Word and Phrase

Pronunciation playback for selected words and phrases. Core language feature, not just accessibility.

audio TTS pronunciation
Very High

Strong Personal Dictionary Foundation

Lemma-based grouping, stable lemma generation, dictionary-entry model, item states (new/learning/known/ignored).

vocabulary lemmatization
Very High

Better Import and First-Reading Flow

Improve file importing, format clarity, reliability, and first-open experience after import.

UX onboarding
High

Starter Content / Sample Library

Sample books or curated starter texts grouped by language. Enables immediate value and better onboarding.

content onboarding
Phase 2

Premium Reading Experience

What makes Ember feel worth paying for. The transition from functional to exceptional.

High

Audio-Assisted Reading

TTS for current sentence or paragraph, play-from-here, optional sentence stepping, follow-along highlighting.

audio TTS reading mode
High

Review Tightly Connected to Reading

Light, context-aware review derived from real reading. Easy jump back to source book. Reading-first, not flashcard-first.

SRS review
High

Session Continuity

Continue where you left off, subtle reminders about saved or due items, session recap, "resume + optional review" patterns.

UX engagement
Medium-high

Progress Visibility

Pages read, books finished, reviewed items, repeated encounters, knownness growth, comprehension progress per book.

analytics motivation
Phase 3

Signature Differentiation

What can make Ember meaningfully distinct from competitors. The features that make Ember memorable.

High

Re-reading Features

Re-reading with remembered items visible, revisit support, "you used to not know these items" indicators, resurfacing of saved language in context.

differentiation memory
Medium-high

Smart Language Triage

Accept to learning, mark known, ignore, archive. Possibly suggest actions based on frequency or repeated exposure.

vocabulary organization
Medium

Context-Rich Review Modes

Review from original sentence, review across multiple encounters, compare similar usages, "seen before in these books".

review context
Phase 4

Advanced Expansion

Valuable later additions that should not compete with higher-priority roadmap items.

Medium

Parallel Texts

Strong feature for advanced learners. Adds complexity to UX, content structure, and implementation.

advanced content
Low-medium

Cloze Deletion

Useful but may push Ember toward generic SRS territory. Only after reading and re-reading foundation is strong.

SRS advanced
Low

Additional Review Modes

Typing, multiple choice, matching, flashcard variants. Only if they clearly strengthen the reading loop.

SRS review

Priority Tiers

Tier A — Must Have

Required for Ember to feel like a strong, complete product.

  • TXT support
  • FB2 support
  • Basic PDF support
  • TTS for word
  • TTS for phrase/sentence
  • Strong lemma infrastructure
  • Personal dictionary foundation
  • Better import flow
  • Starter/sample content
  • Polished reading-save-lookup loop

Tier B — Should Have

Make Ember feel premium and coherent.

  • Audio-assisted reading
  • Session continuity
  • Reading-connected review
  • Progress visibility
  • Smart triage for saved items

Tier C — Differentiation

Can make Ember truly memorable.

  • Re-reading features
  • Context-rich resurfacing
  • Stronger accumulation model
  • Knownness / repeated exposure logic

Tier D — Later

Advanced expansion when foundation is solid.

  • Parallel texts
  • Cloze deletion
  • Extra review modes

What We're Not Building

These should not be priorities right now:

  • Many review modes just for feature count
  • Heavy gamification
  • Turning Ember into an Anki-like system
  • Trying to make PDF equal to EPUB
  • Building a huge built-in library before starter content proves value