User Capability Map — Dec 18, 2025

QuranFlow User Capability Map

Version: 1.1 Date: December 18, 2025 Purpose: Comprehensive mapping of user functionality for app redesign

Document Purpose

This document maps what users need to do in QuranFlow, independent of the current app structure. It serves as the foundation for redesigning the app from first principles.

How to use this document:

1. Each "Task" is a discrete piece of functionality users need
2. Tasks can be regrouped into any screen/navigation structure
3. "Required Capabilities" describe what the system must enable
4. Problems and gaps inform redesign priorities
5. Priority tags indicate importance for MVP planning

Priority Tags:

Scope: Year 1 (Levels 1-4) and Year 2 student experiences

Section 1: User Context & Framing

1.1 Year 1 Student Profiles

QuranFlow Year 1 ("Essentials") spans four progressively advanced levels:

Common characteristics:

• Adult learners with busy schedules
• Range from complete beginners to those refining existing skills
• Need flexibility (minimum 30 min/week, ideal 1-2 hours)
• Many are older users (accessibility consideration)
• Some have learning disabilities or executive function challenges
• Many don't read emails/manuals (need in-app guidance)

1.2 Year 2 Student Profile

Year 2 ("Advanced") is for graduates of Level 4 who want to continue. Key differences:

• No weekly submissions (that learning mode is complete)
• Focus on appointments (1:1 sessions with TAs)
• Elective-based curriculum
• Different interaction patterns with Quran Coaches

1.3 Core Jobs-to-Be-Done

These high-level jobs frame why users engage with QuranFlow:

1.4 The Primary Problem: User Disorientation

From PM discussion, the #1 problem is user disorientation:

"Students struggle to understand where they are in the program, what they should be doing, and when things happen."

Manifestations:

• Students email asking "when does semester start?" despite receiving 5+ emails
• Students don't know which week they're on
• Students don't find their schedule (hidden behind 5 clicks)
• Students miss live classes they intended to attend
• Students don't discover key features (font settings, recordings, archives)
• Students feel lost in first 2 weeks and some give up

Root causes:

1. People don't read emails/manuals
2. Critical information not surfaced in-app
3. No clear visual orientation (current week, current status)
4. Steep learning curve with multiple concurrent activities
5. Key features hidden in non-intuitive locations

Design implication: The redesign must make the app "foolproof" - even users who read nothing should be able to understand what to do and when.

Section 2: Pre-Semester Phase

Timeframe: Sign-up (~2 weeks before semester) through Day 1 of semester

Activity 2A: Enroll in Program

Task 2A.1: Sign up for program [Core]

Current State: External sales page, not in-app

Problems Identified:

• N/A (external to app scope)

Required Capabilities:

• Account creation
• Payment processing
• Credential delivery (email with login)

Task 2A.2: Complete initial assessment [Core]

Current State: After login, student sees assessment screen with record button. Records reading sample, submits.

Problems Identified:

• None identified in audit (seems to work)

Required Capabilities:

• Display assessment prompt/instructions
• Audio recording
• Playback for review before submit
• Submit to Quran Coach queue
• Confirmation of successful submission

Task 2A.3: Receive level placement [Core]

Current State: Within 48 hours, student receives audio feedback in-app with level placement and assigned Coach.

Problems Identified:

• Notification reliability issues (may not reach student)
• Student level shown only in hamburger menu (hard to find)
• TA assignment only visible in hamburger menu

Required Capabilities:

• Deliver placement notification (in-app + push)
• Display assigned level prominently
• Display assigned Quran Coach prominently
• Audio feedback playback

Task 2A.4: Know who my Quran Coach is [Supporting]

Current State: TA name shown in hamburger menu (left icon)

Problems Identified:

• Hidden in hamburger menu - users would never think to check (Audit P1)
• No photo or introduction
• No way to communicate directly with TA

Required Capabilities:

• Display TA name/photo prominently
• Brief TA introduction/bio
• Direct communication channel to TA

Activity 2B: Understand the Program

Task 2B.1: Understand program structure [Supporting]

