Mobile App UX Flow Architect

=== MOBILE APP UX FLOW ARCHITECTURE ===

App
PulsePath

Platforms
iOS and Android

Primary User
An adult seeking guided home workouts and consistent habit support.

Primary User Job
Choose an appropriate fitness plan, complete workouts, track progress, and maintain a sustainable routine.

Primary Business Goal
Improve first-week activation and convert qualified users into recurring subscribers.

Activation Moment
Complete the first guided workout and schedule the next workout.

=== EXECUTIVE SUMMARY ===

PulsePath should prioritize first value before subscription pressure.

The recommended primary journey is

First Launch
→ Brief Value Introduction
→ Goal and Experience Setup
→ Starter Workout Recommendation
→ Limited Workout Preview
→ Account Creation Before Permanent Progress Saving
→ First Guided Workout
→ Completion Feedback
→ Schedule Next Workout
→ Contextual Notification Request
→ Home
→ Trial or Subscription Offer at a relevant value moment

The app should avoid

• Long feature tours
• Signup before users understand the value
• Multiple permission prompts at first launch
• An overloaded home screen
• Paywalls without transparent terms
• Streak-based emotional pressure
• Hidden cancellation
• Unsupported offline claims

=== USER ROLES ===

Guest

• View value proposition
• Browse sample workouts
• Preview programs
• View verified pricing
• Complete one introductory workout
• Cannot permanently save progress

Registered User

• Save workouts
• Save progress
• Schedule workouts
• Configure reminders
• Manage fitness preferences

Trial User

• Access verified trial features
• View trial status
• Manage subscription
• Receive transparent renewal information

Active Subscriber

• Access subscribed content
• Track progress
• Download content only if implemented
• Manage plan and billing

Expired Subscriber

• Retain verified account access
• View available free content
• Review reactivation options
• Manage account and data

Trainer

• Maintain an approved trainer profile
• Publish approved workout plans
• Exact publishing workflow requires verification

=== USER LIFECYCLE ===

1. First Open
2. Value Exploration
3. Goal Setup
4. Starter Plan Recommended
5. Introductory Workout
6. Account Created
7. First Workout Completed
8. Next Workout Scheduled
9. Activated
10. Trial or Subscription Considered
11. Subscriber
12. Retained
13. At Risk
14. Cancelled or Expired
15. Reactivated

=== FIRST-LAUNCH LOGIC ===

Fresh User
Value Introduction
→ Goal Setup
→ Experience Level
→ Workout Duration
→ Equipment
→ Starter Recommendation

Returning Signed-Out User
Welcome Back
→ Login
→ Restore Intended Destination

Returning Signed-In User
Session Restoration
→ Home or Active Workout

Incomplete Onboarding
Resume at the last verified saved step

Deep-Link Entry
Resolve link
→ Authenticate if required
→ Return to intended destination

Offline Entry
Explain that live content cannot be loaded
→ Show only verified locally available content
→ Do not imply full offline support

=== VALUE ONBOARDING ===

Screen 1:

Heading
Build a Routine That Fits Your Life

Purpose
Explain the core app value.

Primary Action
Choose My Goal

Secondary Action
Explore Sample Workouts

Screen 2:

Question
What would you like to focus on?

Options

• Build Strength
• Improve Mobility
• Increase Endurance
• Stay Consistent

Requirement
Use approved goal terminology.

Screen 3:

Question
What is your current experience level?

Options

• Beginner
• Intermediate
• Advanced

Screen 4:

Question
How much time do you usually have?

Options

• 10 Minutes
• 20 Minutes
• 30 Minutes
• 45 Minutes or More

Screen 5:

Question
What equipment is available?

Options

• No Equipment
• Resistance Bands
• Dumbbells
• Full Home Gym

Completion

Heading
Your Starter Plan Is Ready

Primary Action
Preview First Workout

Secondary Action
Adjust Preferences

=== ACCOUNT CREATION ===

Timing
After the starter recommendation and before permanent progress saving.

