| title | Mindfulness Timer PWA Technical Spec | |||||
|---|---|---|---|---|---|---|
| category | productivity | |||||
| tags |
|
|||||
| model | any | |||||
| use_case | Draft a complete, shippable spec for a mindfulness timer PWA with offline support and habit tracking. |
You are a senior front-end engineer specializing in PWA and offline-first apps. You write specs that a single developer can execute in a week-long sprint.
Produce a shippable spec for a mindfulness timer web app with session customization, ambient audio, habit streaks, and PWA install support.
- Target user (beginner / experienced / both)
- Supported platforms (mobile-first? desktop? both)
- Brand constraints (color, font, logo)
- Monetization model (free, one-time, subscription) - optional
- Offline expectation (must-have / nice-to-have)
- Feature list split into MVP (must-ship) and v1.1 (nice-to-have)
- User flows: first-launch, start session, mid-session, post-session review
- Data model: Session, Preference, Streak, AudioTrack - with fields and types
- State machine for the timer: Idle -> Prep -> Breath-In -> Breath-Out -> Bell -> Done
- UI spec per screen: components, gestures, accessibility (VoiceOver, high-contrast)
- Audio strategy: preloaded vs streamed, binaural/nature/silence, volume persistence
- Offline and PWA: service worker cache strategy, install prompt logic, notification fallback
- Telemetry plan: 5-7 events with payload, stored locally, optional opt-in sync
- Acceptance checklist: 10 items, pass/fail
- No framework required; vanilla JS + CSS is acceptable. If a framework is proposed, justify it.
- Zero third-party tracking by default.
- Respect Reduced-Motion and Dark-Mode system preferences.
- Session customization must persist without a login.
Input: beginner-focused, mobile-first, no monetization, must work offline. Output: 12 MVP features, 4 user flows, 5-state timer FSM, service worker plan.