Current State: Explained in emails, not clearly in app. Orientation session on Sunday before semester.

Problems Identified:

• People don't read emails (PM Discussion)
• No in-app walkthrough or tutorial
• Orientation session is live-only, not recorded/accessible
• Tutorials section exists but unclear what it contains

Required Capabilities:

• In-app orientation content (video walkthrough)
• Explain: weekly cycle, submissions, live classes, QRCs
• Explain: what's required vs optional
• Accessible anytime (not just live session)

Task 2B.2: Know when semester starts [Core]

Current State: Communicated via email only. No in-app countdown or date display.

Problems Identified:

• Critical information missing from app (PM Discussion - top priority)
• Students email asking when semester starts despite receiving 5 emails
• No visual countdown or date indicator

Required Capabilities:

• Display semester start date prominently
• Countdown timer to semester start
• Clear visual state: "Pre-Semester" vs "Semester Active"

Task 2B.3: Understand my weekly schedule [Core]

Current State: Hidden in Resources → External Google Calendar link. Previously was PDF (got outdated).

Problems Identified:

• 5 clicks to access schedule (PM Discussion - top 3 priority)
• External link, not native experience
• PDF solution failed (outdated when changes made)
• Live tab exists but unused - wall of text, confusing
• Timezone ambiguity

Required Capabilities:

• Weekly schedule in calendar format
• Native in-app experience (not external link)
• Auto-updates when schedule changes
• Local timezone conversion with clear indicator
• Easy access (not buried in resources)

Task 2B.4: Explore available resources [Supporting]

Current State: Resources section in hamburger menu with ~15 items

Problems Identified:

• No hierarchy or organization (PM Discussion)
• Essential items mixed with supplementary
• Students must dig through everything
• External links for schedule

Required Capabilities:

• Organized resource categories
• Visual hierarchy (essential vs supplementary)
• Search/filter resources
• Clear labels and descriptions

Activity 2C: Pre-Semester Engagement

Task 2C.1: Attend pre-semester live sessions [Enhancement]

Current State: "Housewarming" sessions available before semester starts

Problems Identified:

• Students may not know these exist
• Part of disorientation - sessions happening but unclear what they are

Required Capabilities:

• Show pre-semester sessions clearly
• Differentiate from semester sessions
• Explain purpose of each session type

Task 2C.2: Receive welcome materials [Supporting]

Current State: Level notes/binder sent separately, welcome package in Resources

Problems Identified:

• Physical materials separate from app
• Digital welcome package not prominent

Required Capabilities:

• Consolidated welcome experience
• Clear access to all starter materials
• Checklist of what to do before semester starts

Section 3: Weekly Learning Cycle

Timeframe: Repeats for 15 weeks during semester Core rhythm: Lesson → Practice → Submit → Feedback → Live Sessions → Repeat

Activity 3A: Complete Weekly Lesson

Task 3A.1: Know which week I'm on [Core]

Current State: Not explicitly shown. Must infer from "8 out of 15 submissions unlocked" or count completed lessons.

Problems Identified:

• No explicit "Week X" indicator (PM Discussion - causes disorientation)
• Students must calculate current week themselves
• "8 out of 15" doesn't translate to "Week 8" for many users

Required Capabilities:

• Prominent "Week X of 15" display
• Current week highlighted in all relevant contexts
• Clear visual of where student is in semester

Task 3A.2: Access this week's lesson [Core]

Current State: Lessons tab shows list, current week unlocked

Problems Identified:

• Loading screen between navigation (dated - Audit P2)
• No indication of what lesson covers (topic, objectives)
• Very minimal interface with no context

Required Capabilities:

• Quick access to current week's lesson
• Lesson metadata (topic, learning objectives, duration)
• Pre-caching to eliminate load screens

Task 3A.3: Watch instruction videos [Core]

Current State: Vimeo-based player in lesson detail

Problems Identified:

• Video playback failure (Audit P0) - buffers, can't play on slower connections
• Defaults to 1080p, no adaptive bitrate
• Player doesn't feel native to iOS
• Full-screen requires 2 taps with small button (Audit P1)
• Excessive padding, not using full width
• Generic thumbnails, not descriptive

Required Capabilities:

• Reliable video playback with adaptive bitrate
• Native iOS player behavior (or equivalent)
• Single-tap full-screen with large touch target
• Full-width video display
• Descriptive thumbnails per video
• Subtitles/captions support

Task 3A.4: Track progress within multi-video lessons [Supporting]

Current State: Some lessons have 5-7 videos. No indication of which videos watched.

Problems Identified:

• No per-video watch tracking (PM Discussion)
• Students forget where they left off
• Have to rewatch to find their place
• No resume from last position

Required Capabilities:

• Track watched status per video in lesson
• Visual indicator (checkmark, progress bar)
• Resume from last position
• Clear "continue where you left off"

Task 3A.5: Mark lesson complete [Supporting]

Current State: "Mark Complete" button at end of lesson

Problems Identified:

• One-way action - cannot unmark (Audit P1)
• Violates reversibility principle
• No confirmation dialog

Required Capabilities:

• Mark complete functionality
• Ability to unmark/undo
• Or: auto-complete based on video watch progress

Task 3A.6: Access previous levels' content [Enhancement]

Current State: All levels (1-4) shown side-by-side in Lessons tab

Problems Identified:

• No visual separation between current level and historical (PM Discussion)
• Confusing - seems like all are equally relevant
• No clear hierarchy

Required Capabilities:

• Clear separation: current level vs previous levels
• Previous levels accessible but de-emphasized
• Visual hierarchy showing what's current

Activity 3B: Submit Weekly Recording

Task 3B.1: Know what to submit [Core]

Current State: Submissions tab shows current submission with lesson name

Problems Identified:

• Good: shows lesson name clearly
• Missing: what passage to recite (unless you view the recording screen)
• Unclear submission numbering ("Submission 2" vs "Week 2")

Required Capabilities:

• Clear identification of current week's submission
• Preview of what needs to be recited
• Consistent terminology (Week X, not "Submission X")

Task 3B.2: View Quranic text to recite [Core]

Current State: Recording screen shows Arabic text of passage

Problems Identified:

• Non-standard Quranic font (Audit P0) - not mushaf script by default
• Proper font exists but hidden in Settings (hamburger menu)
• Should be part of onboarding but isn't
• Font rendering errors even with correct font

Required Capabilities:

• Mushaf-standard font as DEFAULT
• Clear, readable Arabic text
• Font selection easily accessible
• Font selection in onboarding flow
• Pixel-perfect rendering

Task 3B.3: Record my recitation [Core]

Current State: Start Recording button, clear recording interface

Problems Identified:

• No indication of attempt limits
• No explanation of how recording works
• Unclear green dot indicator
• No guidance on what makes a good submission

Required Capabilities:

• Clear recording interface
• Recording instructions/tips
• Attempt limit display (if applicable)
• Visual feedback during recording
• Audio level indicator

Task 3B.4: Review recording before submitting [Core]

Current State: Review and re-record functionality available

Problems Identified:

• This works well (Audit: "excellent")
• Play button and submit button close together

Required Capabilities:

• Playback of recording
• Clear re-record option
• Visual distinction between play and submit

Task 3B.5: Submit to Quran Coach [Core]

Current State: Submit button sends to assigned TA

Problems Identified:

• Accidental submissions common (PM Discussion) - students press submit when trying to play
• No confirmation dialog
• No undo once submitted
• Contradictory turnaround messages: "5 business days" vs "2 business days" (Audit P1)

Required Capabilities:

• Submit confirmation (double-check intent)
• OR: Ability to retract before TA reviews
• Clear, consistent turnaround expectation
• Success confirmation with next steps

Task 3B.6: View submission history [Supporting]

Current State: Completed submissions move to different section. Archives exist but hard to navigate.

Problems Identified:

• Missing submission history (Audit P0) - past submissions not easily visible
• Submissions and feedback in different places
• Archive navigation tedious (filter by month, year)
• Completed submissions separated from pending unnaturally

