Platform-integrated, developer-facing HTML PRD.
This version shows how the progress system connects to the platform's own modules and functions,
including guided plan creation, reward bars, learner identity themes, streak handling, and recovery behavior.
Primary CurrencyStars
Visual MomentumXP-style feedback bars
Punishment ModelNo damage or death loop
Research Scope59 reference HTML files reviewed
What This HTML PRD Is
The written Markdown PRD defines behavior, rules, and scope. This HTML version adds the missing visual layer so a developer can understand what the system should feel like on screen, not only what fields and events it stores.
Use This File For
dashboard and module page layout direction
reward and progress bar treatment
visual translation of game-like progress patterns into this app's own system
alignment between PM, designer, frontend, backend, and QA
Important Constraint
Users do not create arbitrary free-text tasks here. They build trackable study plans from the platform's own modules, lessons, activities, and recovery units. The progress layer must therefore feel flexible while staying connected to real learning functions.
Keep: streaksKeep: checklistsKeep: rewardsAvoid: HP damageAvoid: death mechanics
AI English Learning App Progress Tracker
Visual PRD for the progress system, guided study plans, rewards, and recovery flow
System Model: Open Productivity Feel, Platform-Bound Study Logic
The goal is to deliver the motivation, clarity, and visible momentum of a strong task system without letting users create disconnected or invalid work items. Every trackable item must map back to an approved learning surface in this platform.
Open Productivity Expectation
XP for fast feedback
classes for player identity
repeat, scheduled, and one-off work shapes
day-completion bonus
pause and recovery behavior
tags, checklists, and urgency cues
Platform Implementation
Stars as persistent reward currency
soft learning archetypes instead of RPG combat classes
required recurring units, optional repeat practice units, and one-time learning units generated from real modules
Perfect Study Day for all due required work
snooze, low-pressure mode, pause, and rest
weak-item recovery, teacher/parent digest, and honest completion validation
Reference Concept
Decision
How It Should Look Here
Implementation Meaning
Session momentum bar
Adapt
short-term progress bar inside a session or module
visual feedback only; persistent economy remains stars and mastery progress
Unlock ladder
Adapt Lightly
optional study rank or journey tier ribbon
cosmetic pacing layer only; do not gate core learning functions behind high level thresholds
Learner identity theme
Adapt Carefully
study archetype badges, themes, and focus suggestions
identity layer only; no combat stats, no skill trees in MVP
Recurring required units
Keep
today plan, Daily Recital, required Journey tasks
drives streaks, reminders, and Perfect Study Day
Repeat practice units
Keep Softly
repeatable optional practice cards generated from allowed modules
counts toward momentum without needing harsh missed-day penalties
rest banner, quiet reminder state, simplified plan
protects learners from punishment-style collapse
Health / Death / Mana
Avoid
do not render
not aligned with child-safe, education-first motivation
Primary Dashboard Visual
The dashboard is the progress command center. It should tell the learner what to do next from the platform's actual learning functions, show whether effort counted, and make recovery obvious without making the learner feel punished.
My Study Today
See what to do, what you finished, and what comes next
My Path is onMain task readyParent note ready
My Streak
12
You studied for 12 days
My Stars
184
16 more stars for a new badge
Great Day
Yes
You can still finish all today's work
Words to Fix
9
6 word list, 3 speaking words
My Work TodayYour study plan for today
Daily Recital: Finish today's part
Daily work | Speaking warm-up
Do today
ProgressDone
Vocabulary Trainer: Finish 1 round
Main task | Word practice
Main task
Words done this round18 / 25
Reading: Finish 1 passage
Reading work
Not yet
Reading progress0 / 1
Word List: Review 5 words
Extra help
Try this
Words fixed2 / 5
This WeekYour study this week
Study days done4 / 5 days
Great days: 3Free pass left: 0Read to get more
My RewardsSee your stars and progress
Round progress64 / 100
Stars today: 3Next gift: frame at 200
My LearningSee each part here
Vocabulary Trainer
Rounds done, words done, and level progress
Main part
Scenario Role-Play
Finish work, score change, and hard words
Speaking
Thinking Lab
Step progress and checklist
Thinking
AI DSE Reading
Passage progress and hints
DSE
Home NoteFor teacher or parent
Status: Trying hard, but still needs help
The student is studying well, but more hard words are building up.
Next step: finish one Word List review before extra speaking work.
Cross-Client and Companion Experience
The tracker should behave as one system with different depth on each surface. Web is the full command center, mobile is the fast companion, and wearable surfaces should stay lightweight.
Web dashboardFull planning surface
My Work Today
Today's work, main task, and help tips
My Rewards
Stars, progress bar, and next gift
Home Note
Parent and teacher message
best place for guided plan creation, task selection from modules, and rich dashboards
supports filters, tags, checklist editing, and full progress explanation
primary home for adult monitoring and reset/recovery administration
Phone viewToday first
Do Today
Daily Recital, 1 vocab round, reading
Quick View
Today, All, Hard words, Catch Up
Rewards
Stars today, streak, next gift
optimized for quick completion, reminders, and on-the-go review
must preserve event parity with web
needs clear refresh, sync, and filter behavior
Watch viewOptional
12 day streak
One-tap glance
Next work
Daily Recital
use only for glanceable progress, reminders, or quick acknowledgment
do not make watch the main study surface
keep interaction count low and completion validity strict
Surface
Must Support
Can Be Lighter
Design Implication
Web
full dashboard, guided plan builder, adult digest, recovery controls
none of the core tracker logic
full-fidelity progress explanations and configuration
Mobile
due-first lists, quick completion, streak, star wallet, filters, refresh
dense reporting and advanced administration
companion-first, fast, and resilient to interruption
support action initiation, not deep task management
Loading and Empty-State Tips
The app should use loading, empty, and waiting states to teach better study behavior.
break big work into small steps
one vocab round is better than "study more"
do the hard work first
Filter Logic
Mobile pages should support filters similar in spirit to Due vs All, weak vs strong, and catch-up views.
Today
All
Catch Up
Hard Words
Settings Sync
Progress mode, reminder intensity, accessibility preferences, and language or audio settings should stay consistent across clients when possible.
Reward Stack, Stars, and XP-Style Visuals
Developers need to distinguish between what is persistent and what is only short-term feedback. The product's stored long-term reward is stars. However, an XP-like bar is still useful as on-screen motivation inside a session or daily plan.
Layer 1: Immediate MomentumVisual only
Use an XP-style fill bar during a session, round, or checklist completion. This helps the learner feel progress quickly, especially in Vocabulary Trainer, reading passages, and multi-step Thinking Lab flows.
Round progress78 / 100
Layer 2: Daily CompletionReal product logic
Show whether the learner met the daily minimum and whether all due required tasks were completed. These are different states and both should be stored.
Minimum goal metGreat Day still possible
Layer 3: Weekly RhythmRolling 7-day logic
Weekly target bars show rhythm, not just raw volume. This is where rolling 7-day target completion and grace-day interpretation become visible.
Weekly target6 / 7 rhythm points
Layer 4: MilestonesPersistent progression
Milestones should unlock tangible, visible rewards such as Ari accessories, companions, frames, themes, and badges.
Accessory unlockTheme unlockBadge unlock
Total Stars
184
Next frame unlock at 200
Ari companion unlock at 240
Theme track unlock at 300
Developer Rule
Stars are cumulative and never lost. Session bars, XP-like fills, and module progress meters may reset visually, but stars and unlock history persist.
Optional Study Rank
The level pages suggest that a visible progression ladder can help pace unlock excitement. If desired, add a lightweight Study Rank or Journey Tier ribbon.
cosmetic and motivational only
can unlock themes, frames, or archetype badges
should not gate essential lessons, reminders, or recovery features
Currency Translation
This product should keep the economy simple: stars are the main persistent currency, while XP-style bars remain visual momentum indicators only.
Learner Identity Theme System
The product can use a soft identity layer so developers understand the intended feel. It should not adopt a literal RPG class system. Instead, it can use a learner identity theme layer that changes theme, orientation, and recommendation style without changing scoring fairness.
Book Star
Best visual fit for Vocabulary Trainer, Word List, and General Reading.
book, card, or notebook motifs
mastery rings and reading bars
focus suggestion: vocab round or reading passage
Speech Star
Best fit for Scenario Role-Play, Daily Recital, and Recite Your Script.
voice-wave, stage, or mic-inspired accents
retry and improvement cards
focus suggestion: one speaking completion with score lift
Think Star
Best fit for Thinking Lab, ARI support, and AI DSE Prep reading flows.
Best fit for Journey Mode, streak retention, and comeback flows.
route, peak, and milestone markers
streak card, weekly rhythm, comeback banner
focus suggestion: hardest-task-first or catch-up block
How Developers Should Use This
theme dashboard accents or badge sets by archetype
change copy tone and highlight cards by learner identity
use archetypes to group recommendations, not to change scoring rules
What Not To Do
do not create combat stats, mana spend, or damage loops
do not gate learning content by archetype choice
do not make one archetype objectively better than another
Guided Plan Builder, Goal Design, and Smart Tips
The tracker must help users build meaningful study plans, but only from the platform's own functions and modules. Users should feel agency without being asked to invent arbitrary tasks disconnected from real learning surfaces.
1. Choose Goal Direction
Start from a real objective such as improve pronunciation, finish one reading passage, or recover weak words.
SpecificRelevant
2. Pick From Allowed Modules
Select only from available surfaces such as Vocabulary Trainer, Word List, General Reading, Daily Recital, Scenario Role-Play, Thinking Lab, or DSE functions.
ModuleFunctionUnit
3. Configure Scope and Rhythm
Choose quantity, frequency, due timing, and recovery behavior from allowed options. The system then generates trackable study units.
CountScheduleThreshold
4. Generate Study Plan
The platform creates recurring required units, optional repeat units, or one-time units, then attaches stars, progress bars, and review logic.
RewardReview
How Users Create Trackable Work
Step 1: choose a real module or function from the platform
Step 2: choose the unit style the module allows, such as one round, one passage, one script attempt, or one review packet
Step 3: set frequency or due timing from approved options
Step 4: let the system generate the study item and attach completion rules automatically
UI Connection to the Progress System
Module card: user chooses from real available learning surfaces
Plan builder sheet: user selects scope, timing, and priority from structured controls
Generated study item: dashboard and reminders show the created item as part of the progress system
Completion event: actual learning flow sends validated events back to the tracker
Guided Plan Builder UI Flow
1. Open Planner
User clicks Add Study Plan from Dashboard, Journey, or a module page.
2. Choose Module
System shows only supported modules and functions, not a blank task field.
3. Choose Unit
User picks one allowed unit such as vocab round, reading passage, script attempt, or weak-word packet.
4. Set Rhythm
User chooses repeat pattern, target count, due day, and optional focus priority.
5. Generate
The system creates structured study items and adds them to the tracker, streak, reminders, and reward system.
Guided Plan Builder Visual Demo
Add Study PlanStep 2 of 4
Pick a learning part
Vocabulary Trainer
Word List
Reading
Speaking
Thinking Lab
DSE Reading
Pick what to do
Finish 1 round
Finish 2 rounds
Learn 10 words
Review hard words
Pick when
Every day
3 days a week
This week only
Before Friday
Pick help options
Main task
Extra task
Add reminder
Catch Up if missed
Plan preview
Vocabulary Trainer: Finish 1 round
Every day
Shows in My Work Today
Gives stars when done
What This Demo Shows
the learner chooses from real platform parts, not from a blank task box
the learner still has control over amount, time, and priority
the system can explain the plan before saving it
the same builder can work for words, reading, speaking, thinking, and recovery plans
Student-Facing Copy Rule
In the real UI, builder buttons should use short ESL-friendly labels such as
Pick a learning part, Pick what to do, and Pick when.
Selected Module
Allowed User Choice
System-Generated Study Item
Why This Replaces Free Task Creation
Vocabulary Trainer
1 round, N rounds, target mastery count, daily repeat
recurring required unit or repeat practice unit
user still chooses scope and rhythm, but the unit always maps to a real trackable vocab flow
the speaking plan stays tied to actual scenario sessions and validated score events
Recite Your Script
assignment acceptance, attempt planning, due timing
one-time study unit
assignment work appears in the tracker without becoming vague free-form work
Thinking Lab
lesson selection, stage cadence, focus priority
ordered lesson unit
step-based thinking work stays structured and sequential
Good Generated Study Items
Complete today's Daily Recital passage
Finish 1 Vocabulary Trainer round
Review 5 Word List weak words
Record Script 2 before Friday
What The UI Should Not Allow
blank free-text task creation disconnected from modules
vague plans such as "Do English"
items with no completion rule
made-up activities that the platform cannot validate
Contextual Smart Tips
Tips should be pulled from the current learner situation, not shown as random trivia.
Use a checklist when a task feels too big
Try the hardest task first when avoidance is visible
Turn a one-time reading plan into a recurring reading target if the learner needs steadier rhythm
Weekly Process Review
The tracker should support a light weekly review task for learners, parents, or teachers.
What tasks were repeatedly snoozed?
Which module is being avoided?
Should a recurring required unit become optional or simplified?
Sample Plan Templates
The platform can later ship prebuilt plan templates for common learner profiles using only approved functions and unit types.
exam-prep week
weak-vocabulary recovery
daily speaking confidence
Real Platform Mapping
The tracker must map to real platform functions, not just broad labels like "speaking" or "reading". The cards below show the visual and product meaning each module needs.
Word List
Counts as: weak-item recovery surface and plan-builder option
track weak-word backlog and recovery speed
show backlog severity when threshold is exceeded
allow optional use in normal mode and stronger prompting in recovery mode
Vocabulary Trainer
Counts as: core round and mastery engine, selectable in guided plan builder
visualize book, level, round, word, and task layers
show retries, pronunciation gate, and mastery status
support daily units by round plus mastery
General Reading
Counts as: reading passage completion
track passage finish, question set, time, and hint use
never treat hint usage as failure
show reading target progress as part of daily plan
Scenario Role-Play
Counts as: speaking completion plus improvement signal
show score breakdown and change from previous attempt
surface low-score word transfer into Word List
make retries visible without over-rewarding spam
Daily Recital
Counts as: strongest natural recurring required unit
should be visually treated as a streak anchor
simple completion bar and today badge
ideal location for supportive reminder loops
Recite Your Script
Counts as: assignment-like one-time speaking unit
show teacher assignment, attempt count, and due state
support bulk-upload classroom workflows
make completion validity strict and auditable
Thinking Lab
Counts as: ordered multi-step lesson
visualize step sequence and checklist completion
should feel like progress along a path, not random tasks
support current five-step flow first
ARI
Counts as: support signal, not primary completion by default
track usage and session support value
avoid falsely treating chat support as lesson completion
show in adult digest as context, not as core discipline proof
AI DSE Reading
Counts as: exam-oriented reading completion
support passage progress, hint usage, and due-state behavior
treat it as a real progress surface, not an appendix
Burnout prevention, snooze behavior, and recovery states matter as much as rewards. These should be visible states, not hidden backend flags.
Normal Mode
Full plan visible. Required and optional work both available.
Streak activeRewards normal
Catch-up Mode
Missed required work creates a bounded comeback path. Backlog is capped.
Recovery firstBacklog cap: 2
Low-Pressure Mode
Reduced obligation density for overload, exam week, illness, or stress.
Simplified planReminder tone softened
Rest Mode
Recovery window that protects learners from collapse while preserving history and identity.
No punishment toneReturn path ready
Urgency States
NewActiveDue soonOverdueStale
Overdue and stale should become more visible, but not emotionally aggressive. Use structure, highlighting, and recovery wording rather than shame.
Snooze vs Pause vs Rest
Snooze: move one task out of today's immediate queue
Pause: temporarily suppress due pressure for a chosen area
Rest: broader recovery state protecting streak logic and mental load
Completion Validation and Event Flow
A progress tracker breaks if it rewards empty clicks. The backend must validate what actually counts, and the UI must make that logic legible to the learner and to adults monitoring them.
1. Activity Event
Module emits start, step, retry, or completion event.
2. Validation Layer
Check duplicate request IDs, completion rules, required thresholds, and valid state transitions.
{
"digest_id": "dig_8112",
"learner_id": "learner_102",
"audience_type": "parent",
"overall_status": "strong_effort_weak_mastery",
"summary_text": "The learner is showing up, but weak-word recovery is lagging behind new vocabulary exposure.",
"recommended_next_action": "Review 5 Word List items before optional speaking practice.",
"weak_surface_list": ["word_list", "scenario_role_play_transfer"]
}