Reason
The user has already received product value and understands why an account is useful.

Methods

• Continue with Email
• Continue with Apple, where supported
• Continue with Google

Required States

• Loading
• Invalid credentials
• Expired code
• Existing account
• Provider conflict
• Network error
• Verification required
• Account created

Duplicate Account
If an email already exists under another approved method, explain the conflict and provide a verified linking or recovery path.

=== PERMISSION STRATEGY ===

Notifications

Trigger
After the user schedules the next workout.

Pre-Permission Message

Heading
Get a Reminder Before Your Next Workout

Body
Enable reminders so PulsePath can notify you at the scheduled time.

Primary Action
Enable Reminders

Secondary Action
Not Now

Denied State
The scheduled workout remains available.
Explain how to enable reminders later from Settings.

Health Data

Trigger
Only when the user opens the approved health integration feature.

Do Not
Request health access during general onboarding.

Camera

Trigger
When the user chooses to add a progress photo.

Alternative
Allow the user to continue without adding a photo.

=== HOME-SCREEN ARCHITECTURE ===

Priority Order

1. Continue Active Workout, when applicable
2. Today's Workout
3. Start Workout
4. Next Scheduled Workout
5. Weekly Progress
6. Recommended Plan
7. Recent Achievement
8. Subscription Status, only when relevant

New User Home

• Complete first workout
• Finish optional setup
• Learn how progress is tracked

Returning User Home

• Resume current activity
• Today's workout
• Weekly progress
• Next scheduled task

Subscriber Home

• Current plan
• Today's workout
• Progress
• Premium content recommendations
• Billing status only when action is required

=== NAVIGATION ARCHITECTURE ===

Bottom Tabs

Home
Current status, workout, progress summary, and next action.

Explore
Search workouts, programs, and trainers.

Progress
Workout history, trends, achievements, and goals.

Account
Profile, preferences, subscription, privacy, security, and settings.

Primary Workout Action
Starting a workout opens a focused full-screen task flow rather than a fifth tab.

Notifications
Accessible from the Home header.

Back Behavior

• Back navigates within the current stack.
• Close exits a modal or bottom sheet.
• Cancel stops a task without automatically deleting saved progress.
• Discard removes unsaved changes only after explicit confirmation.

=== PRIMARY WORKOUT FLOW ===

Entry Points

• Today's Workout
• Continue Workout
• Search Result
• Saved Workout
• Notification Deep Link

Flow

Workout Detail
→ Review Duration, Difficulty, Equipment, and Safety Information
→ Start Workout
→ Preparation
→ Exercise Step
→ Rest
→ Next Exercise
→ Pause or Resume
→ Complete Workout
→ Effort Feedback
→ Progress Saved
→ Schedule Next Workout
→ Completion

Interruption
When the app moves to the background, preserve the current step and elapsed state where supported.

Resume
Return to the active workout with a clear Continue action.

Exit
Confirm whether the user wants to pause, end, or discard the workout.

=== WORKOUT STATES ===

• Not Started
• Preparing
• Active
• Paused
• Backgrounded
• Resuming
• Completed
• Ended Early
• Save Pending
• Save Failed
• Offline Unconfirmed

Save Failure

Heading
We Could Not Confirm Your Progress

Body
Your workout result is still visible on this device. Reconnect and try saving again.

Use only if local preservation is verified.

=== SEARCH AND DISCOVERY ===

Search Scope

• Workouts
• Programs
• Trainers
• Goals
• Duration
• Difficulty
• Equipment

Required States

• Recent searches
• Suggestions
• Results
• Loading
• No results
• Filtered empty
• Error

Context Preservation
Keep the query, filters, and result position when the user opens a workout and returns.

=== SUBSCRIPTION FLOW ===

Entry Points

• Premium workout
• Usage or feature gate
• Subscription settings
• Contextual post-value offer
• Expired subscription state

Plan Comparison

• Monthly
• Annual
• Verified trial where applicable

Required Information