Required Capabilities:

• Unified submission history view
• All submissions in one place (pending, completed, archived)
• Easy chronological navigation
• No complex filtering required for recent items

Task 3B.7: Understand submission limits [Supporting]

Current State: Message says "2 submissions per 7-day period"

Problems Identified:

• Slightly awkward phrasing
• Good that limit is communicated

Required Capabilities:

• Clear submission limit display
• Current count vs limit (e.g., "1 of 2 used this week")
• Reset timing clear

Activity 3C: Receive and Review Feedback

Task 3C.1: Know when feedback is ready [Core]

Current State: Notification appears, status changes to show feedback available

Problems Identified:

• Broken notifications (Audit P0) - notification says "submission rejected" with no: timestamp, date, which submission, reason
• Cannot act on notification - completely fails purpose
• May not receive push notification at all

Required Capabilities:

• Clear notification: which submission, when submitted, what status
• Deep link to specific submission
• Push notification + in-app indicator
• Notification history

Task 3C.2: Listen to TA audio feedback [Core]

Current State: Audio feedback accessible in Feedback section

Problems Identified:

• Feedback hard to find (PM Discussion)
• "Feedback" button initially interpreted as "give feedback" not "view feedback"
• Audio playback works but navigation to it is confusing

Required Capabilities:

• Clear "View My Feedback" labeling
• Audio playback controls
• Feedback linked directly to submission (same screen)

Task 3C.3: Ask follow-up questions [Supporting]

Current State: Comment section below feedback allows typing questions

Problems Identified:

• Typing interface broken - text pushes left, can't see what you typed (PM Discussion)
• No notification to TA when student posts comment
• Hyperlinks don't work in comments
• Posts don't appear until refresh

Required Capabilities:

• Functional text input
• TA notification when student asks question
• Link support
• Real-time update (no refresh needed)

Task 3C.4: Access feedback history/archives [Supporting]

Current State: Archives section with month/year filters

Problems Identified:

• Tedious filter system (PM Discussion)
• Must remember dates from previous semesters
• Multi-semester students have lots of history to dig through

Required Capabilities:

• Chronological list without complex filtering
• Level/semester grouping
• Search by date range (optional, not required)
• Recent feedback easily accessible

Activity 3D: Attend Live Sessions

Task 3D.1: See my weekly schedule [Core]

Current State: Live tab shows sessions, Resources has Google Calendar link

Problems Identified:

• Live tab is wall of text, students don't use it (PM Discussion)
• Schedule hidden behind 5 clicks in Resources
• No calendar view in-app
• 38-hour lookahead is arbitrary

Required Capabilities:

• Calendar/schedule view in-app
• Weekly layout with time blocks
• Filter by session type
• Easy access (prominent, not buried)

Task 3D.2: Understand session types [Supporting]

Current State: Sessions labeled (Level Class, QRC, Office Hours) but not explained

Problems Identified:

• New students don't understand differences
• All sessions look the same visually
• No explanation of what each type offers

Required Capabilities:

• Clear session type labels
• Brief description of each type
• Visual differentiation
• Recommendation of which to attend

Task 3D.3: Know timezone/timing [Core]

Current State: Times shown (e.g., "6 am Friday") with unclear timezone

Problems Identified:

• No timezone display (Audit P0)
• Unclear if converted to user's local time
• Same session could be different day for different users
• Critical for international student base

Required Capabilities:

• All times in user's local timezone
• Clear timezone indicator
• Or: explicit "in your timezone" label
• Handles day-boundary conversions

Task 3D.4: Join a live session [Core]

Current State: Click session to access Zoom link

Problems Identified:

• "Not yet available" message with no explanation (Audit P1)
• Some sessions clickable, others not - inconsistent
• No clarity on when session becomes joinable

Required Capabilities:

• Clear join button when session is live/about to start
• Explain "not yet available" with countdown
• Direct launch to Zoom
• Status indicator (upcoming, live now, ended)

