feat(mindmachine): implement Android MVP app scaffold, session flows, safety gating, and tests
This commit is contained in:
Tretzi
160
MVP.md
Normal file
160
MVP.md
Normal file
@@ -0,0 +1,160 @@
|
||||
# MindMachine - MVP Definition
|
||||
|
||||
## 1. MVP Goal
|
||||
|
||||
The MVP shall prove that a smartphone can function as a simple personal mind machine by:
|
||||
- displaying controlled blinking light patterns on-screen,
|
||||
- outputting binaural audio through stereo headphones,
|
||||
- guiding the user through safe setup and session use,
|
||||
- supporting short, usable sessions with minimal configuration.
|
||||
|
||||
The MVP is a working prototype focused on core experience, safety, and reliability rather than breadth.
|
||||
|
||||
---
|
||||
|
||||
## 2. MVP Success Criteria
|
||||
|
||||
The MVP is successful if a user can:
|
||||
1. open the app,
|
||||
2. read and acknowledge the safety warnings,
|
||||
3. choose a preset,
|
||||
4. connect headphones,
|
||||
5. start a session,
|
||||
6. experience synchronized screen blinking and binaural audio,
|
||||
7. pause or stop the session at any time,
|
||||
8. finish the session without confusion or instability.
|
||||
|
||||
---
|
||||
|
||||
## 3. Included in MVP
|
||||
|
||||
### 3.1 Core session engine
|
||||
- Start, pause, resume, and stop a session
|
||||
- Configurable session duration
|
||||
- Countdown before start
|
||||
- Remaining time display
|
||||
|
||||
### 3.2 Visual stimulation
|
||||
- Full-screen flashing mode
|
||||
- Full-screen pulse/fade mode
|
||||
- Adjustable blink frequency
|
||||
- Adjustable screen brightness recommendation
|
||||
- Keep screen awake during session
|
||||
|
||||
### 3.3 Audio stimulation
|
||||
- Stereo binaural tone generation
|
||||
- Adjustable carrier frequency
|
||||
- Adjustable binaural beat difference frequency
|
||||
- In-app volume control or clear system-volume guidance
|
||||
- Headphone-required guidance
|
||||
|
||||
### 3.4 Presets
|
||||
The MVP shall include at least 3 built-in presets:
|
||||
- Relax
|
||||
- Focus
|
||||
- Sleep Prep
|
||||
|
||||
Each preset includes:
|
||||
- duration
|
||||
- blink rate
|
||||
- light pattern
|
||||
- carrier frequency
|
||||
- binaural difference
|
||||
|
||||
### 3.5 Safety
|
||||
- First-run warning and acknowledgment flow
|
||||
- Session-start reminder to use stereo headphones
|
||||
- Explicit warning for seizure/photo-sensitivity risks
|
||||
- Stop immediately guidance for discomfort
|
||||
|
||||
### 3.6 Setup guidance
|
||||
- Brief instructions for how to place the phone in front of the eyes
|
||||
- Basic explanation of a DIY cardboard holder
|
||||
- Comfort and fit cautions
|
||||
|
||||
### 3.7 Completion flow
|
||||
- Session finished screen
|
||||
- Option to repeat session
|
||||
- Option to return to home screen
|
||||
|
||||
---
|
||||
|
||||
## 4. Excluded from MVP
|
||||
|
||||
The MVP does not need:
|
||||
- accounts or cloud sync
|
||||
- ambient background sounds
|
||||
- downloadable content
|
||||
- spoken voice guidance
|
||||
- printable holder templates
|
||||
- advanced animation editor
|
||||
- adaptive or biometric feedback
|
||||
- social/community features
|
||||
- analytics dashboard for users
|
||||
- medical claims or therapeutic workflows
|
||||
|
||||
---
|
||||
|
||||
## 5. MVP User Flow
|
||||
|
||||
1. User opens app
|
||||
2. User reads onboarding + warnings
|
||||
3. User selects preset
|
||||
4. User verifies headphones and setup
|
||||
5. User starts countdown
|
||||
6. App enters full-screen session mode
|
||||
7. App runs synchronized light + audio session
|
||||
8. User pauses/stops or reaches session end
|
||||
9. App shows completion screen
|
||||
|
||||
---
|
||||
|
||||
## 6. MVP Screens
|
||||
|
||||
The MVP should include these screens:
|
||||
- Welcome / onboarding
|
||||
- Safety warning acknowledgment
|
||||
- Home / preset selection
|
||||
- Session setup
|
||||
- Active session screen
|
||||
- Session complete screen
|
||||
- Simple settings screen
|
||||
|
||||
---
|
||||
|
||||
## 7. MVP Technical Priorities
|
||||
|
||||
Implementation priority order:
|
||||
1. Stable session timing
|
||||
2. Reliable stereo audio generation
|
||||
3. Full-screen light rendering
|
||||
4. Safe interruption handling
|
||||
5. Clear UI for start/pause/stop
|
||||
6. Preset persistence
|
||||
|
||||
---
|
||||
|
||||
## 8. MVP Risks
|
||||
|
||||
Main risks for the MVP:
|
||||
- audio latency or instability,
|
||||
- timing drift between audio and visual patterns,
|
||||
- inconsistent brightness behavior across devices,
|
||||
- interruptions from calls/notifications,
|
||||
- unsafe use without proper warnings,
|
||||
- poor comfort if holder guidance is unclear.
|
||||
|
||||
---
|
||||
|
||||
## 9. Recommended First Platform
|
||||
|
||||
The MVP should target **Android first** because:
|
||||
- native Android gives more direct control over audio/session behavior,
|
||||
- Android is more practical for experimental device-style applications,
|
||||
- screen/audio/session APIs are generally more flexible for this use case.
|
||||
|
||||
---
|
||||
|
||||
## 10. MVP Deliverable
|
||||
|
||||
The MVP deliverable is a native mobile app prototype that safely delivers a basic mind machine session experience with a small set of presets and a clean, minimal interface.
|
||||
Reference in New Issue
Block a user