• Price
• Currency
• Billing cadence
• Trial terms
• Renewal
• Feature access
• Cancellation access
• Platform billing context

Primary Action
Start Verified Plan or Trial

Secondary Action
Continue With Available Access

Do not invent exact wording until commercial terms are verified.

=== SUBSCRIPTION STATES ===

• Eligible
• Trial Available
• Trial Active
• Active
• Renewal Upcoming
• Payment Processing
• Payment Failed
• Grace Period
• Cancelled With Access Remaining
• Expired
• Reactivation Available

Payment Uncertain

Heading
Confirming Your Subscription

Body
The payment result has not been confirmed yet. Do not submit another payment until the status updates.

=== CANCELLATION FLOW ===

Step 1:
Show current plan and verified billing status.

Step 2:
Explain the effective cancellation date and retained access.

Step 3:
Offer approved alternatives without blocking cancellation.

Step 4:
Confirm cancellation.

Step 5:
Show the verified outcome and reactivation path.

Do not

• Hide the final cancellation action
• Use emotional pressure
• Use misleading colors
• Require unnecessary support contact
• Invent data-loss consequences

=== NOTIFICATION SYSTEM ===

Workout Reminder
Opens the scheduled workout.

Plan Reminder
Opens the relevant plan or schedule.

Payment Notification
Opens subscription status.

Security Notification
Opens the verified security destination.

Signed-Out Deep Link
Authenticate
→ Restore link
→ Verify authorization
→ Open destination

Missing Workout
Show that the workout is no longer available and provide a relevant alternative.

=== SETTINGS ARCHITECTURE ===

Account

• Email
• Authentication methods
• Session management

Profile

• Display name
• Optional photo
• Fitness profile

Fitness Preferences

• Goal
• Experience
• Duration
• Equipment

Notifications

• Workout reminders
• Plan updates
• Billing
• Security
• Approved marketing preferences

Privacy

• Progress visibility
• Progress photos
• Health integrations
• Data controls

Subscription

• Current plan
• Billing status
• Change plan
• Cancellation
• Restore purchase where required

Security

• Password
• Biometrics
• Active sessions
• Two-factor authentication where supported

Accessibility

• Motion preference
• Audio guidance
• Caption or transcript support where relevant

Help

• Support
• FAQ
• Report a problem

Danger Zone

• Delete account

=== ACCOUNT-DELETION FLOW ===

1. Explain account and progress impact.
2. Explain subscription impact.
3. Offer approved data export where supported.
4. Confirm identity.
5. Capture optional reason.
6. Confirm deletion.
7. Show processing.
8. Confirm completion.
9. Explain verified retention or recovery behavior.

Do not invent recovery periods.

=== OFFLINE ARCHITECTURE ===

MVP
No full offline claim.

Supported Offline Behavior
Only verified cached content or temporary active-workout state.

Unsupported
Browsing the complete library
Starting new content that was not loaded
Completing live subscription actions
Guaranteed synchronization

Connection Restored
Retry pending verified actions and explain conflicts when necessary.

=== DEEP-LINK MATRIX ===

Workout Reminder
Scheduled Workout

Shared Workout
Workout Detail

Subscription Alert
Subscription Status

Password Reset
Reset Flow

Signed Out
Authenticate and return

Unauthorized
Explain the access restriction

Missing Object
Explain that the content is unavailable

Expired Link
Provide a safe replacement action

Offline
Preserve the destination and retry when connected where supported

=== ACCESSIBILITY REQUIREMENTS ===

• Accessible labels for all controls
• Logical screen-reader order
• Dynamic type
• Large touch targets
• Non-color workout states
• Reduced motion
• Accessible timers
• Accessible progress indicators
• Accessible modal and bottom-sheet focus
• Gesture alternatives
• Captioned or described workout media where applicable
• External-keyboard support where applicable
• Orientation review
• Safe-area support
• Screen-reader announcements for meaningful state changes
• No claim of conformance without testing

=== ANALYTICS EVENT MAP ===

Event
onboarding_started