Task 3D.5: Add session to personal calendar [Supporting]

Current State: Not available as native feature

Problems Identified:

• No calendar integration (Audit P1)
• Students must manually track sessions
• Likely to miss sessions they intended to attend

Required Capabilities:

• "Add to Calendar" button
• Generate .ics file or direct calendar integration
• Include session details in calendar event

Task 3D.6: RSVP/indicate intent to attend [Enhancement]

Current State: Does not exist

Problems Identified:

• No RSVP system (Audit P1)
• Instructors don't know expected attendance
• Students can't commit/track which they'll attend

Required Capabilities:

• RSVP/bookmark functionality
• Personal "my sessions" list
• Optional: instructor sees interest count

Activity 3E: Access Recorded Sessions

Task 3E.1: Find recordings of missed sessions [Supporting]

Current State: Recordings section in hamburger menu with filter system

Problems Identified:

• Not documented in original audit - discovered in PM Discussion
• Filter system frustrating (year, month selection)
• Memory-dependent (must remember when things happened)
• Up to 20 sessions per week to sift through
• Important feature but hidden

Required Capabilities:

• Recordings easily accessible (not buried in menu)
• Chronological list (recent first)
• Session type labels
• Date/time information

Task 3E.2: Filter/search recordings [Enhancement]

Current State: Filter by month, year

Problems Identified:

• Filter UX is tedious (PM Discussion)
• No filter by session type
• No filter by instructor
• No search

Required Capabilities:

• Filter by: type (QRC, Level Class), instructor, date range
• Or: simple list that doesn't need filtering
• Search by keyword (optional)

Task 3E.3: Watch recorded session [Supporting]

Current State: Playback available

Problems Identified:

• Playback glitches since backend clone (PM Discussion)
• Navigation doesn't update, have to exit and re-enter
• No resume from where left off

Required Capabilities:

• Reliable playback
• Resume position
• Playback controls (speed, skip)

Activity 3F: Track Progress

Task 3F.1: See overall progress in level [Supporting]

Current State: Progress circle with percentage in top header

Problems Identified:

• Shows "9%" with no clear indication of what it represents (Audit P1)
• Both circle AND bar shown (redundant - Audit P2)
• "QR Progress" branding (should be QuranFlow - Audit P2)
• Overall design described as "ugly and redundant"

Required Capabilities:

• Clear progress metric with label ("X of Y lessons completed")
• Single, clear visualization
• Current level context

Task 3F.2: See detailed statistics [Enhancement]

Current State: Progress screen shows quizzes, lessons, submissions counts

Problems Identified:

• Cryptic statistics (Audit P2) - "0/0 quizzes, 2/7 lessons, 0/15 something"
• No clear category labels
• No access to feedback/grades from progress screen (Audit P0)
• Icons misaligned

Required Capabilities:

• Clear labels for all metrics
• Access to feedback history from progress view
• Grades/performance trend over time
• Clean, organized display

Section 4: End of Semester Phase

Timeframe: Final weeks of 15-week semester

Activity 4A: Complete Final Assessment

Task 4A.1: Complete end-of-course assessment [Core]

Current State: Final submission called "End of Course Assessment" combining all concepts

Problems Identified:

• Not specifically documented in audit
• Likely same issues as regular submissions

Required Capabilities:

• Clear EOC assessment availability
• Instructions specific to EOC
• Recording/submission same as weekly
• Confirmation of completion

Task 4A.2: View final results [Core]

Current State: Receive feedback on EOC, determine graduation status

Problems Identified:

• Not specifically documented
• Need 12 submissions + successful EOC to graduate

Required Capabilities:

• Clear results communication
• Pass/fail status
• Feedback on EOC
• Graduation confirmation

Activity 4B: Transition to Next Level

Task 4B.1: Graduate to next level [Core]

Current State: Promoted by admin, welcomed to new level

Problems Identified:

• Not specifically documented from student perspective

Required Capabilities:

• Graduation notification
• New level access
• Updated TA assignment (if changed)
• New semester onboarding

