Overview#
The OSHUN closed beta validates the unified shell experience across all five customer domains (Tara, Arete, Veritas, Nyx, Nisaba) before public launch. Beta runs for 3 weeks with two cohorts: internal team and invited external testers.
Cohorts#
Internal Cohort (Week 1-3)#
| Group | Size | Selection Criteria |
|---|---|---|
| Engineering | 10 | All OSHUN contributors |
| Product & Design | 5 | PMs and designers for each domain |
| QA | 3 | Dedicated QA engineers |
| Stakeholders | 5 | Leadership, domain leads |
Total internal: ~23 testers
Distribution: TestFlight (Internal group) and Play Console (Internal track)
External Cohort (Week 2-3)#
| Group | Size | Selection Criteria |
|---|---|---|
| Domain power users | 20 | Active users of Tara/Veritas/Nyx surfaces plus study-oriented Nisaba-adjacent users |
| New users | 10 | No prior domain app experience |
| Accessibility | 5 | Users with assistive technology needs |
| Low-connectivity | 5 | Users in regions with unreliable network |
Total external: ~40 testers
Distribution: TestFlight (Beta group) and Play Console (Closed track)
Recruitment channels: In-app banners in standalone domain apps, email invitation to power users, direct outreach for accessibility and low-connectivity testers.
Beta Test Scripts#
Script 1: First Launch and Onboarding#
1. Install OSHUN from TestFlight / Play Internal.
2. Launch the app. Note: time from tap to first interactive screen.
3. Complete onboarding flow. Note: any confusion, friction, or errors.
4. Choose at least 2 domains during onboarding.
5. Arrive at the home screen. Note: is the feed populated and relevant?
6. Verify: dark mode respects system preference.
Success criteria: Onboarding completes in < 2 minutes. Home feed shows content from chosen domains.
Script 2: Cross-Domain Daily Journey (Morning)#
1. Open OSHUN.
2. From home, launch a Tara meditation session (should be <= 2 taps).
3. Complete or skip the session.
4. Return to OSHUN home (back navigation or gesture).
5. Tap a Veritas story from the feed.
6. Read the story. Note: confidence indicators and evidence visibility.
7. Save the story (bookmark).
8. Return to home.
9. Check the Activity tab. Note: does it show today's meditation and reading?
Success criteria: Each domain launch takes <= 2 seconds. Back navigation returns to shell. Activity feed is updated in real-time.
Script 3: Cross-Domain Daily Journey (Evening)#
1. Open OSHUN.
2. Launch Nyx from home or Explore tab.
3. View tonight's sky highlights. Note: readability in night/dark mode.
4. Return to home.
5. Launch Arete daily check-in from the home card or quick action.
6. Complete the check-in. Note: total time (target: <= 60 seconds).
7. View streak and progress visuals.
8. Return to home.
9. Verify: home feed reflects evening context (Nyx promoted, Tara wind-down).
Success criteria: Check-in completes in <= 60 seconds. Night mode is comfortable. Streaks display correctly.
Script 4: Search and Discovery#
1. Open the Search tab or universal search.
2. Search for "meditation" — results should include Tara sessions.
3. Search for "climate" — results should include Veritas stories.
4. Search for "Mars" — results should include Nyx content.
5. Search for "journal" — results should include Arete entries.
6. Search for "passage" — results should include Nisaba reading or study items.
7. Tap a cross-domain result. Note: does it launch the correct domain?
8. Note: search latency, result relevance, empty states.
Success criteria: Cross-domain search returns relevant results from all domains. Tap-to-content takes < 3 seconds.
Script 5: Offline and Connectivity#
1. Open OSHUN while online. Navigate to home, explore, and profile.
2. Enable airplane mode.
3. Navigate between tabs. Note: which screens show cached content vs. errors.
4. Attempt to launch a Tara session. Note: does cached audio play?
5. Attempt to open a Veritas story. Note: does saved article display?
6. Re-enable network.
7. Verify: app recovers gracefully, no stuck loading states.
Success criteria: Home and profile show cached content offline. Saved content is accessible. Recovery is automatic.
Script 6: Deep Links and Universal Links#
1. Receive a shared OSHUN link (e.g., oshun.app/d/tara/session/123).
2. Tap the link. Note: does it open OSHUN and navigate to the correct content?
3. Test: oshun://domains/veritas/story/456 (custom scheme).
4. Test: oshun.app/d/nyx/tonight (universal link).
5. Test: oshun.app/d/arete/checkin (universal link).
6. Note: any link that fails to resolve or shows wrong content.
Success criteria: All deep links resolve to the correct domain and content.
Script 7: Accessibility#
1. Enable VoiceOver (iOS) or TalkBack (Android).
2. Navigate through the home tab. Note: all elements are labeled and reachable.
3. Launch a domain experience. Note: domain content is navigable.
4. Return to shell. Note: focus returns to a logical element.
5. Test with dynamic type (largest text size):
a. Home feed cards remain readable.
b. Tab bar labels are visible.
c. No text truncation hides critical information.
6. Test with reduced motion:
a. Tab transitions use no animation.
b. Domain launch transitions are instant.
Success criteria: All interactive elements have accessibility labels. Large text does not break layout. Reduced motion is honored.
Script 8: Performance and Battery#
1. Use the app for 30 continuous minutes with screen on.
2. Note: battery drain percentage.
3. Monitor: memory usage (should stay < 300 MB active).
4. Scroll the home feed rapidly for 60 seconds.
5. Note: any dropped frames or jank.
6. Switch between domains 10 times rapidly.
7. Note: any crashes, ANRs, or loading failures.
Success criteria: Battery drain < 5% per 30 min. No crashes. No sustained jank (> 3 consecutive dropped frames).
Feedback Collection#
In-App Feedback#
- Shake-to-report gesture triggers feedback form (dev/beta builds only).
- Form captures: screenshot, device info, app version, reproduction steps.
- Submitted to internal issue tracker with
beta-feedbacklabel.
Structured Surveys#
- Day 1 survey: First impressions, onboarding experience, NPS.
- Day 7 survey: Feature discovery, cross-domain navigation, pain points.
- Day 14 survey: Retention drivers, comparison to standalone apps, NPS.
- Exit survey (opt-in): Reasons for disengagement.
Severity Tagging#
All reported issues are triaged and tagged:
| Severity | Definition | Beta Response |
|---|---|---|
| P0 | Crash on launch, data loss, security issue | Fix before Week 2 |
| P1 | Core flow broken (auth, navigation, domains) | Fix before Week 3 |
| P2 | Feature degraded, bad UX, performance issue | Fix before launch |
| P3 | Cosmetic, minor friction | Track for post-MVP |
| P4 | Enhancement suggestion | Backlog |
Beta Milestones#
| Week | Milestone | Gate |
|---|---|---|
| 1 | Internal cohort onboarded, scripts 1-4 run | Zero P0 issues |
| 2 | External cohort invited, scripts 5-8 run | Zero P0, P1 count < 5 |
| 3 | All surveys complete, final triage | Zero P0/P1, NPS >= 30 |
Go/No-Go Criteria for Public Launch#
The beta is successful and launch proceeds if:
- Zero unresolved P0 or P1 issues.
- Crash rate < 0.5% across both platforms.
- ANR rate < 0.2% (Android).
- NPS score >= 30 from external cohort.
- All 8 beta scripts pass on both iOS and Android.
- Onboarding completion rate >= 85%.
- D7 retention of beta cohort >= 40%.
- All domain-specific acceptance criteria met (see OSHUN_APP_TODOS.md).