Properties

• entry_source
• platform
• app_version

Event
onboarding_step_completed

Properties

• step_id
• elapsed_time_bucket
• platform

Event
first_workout_started

Properties

• workout_category
• duration_bucket
• source

Event
first_workout_completed

Properties

• workout_category
• completion_state
• scheduled_next_workout

Event
notification_permission_viewed

Properties

• trigger_context
• platform

Event
subscription_viewed

Properties

• source
• user_state
• plan_context

Event
subscription_started

Properties

• plan_type
• entry_source
• eligibility_state

Privacy
Do not send health details, progress photos, payment information, private profile data, raw location, passwords, or private messages into analytics.

=== EXPERIMENT ROADMAP ===

Experiment 1:
Account Creation Timing

Hypothesis
Showing the starter recommendation before account creation will improve qualified account creation.

Primary Metric
Account creation after starter-plan preview

Guardrail
First-workout completion

Experiment 2:
Notification Timing

Hypothesis
Requesting notifications after scheduling the next workout will increase qualified opt-in.

Primary Metric
Notification permission acceptance

Guardrail
Reminder disable rate

Experiment 3:
Post-Workout Subscription Entry

Hypothesis
Showing a transparent subscription offer after first value will improve qualified conversion.

Primary Metric
Subscription start after workout completion

Guardrails
Cancellation rate
Support contact
App abandonment

=== DEVELOPER HANDOFF ===

Required Navigation

• Root session router
• Authentication stack
• Onboarding stack
• Main tab navigation
• Full-screen workout stack
• Subscription stack
• Settings stack
• Deep-link router

Required State Domains

• Session
• Onboarding
• Account setup
• Permissions
• Workout
• Progress
• Subscription
• Notifications
• Settings
• Connectivity
• Deep links

Required Screens

• Startup
• Welcome
• Goal Setup
• Experience Setup
• Duration Setup
• Equipment Setup
• Starter Recommendation
• Authentication
• Verification
• Home
• Explore
• Search Results
• Workout Detail
• Active Workout
• Workout Completion
• Progress
• Subscription
• Notification Center
• Account
• Settings
• Security
• Delete Account

=== IMPLEMENTATION SEQUENCE ===

1. Confirm roles, business rules, and platform constraints.
2. Define session and first-launch routing.
3. Implement onboarding and authentication.
4. Implement account setup and contextual permissions.
5. Implement main navigation and home.
6. Implement the primary workout flow.
7. Implement progress and search.
8. Implement subscription states.
9. Implement notifications and deep links.
10. Implement settings, security, and deletion.
11. Implement error, offline, and interruption states.
12. Implement accessibility and localization.
13. Add analytics.
14. Complete functional, accessibility, payment, notification, deep-link, and device QA.

=== ACCEPTANCE CRITERIA ===

First Value

Given a new user opens PulsePath,
when onboarding begins,
then the user can understand the core value, configure a starter recommendation, and reach a first workout without completing unrelated profile fields.

Permission Timing

Given a user schedules the next workout,
when reminder value becomes relevant,
then PulsePath may explain and request notification permission.

Permission Denial

Given the user denies notification permission,
when the app continues,
then workout access remains available and the reminder setting can be revisited later.

Workout Interruption

Given an active workout is interrupted,
when the user returns,
then the app restores the verified saved workout state and provides a clear resume action.

Subscription Transparency

Given a user reviews a subscription,
when the plan screen appears,
then verified price, billing cadence, trial terms, renewal, limitations, and cancellation access are visible.

Payment Uncertainty

Given the app cannot confirm a payment result,
when the user returns from the payment provider,
then the app avoids duplicate submission and communicates that the status is being confirmed.

Deep-Link Recovery

Given a signed-out user opens a workout reminder,
when authentication completes,
then the app returns to the intended workout if it remains available and authorized.

Account Deletion

Given a user chooses account deletion,
when confirmation begins,
then the app explains verified data and subscription consequences before the final action.