Task 4B.2: Transition from Level 4 to Year 2 [Supporting]

Current State: Level 4 graduates eligible for Year 2, must explicitly sign up

Problems Identified:

• Separate enrollment process
• Different experience (appointments vs submissions)

Required Capabilities:

• Clear Year 2 information
• Enrollment pathway
• Explanation of how Year 2 differs

Section 5: Year 2 Differences

Context: Year 2 ("Advanced") is for Level 4 graduates. Different learning model.

5.1 Overview

Activity 5A: Book Appointments

Task 5A.1: View available appointment slots [Core]

Current State: Appointments section exists for Year 2

Problems Identified:

• Not yet audited in detail
• Year 2 credentials provided for testing but not yet explored

Required Capabilities:

• View TA availability
• See time slots in local timezone
• Understand appointment types

Task 5A.2: Book an appointment [Core]

Current State: Booking system exists

Problems Identified:

• Not yet audited

Required Capabilities:

• Select time slot
• Confirm booking
• Receive confirmation
• Add to calendar

Task 5A.3: Manage appointments [Supporting]

Current State: Unknown

Problems Identified:

• Not yet audited

Required Capabilities:

• View upcoming appointments
• Reschedule if needed
• Cancel if needed
• Join appointment (Zoom)

Section 6: Cross-Cutting Capabilities

These capabilities span multiple phases and activities.

Activity 6A: Manage Profile & Account

Task 6A.1: View/edit profile information [Supporting]

Current State: Profile screen (right icon) shows minimal info: email, phone field

Problems Identified:

• Inadequate profile screen (Audit P0) - missing critical info
• No category headings or labels
• No billing, payment, subscription info
• No learning history, achievements
• Design described as "ridiculous" and "fail"
• Can't upload photo from gallery, only take selfie (PM Discussion - broken)

Required Capabilities:

• Personal info (name, email, phone)
• Profile photo (upload from gallery)
• Account & subscription info
• Billing & payment history
• Learning history (past levels, grades)
• Achievements
• Proper section labels

Task 6A.2: Change password [Supporting]

Current State: Inline "fill these fields if you want to change password" on profile

Problems Identified:

• Ad-hoc implementation
• No standard settings flow

Required Capabilities:

• Password change in settings
• Current password verification
• Confirmation flow

Activity 6B: Configure Settings

Task 6B.1: Set Quranic text font [Core]

Current State: Font selector in Settings (hamburger menu)

Problems Identified:

• Font setting not discoverable (Audit P0)
• Hidden in hamburger menu → Settings
• Not part of onboarding
• Critical feature invisible to users
• Some rendering errors even with correct font

Required Capabilities:

• Font selection (mushaf vs simplified)
• Default to proper mushaf font
• Include in onboarding flow
• Easy access to change later

Task 6B.2: Manage notifications [Core]

Current State: Notifications setting exists

Problems Identified:

• Notification system itself is broken
• Settings may work but notifications don't reach users

Required Capabilities:

• Push notification toggle
• Email notification preferences
• Notification types (feedback ready, upcoming session, etc.)
• Working notification delivery

Task 6B.3: Adjust display settings [Enhancement]

Current State: Enlarge font option exists (not currently active)

Problems Identified:

• Font enlargement disabled
• Some elderly users requested larger text
• Tension: smaller text preferred but accessibility needed

Required Capabilities:

• Text size adjustment
• Accessibility options
• Device font size respect

Activity 6C: Get Help & Support

Task 6C.1: Access support/help [Supporting]

Current State: Support button in hamburger menu only

Problems Identified:

• Support well-hidden (Audit P1)
• No obvious path to help
• Three support categories: General, Tech, Billing
• No "contact my TA" option

Required Capabilities:

• Prominent help access
• Multiple contact channels
• FAQ/self-help content
• Route to appropriate team

Task 6C.2: Contact my TA directly [Supporting]

Current State: Not possible in-app. Must email coaches@quranflow.org

Problems Identified:

• No 1:1 TA communication (PM Discussion)
• Students use submission recordings to communicate (keep talking after recitation)
• Email address must be known from external communication
• App provides no direct channel

Required Capabilities:

• In-app TA messaging
• Or: easy email to coaches@ from app
• Clear path to reach assigned TA

Activity 6D: Community Interaction

Task 6D.1: View community board/announcements [Enhancement]

Current State: Conversations feature on home screen

Problems Identified:

• Conversations purpose unclear (Audit P1)
• Confusion: is it messages, complaints, TA communication, FAQ?
• Redundant UI (button + chat bubble - Audit P2)
• Lacks vision (PM Discussion) - unclear who's in the board
• See students from different levels/groups
• Gender segregation confusion
• Categories (Question, Tech Issue) suggest support

Required Capabilities:

• Clear purpose definition
• Appropriate membership (who can see what)
• Announcement broadcasting from TAs
• Proper categorization
• Or: reconsider if this feature is needed at all

Task 6D.2: Post to community board [Enhancement]

Current State: Can select category and type message

Problems Identified:

• Typing interface broken (text pushes left - PM Discussion)
• Hyperlinks don't work
• Posts don't appear until refresh
• TAs don't get notifications
• Overlap with support creates confusion

Required Capabilities:

• Functional text input
• Real-time posting
• Working links
• Notification to relevant parties

Activity 6E: Navigate the App

Task 6E.1: Understand app structure [Core]

Current State: Top tabs (Home, Lessons, Submissions, Live), hamburger menu, profile icon

Problems Identified:

• Non-standard navigation (Audit P2) - iOS standard is bottom tabs
• Hamburger menu deprecated pattern
• Hidden features (recordings, support, TA info)
• Mix of top tabs + hamburger + buttons confusing

Required Capabilities:

• Clear navigation structure
• iOS-standard patterns (bottom tab bar)
• Key features not hidden
• Consistent information architecture

Task 6E.2: Receive and act on notifications [Core]

Current State: Bell icon for notifications

Problems Identified:

• Broken notification content (Audit P0)
• No timestamp, date, context, deep link
• Cannot act on notification information
• Notification history unclear

Required Capabilities:

• Rich notifications with full context
• Deep links to relevant content
• Notification history/log
• Clear, actionable information

Section 7: Gap Analysis Summary

7.1 P0 Gaps (Blocking Core Functionality)

7.2 Capability Gaps (Things That Don't Exist)

7.3 Discoverability Gaps (Things That Exist But Are Hidden)

7.4 Design Gaps (Things That Exist But Work Poorly)

7.5 The Disorientation Problem - Summary

The core problem maps to these specific gaps:

Appendix A: Source Reference

Appendix B: Current Screen Inventory (Reference)

From audit, these screens currently exist:

1. Home (tab)
2. Lessons (tab)
3. Submissions (tab)
4. Live Sessions (tab)
5. Lesson Detail
6. Recording Interface
7. Progress/Stats (top-right circle)
8. Notifications (bell icon)
9. User Profile (top-right user icon)
10. Side Menu (hamburger)
11. Settings (in side menu)
12. Support (in side menu)
13. Feedback History (in side menu)
14. Resources (in side menu)
15. Recordings (in side menu)

Note: This inventory is for reference only. The capability map above is intentionally structure-agnostic to enable reorganization.

Appendix C: Using This Document for Redesign

Card Sorting Exercise

Each Task in Sections 2-6 is a "card" that can be:

1. Grouped with related tasks
2. Assigned to screens/sections
3. Prioritized for MVP vs later releases

Suggested Process

1. List all tasks on cards (physical or digital)
2. Remove duplicates and merge related items
3. Group by user mental model (not current structure)
4. Name the groups - these become your new navigation
5. Validate - does this address the disorientation problem?

Key Questions for Redesign

• Does the home screen answer: "What week am I on? What should I do today?"
• Can users find their schedule in <2 taps?
• Is feedback accessible from the submission it relates to?
• Can new users understand the app without reading a manual?
• Are all critical features (font, support, recordings) in primary navigation?

End of Document