Build your own Headspace.

# Build an original app inspired by Headspace

You are an experienced mobile product designer and mobile engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: iOS. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original iOS meditation companion called Stillroom, inspired by Headspace. It is for adults choosing short original mindfulness recordings and keeping a personal practice routine. The core journey is selecting a session, listening with working controls, finishing or resuming it, and reviewing actual practice history. Deliver a native SwiftUI project with licensed or original audio; an attractive player with no playable media is incomplete.

## Design
Use an original soft palette, generous space, simple session cards, and a focused player with large play/pause and seek controls. Explain session length and whether audio is downloaded. Provide VoiceOver playback labels, Dynamic Type, reduced motion, and readable transcripts. Avoid a compulsory onboarding funnel; let someone try a bundled session immediately.

## Features
1. Session library: offer a small collection of original breathing, focus, and unwind recordings with descriptions, durations, and transcripts. Browse by theme and favorite sessions. Keep licensed asset provenance alongside the content and never reuse commercial recordings.

2. Audio playback: play, pause, seek, and resume from a durable position. Support headphones, lock-screen controls, interruption handling, and route changes. Pause or resume according to a documented policy after a call, rather than unexpectedly restarting audio.

3. Offline listening: bundle at least one usable recording; allow downloading permitted remote files with progress, cancellation, disk-space checks, and explicit removal. Show available offline sessions and an actionable failed-download state.

4. Practice history: record listening time from real playback, mark completion using a documented threshold, and show a calendar plus recent sessions. Replaying or scrubbing to the end must not invent minutes practiced. Let users delete personal history.

5. Routine: offer a configurable reminder only after someone opts in, with a useful fallback when notification permission is denied. A simple silent breathing timer can accompany the audio, but must respect background transitions and reduced motion.

## Tech stack
Use Swift, SwiftUI, AVFoundation/AVAudioSession, MediaPlayer, UserNotifications, and a suitable native persistent store such as SwiftData. Include the Xcode project, deployment target, audio background-mode configuration, and runnable bundled assets. Keep playback, downloads, and practice accounting separate from views. Reuse a compatible native repository when present; do not substitute a website or WebView. A local edition needs no cloud account, analytics, microphone access, or paid wellness API.

## Data & behavior
Session {id, title, theme, duration, audioSource, transcript, license}; Favorite; AudioDownload {sessionId, localURL, state, bytes}; PlaybackCheckpoint {sessionId, positionSeconds}; PracticeRun {id, sessionId, startedAt, actualListeningSeconds, completedAt}; ReminderPreference. Store downloads in app-managed files and history locally, use monotonic playback intervals for accounting, and save checkpoints during interruptions. Remove broken file references after failed writes without deleting previous usable downloads.

Acceptance checks and scope:
Play an original five-minute recording, seek, unplug headphones, background/lock the phone, and resume after app relaunch. Verify counted minutes follow real playback, test offline playback, interrupted/canceled downloads, disk exhaustion, and denied notifications. Build in Xcode and test audio behavior on a device when possible; state simulator limits. Exclude copied narration, therapy or diagnosis, mood inference, medical outcome promises, subscription billing, social groups, and cloud synchronization.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.