=== REGRESSION TEST MATRIX ===

User States

• Guest
• New User
• Registered User
• Trial User
• Subscriber
• Expired Subscriber

Authentication

• Email
• Apple
• Google
• Existing Account
• Invalid Credentials
• Expired Code
• Network Error

Permissions

• Granted
• Limited
• Denied
• Permanently Denied
• Settings Recovery

Workout

• Not Started
• Active
• Paused
• Backgrounded
• Completed
• Save Failed

Subscription

• Eligible
• Trial Active
• Active
• Payment Failed
• Cancelled
• Expired
• Reactivated

Connectivity

• Online
• Offline
• Reconnecting
• Synchronization Pending
• Conflict

Accessibility

• Screen Reader
• Dynamic Type
• Reduced Motion
• Large Touch Targets
• Orientation
• External Keyboard where applicable

=== QA CHECKLIST ===

First Launch

• Verify fresh install.
• Verify returning user.
• Verify signed-out user.
• Verify incomplete onboarding.
• Verify deep-link entry.
• Verify offline entry.

Onboarding

• Verify required fields.
• Verify optional fields.
• Verify skip behavior.
• Verify resume behavior.
• Verify progress.
• Verify completion routing.

Authentication

• Verify every method.
• Verify errors.
• Verify recovery.
• Verify duplicate-account behavior.
• Verify deep-link return.

Permissions

• Verify contextual timing.
• Verify denial.
• Verify limited access.
• Verify settings recovery.
• Verify unrelated features remain available.

Navigation

• Verify tabs.
• Verify stacks.
• Verify modals.
• Verify Back behavior.
• Verify state preservation.
• Verify active-tab behavior.

Workout

• Verify start.
• Verify pause.
• Verify resume.
• Verify interruption.
• Verify completion.
• Verify failed save.
• Verify next scheduling.

Subscription

• Verify pricing.
• Verify trial.
• Verify payment states.
• Verify cancellation.
• Verify expiration.
• Verify reactivation.

Accessibility

• Verify labels.
• Verify reading order.
• Verify dynamic type.
• Verify touch targets.
• Verify reduced motion.
• Verify non-color status.
• Verify bottom sheets.
• Verify timers.
• Verify media alternatives.

=== RISKS ===

Risk
Users are asked to create an account before understanding the product.

Mitigation
Show the starter recommendation and limited introductory value before permanent account creation.

Risk
Notification permission is requested without context.

Mitigation
Request it only after the user schedules a workout.

Risk
Health data is requested too early.

Mitigation
Move health permissions into the optional integration flow.

Risk
Active workout progress is lost.

Mitigation
Define verified local state preservation and explicit resume behavior.

Risk
Subscription terms are unclear.

Mitigation
Show verified price, cadence, trial, renewal, limitations, and cancellation access.

Risk
Streak messaging creates unhealthy pressure.

Mitigation
Use supportive progress language and avoid punishment-based loss messaging.

Risk
Deep links lose the destination after authentication.

Mitigation
Preserve and validate the intended route through the authentication handoff.

=== KNOWN LIMITATIONS ===

• Authentication behavior requires technical verification.
• Account linking requires verified provider rules.
• Health-data integration requires privacy, security, platform, and legal review.
• Subscription behavior requires platform and payment validation.
• Offline behavior requires implementation testing.
• Notification delivery is not guaranteed.
• Deep links require platform testing.
• Accessibility requires real-device and assistive-technology testing.
• Analytics require implementation and privacy review.
• The architecture does not guarantee activation, conversion, retention, revenue, or lower churn.

=== FINAL INTEGRITY NOTE ===

All authentication, authorization, payments, subscriptions, trials, pricing, refunds, permissions, notifications, retention, deletion, legal disclosures, privacy statements, security behavior, and platform-specific rules must be verified before implementation.

The UX flow is designed to improve clarity, activation readiness, task completion, retention readiness, and implementation consistency. It does not guarantee conversion, retention, revenue, engagement, reduced churn, or reduced support volume.