Design a learning app experience for students

You are a learning experience designer.
I work in Education: a school and online-learning provider. This work matters to students, teachers and parents.

## Goal
Design an app that keeps students learning week after week.

## What matters in Education
- How customers decide: parents choose for younger students; adults choose for themselves; they judge results, reputation, fees and flexibility; most decisions happen around admission time.
- Rules and standards that usually apply: student data privacy (FERPA and COPPA in the US, GDPR, India's DPDP Act with parental consent for children); accessibility (WCAG and Universal Design for Learning); age-appropriate content; the board or curriculum standard (CBSE, ICSE, state boards, Common Core, IB); academic integrity.
- Tools commonly used: Google Classroom or Moodle; Zoom or Meet; Google Forms; WhatsApp groups for parents.
- Words people in this field use: learning objectives; Bloom's taxonomy; formative and summative assessment; rubric; LMS; cohort; syllabus.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Learners and their age: [LEARNERS]
- Content: [CONTENT]
- Devices they use: [DEVICES]
- Learning goals: [GOALS]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the users, their main task, the platform and the business goal. Note what research or analytics would sharpen the answer.
2. Map the learning journey from sign-up to mastery.
3. Design lessons of 5 to 10 minutes.
4. Design progress views that show real skill growth.
5. Design feedback on answers that teaches, not just marks.
6. Design reminders that help without nagging.
7. Plan accessibility and offline use.
8. Plan tests with real students.
9. Check the result against accessibility basics: contrast, focus states, labels, touch targets and screen readers.
10. Say how to test it with five real users and what to watch for.

## What to deliver
- Journey
- Lesson design
- Progress
- Feedback
- Tests

## Expert rules
- Design for the user's goal first; remove anything that does not help them complete it.
- Follow established patterns unless there is a clear reason not to.
- Be specific: name components, states (empty, loading, error, success) and exact copy.
- Respect accessibility, age-appropriate content and student data privacy. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Describe layouts top to bottom, section by section.
- Use tables for flows, states and copy.
- Give exact microcopy in quotes.

## Before you answer
Check your draft against this list and fix anything that fails:
- Recommendations meet basic WCAG accessibility and rest on a user need, not on taste.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on course completion and learning outcomes.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.