Status: Complete
Date: April 2, 2026
Task: V1-MOB-029
1. Purpose#
This document is the canonical redesign inventory for every major OSHUN mobile shell, domain-entry, and continuity surface that materially shapes the customer experience.
Its job is not to redesign the product yet. Its job is to make the redesign wave executable by answering four questions clearly:
- what surface exists today
- where it lives in the repo
- what experience posture it currently presents
- which redesign tasks should own it next
2. Inputs Reviewed#
Primary implementation inputs reviewed:
apps/oshun/mobile/app/_layout.tsxapps/oshun/mobile/app/(tabs)/_layout.tsxapps/oshun/mobile/app/(tabs)/index.tsxapps/oshun/mobile/app/(tabs)/explore.tsxapps/oshun/mobile/app/(tabs)/activity.tsxapps/oshun/mobile/app/(tabs)/library.tsxapps/oshun/mobile/app/(tabs)/profile.tsxapps/oshun/mobile/app/domain/[domainId].tsxapps/oshun/mobile/src/components/MobileAssistantLauncher.tsxapps/oshun/mobile/src/components/MobileAssistantSheet.tsxapps/oshun/mobile/src/components/MobileDomainSwitcherControl.tsxapps/oshun/mobile/src/components/QuickActionsTray.tsxapps/oshun/mobile/src/offline/GlobalOfflineBanner.tsxapps/oshun/mobile/src/offline/ShellOfflineContinuityCard.tsxapps/oshun/mobile/src/auth/MobileAuthCard.tsxapps/oshun/mobile/src/auth/MobileOnboardingCard.tsxapps/oshun/mobile/src/notifications/*
Existing audit and strategy inputs reviewed:
docs/adr/ADR-0056-oshun-mobile-shell-relationship-model.mddocs/releases/v1/reports/current-state-redesign-inventory.mddocs/releases/v1/specs/surface-redesign-ranking.mddocs/releases/v1/reports/customer-shell-redesign-inventory.mddocs/releases/v1/scope/one-handed-mobile-ergonomic-rules.md
3. Redesign Frame#
3.1 Visual Thesis#
OSHUN mobile should feel like one calm, thumb-reachable, Tara-centered continuity shell with a single dominant focal plane per screen, not a vertical stack of equally weighted cards and utility panels.
3.2 Content Plan#
Every redesigned mobile surface should resolve this sequence:
- orient immediately
- reveal one dominant next move
- show only the support context needed for the current decision
- offer a clean handoff into continuity, governance, or domain depth
3.3 Interaction Thesis#
The redesign wave should bias toward:
- bottom-reachable primary actions
- fewer simultaneous helper surfaces competing at once
- bottom-sheet continuity for assistant, switching, and quick actions
- calmer reveal rhythm and less border-first card repetition
- explicit preserve/continue/branch semantics across every handoff
4. State Labels#
keep: structurally sound and should be preserved with only adjacent polishrefine: correct product role, but hierarchy/ergonomics need meaningful workredesign: important surface exists, but its visual or interaction model is not good enough for V1replace: current surface is absent or the wrong product shape
5. Inventory Summary#
| Surface cluster | Current state | Disposition | Priority | Next-task owners |
|---|---|---|---|---|
| Shell frame and persistent helpers | implemented | refine | P0 | V1-MOB-031, V1-MOB-032, V1-MOB-035, V1-MOB-036 |
| Primary shell routes | implemented | mixed | P0/P1 | V1-MOB-030, V1-MOB-031, V1-MOB-032, V1-MOB-036 |
| Domain-entry surfaces | implemented | redesign | P0/P1 | V1-MOB-031, V1-MOB-032, V1-MOB-033 |
| Domain route and per-domain continuity | implemented | redesign | P0/P1 | V1-MOB-033, V1-MOB-034, V1-MOB-036 |
| Governance and trust continuity | implemented/embedded | refine/replace | P0/P1 | V1-MOB-034, V1-MOB-036, V1-MOB-037 |
6. Detailed Inventory#
6.1 Shell Frame And Persistent Helpers#
| Surface | Entrypoints | Current posture | Disposition | Priority | Primary redesign problem | Must preserve | Next tasks |
|---|---|---|---|---|---|---|---|
| Structural tab shell | app/(tabs)/_layout.tsx |
Five-tab shell exists with emoji icons, dark chrome, and stable accessibility/test contracts. | refine | P0 | Navigation is structurally correct but still reads as utilitarian chrome rather than a premium mobile spine. | Home/Explore/Activity/Library/Profile relationship model from ADR-0050. |
V1-MOB-031, V1-MOB-037, V1-MOB-038, V1-MOB-039 |
| Floating assistant launcher | src/components/MobileAssistantLauncher.tsx, app/_layout.tsx |
Global launcher keeps assistant reachable across shell and domain routes. | refine | P0 | Launcher plus contextual assistant cards create duplicate invitation layers without a single clear hierarchy. | Assistant as a global continuity layer, not a peer tab. | V1-MOB-031, V1-MOB-035, V1-MOB-038 |
| Contextual assistant entry cards | src/components/AssistantEntryCard.tsx, all five tab routes |
Explicit per-screen assistant invitation exists on every primary tab. | refine | P0 | The pattern is directionally right but currently inherits the general stacked-card density problem. | Context-aware prompt seeding and route-aware assistant context. | V1-MOB-031, V1-MOB-032, V1-MOB-038 |
| Assistant sheet | src/components/MobileAssistantSheet.tsx, src/components/AssistantDisclosureStrip.tsx, src/components/AssistantMemoryState.tsx |
Governance-aware global sheet with disclosure, memory state, quick prompts, transcript, and action routing. | refine | P0 | The contract is strong, but the sheet still needs a clearer focal hierarchy and calmer transcript/composer composition. | Disclosure, memory-state clarity, contextual routing, accessibility contract. | V1-MOB-031, V1-MOB-034, V1-MOB-035, V1-MOB-038 |
| Global domain switcher launcher and sheet | src/components/MobileDomainSwitcherControl.tsx, src/components/MobileDomainSwitcherSheet.tsx |
Thumb-zone launcher and grouped switch sheet keep five domains reachable. | refine | P0 | Thumb reach is fixed, but the visual model still feels like a utility panel rather than an intentional shell affordance. | Grouped Tara-centered rail, origin/stack continuity. | V1-MOB-031, V1-MOB-037, V1-MOB-038 |
| Quick actions tray | src/components/QuickActionsTray.tsx |
Bottom sheet exposes fixed launch set for meditation, check-in, briefing, tonight, and passage. | redesign | P0 | The product job is right, but the presentation still reads as a dense list of action tiles rather than a calm task switcher. | Canonical five quick actions and bottom-sheet entry model. | V1-MOB-032, V1-MOB-033, V1-MOB-035, V1-MOB-038 |
| Global offline banner | src/offline/GlobalOfflineBanner.tsx |
Root banner exposes offline/reconnecting status and sync controls. | keep | P1 | Foundation is credible; redesign work should tune tone and integration, not replace the contract. | Global connectivity visibility and queue controls. | V1-MOB-036, V1-MOB-037 |
| Per-surface offline continuity card | src/offline/ShellOfflineContinuityCard.tsx |
Shared offline continuity block is mounted across Home, Explore, Activity, Library, and Profile. | keep | P1 | Useful contract already exists, but current stacked-card weight should be reduced during redesign. | Shared offline copy contract and retry/sync affordances. | V1-MOB-036, V1-MOB-037 |
| Thumb-reach search dock | src/components/ThumbReachActionDock.tsx, app/(tabs)/explore.tsx |
Explore exposes a lower-zone search refocus affordance. | refine | P1 | Good ergonomic direction, but it needs to sit inside a broader shell action hierarchy rather than as a special-case helper. | Thumb-zone refocus behavior. | V1-MOB-031, V1-MOB-037 |
6.2 Primary Shell Routes#
| Surface | Entrypoints | Current posture | Disposition | Priority | Primary redesign problem | Must preserve | Next tasks |
|---|---|---|---|---|---|---|---|
| Home | app/(tabs)/index.tsx |
Daypart hero, return journeys, companion bridges, direct launches, recommendation/favorites/utilities. | redesign | P0 | Home still carries too many secondary blocks and reads as a module stack instead of one calm start-of-day and re-entry composition. | Daypart leadership, return journeys, companion bridges, direct launches. | V1-MOB-030, V1-MOB-032, V1-MOB-037, V1-MOB-038, V1-MOB-039 |
| Explore | app/(tabs)/explore.tsx |
Search-first discovery workspace with filters, collections, spotlight, assistant, domain switching, library preview, and thumb dock. | redesign | P1 | Search, curation, editorial discovery, save-state preview, and operator-like density compete in one route. | Cross-domain search, save-to-library, domain filters, discovery breadth. | V1-MOB-031, V1-MOB-032, V1-MOB-033, V1-MOB-039 |
| Activity | app/(tabs)/activity.tsx |
Hybrid continuity timeline and notification inbox with grouped items, filters, optimistic mutations, and offline retry. | refine | P1 | Triage, progress, and continuity all live in one visual layer, making the route feel heavier than it should. | Cross-domain continuity, mark-read flows, offline replay, governance handoff. | V1-MOB-032, V1-MOB-036, V1-MOB-037, V1-MOB-038 |
| Library | app/(tabs)/library.tsx, src/library/UnifiedLibraryView.tsx |
Preserve-oriented route with hero framing, stats, relationship card, assistant CTA, and unified saved-item view. | refine | P1 | The preserve metaphor is strong, but the route still leans on stacked blocks and dense saved-item cards. | Unified save model, preserve/return semantics, cross-domain item handling. | V1-MOB-032, V1-MOB-033, V1-MOB-038, V1-MOB-039 |
| Profile | app/(tabs)/profile.tsx |
Large governance surface spanning auth, onboarding, plans, billing, accessibility, notifications, privacy, offline downloads, consents, exports, domains, and sessions. | refine | P1 | Scope is correct, but the route reads as a long settings exhaust instead of guided governance with clear section priority. | Auth, recovery, privacy, notification policy, data rights, device/session management. | V1-MOB-034, V1-MOB-036, V1-MOB-037, V1-MOB-039 |
6.3 Domain-Entry Surfaces#
| Surface | Entrypoints | Current posture | Disposition | Priority | Primary redesign problem | Must preserve | Next tasks |
|---|---|---|---|---|---|---|---|
| Home daypart hero | app/(tabs)/index.tsx, src/navigation/mobileDaypartJourneys.ts |
Clear start-of-day anchor with daypart primary/secondary moves. | refine | P0 | Structurally strong, but still framed by too much surrounding support content. | Tara/daypart centering and time-aware route mapping. | V1-MOB-030, V1-MOB-039 |
| Return journeys | app/(tabs)/index.tsx |
Continuity cards surface resumable work across domains. | refine | P0 | Important job, but still rendered as repeated card blocks instead of one composed continuation band. | Re-entry priority and resumable domain context. | V1-MOB-030, V1-MOB-032, V1-MOB-038 |
| Companion bridges and direct launches | app/(tabs)/index.tsx |
Cross-domain bridge cards and direct domain launch cards exist below the hero. | redesign | P1 | Entry choices are useful but visually repetitive, creating a feed-of-cards feel. | Clear branch paths into all five domains. | V1-MOB-030, V1-MOB-032, V1-MOB-033 |
| Explore search entry | app/(tabs)/explore.tsx |
Search bar, filters, sort controls, recent/trending queries, and result list all live in one vertical stack. | redesign | P0 | Search intent is central but the route still forces too much pre-result context before the result lane. | Search-as-primary behavior, save and domain filtering. | V1-MOB-033, V1-MOB-039 |
| Explore curated collections and spotlight entry | app/(tabs)/explore.tsx |
Collections and editorial spotlights provide alternate entry paths into discovery. | refine | P1 | Valuable content exists, but it competes with the primary search job instead of deepening it. | Editorial and collection-driven branching. | V1-MOB-032, V1-MOB-033 |
| Library relationship actions | app/(tabs)/library.tsx |
Explore Further and Resume in Activity establish preserve-to-branch and preserve-to-continue semantics. | refine | P1 | Correct shell model, but the entry pattern is still visually generic. | Library -> Explore and Library -> Activity handoffs. | V1-MOB-032, V1-MOB-033 |
| Profile connected-domain manage entry | app/(tabs)/profile.tsx |
Connected domains block routes into per-domain management. | refine | P2 | Useful governance handoff exists but sits too deep inside the long Profile stack. | Domain governance visibility and manage handoff. | V1-MOB-034, V1-MOB-037 |
| Deep-link focus cards | app/domain/[domainId].tsx, src/navigation/mobileDomainDeepLinkFocus.ts |
Canonical focus cards orient users when domain routes are opened from shared links and deep links. | keep | P1 | Strong continuity contract already exists; redesign should integrate it more gracefully into the domain route chrome. | Deep-link orientation and target-specific CTA. | V1-MOB-033, V1-MOB-037 |
6.4 Domain Route And Per-Domain Continuity#
| Surface | Entrypoints | Current posture | Disposition | Priority | Primary redesign problem | Must preserve | Next tasks |
|---|---|---|---|---|---|---|---|
| Shared domain scaffold | app/domain/[domainId].tsx |
One giant shared route renders all five domains with per-domain branches, deep-link focus, continuity, and offline logic. | redesign | P0 | The route is too important and too broad to remain a single large generic scaffold without stronger domain-specific choreography. | Shared routing contract, assistant/domain continuity, deep-link hydration. | V1-MOB-033, V1-MOB-034, V1-MOB-036, V1-MOB-039 |
| Tara launch and session surface | app/domain/[domainId].tsx Tara branch |
Meditation/course launch, audio session preparation, continuity, offline cache, and drift recovery all exist. | redesign | P0 | Listening entry, launch prep, continuation, and offline states need a calmer and more unified sequence. | Resume/start session behavior, audio prep, offline cache, drift recovery. | V1-MOB-033, V1-MOB-036 |
| Veritas reading and evidence surface | app/domain/[domainId].tsx Veritas branch, EvidenceCard.tsx, EvidenceSidebar.tsx, ClaimListItem.tsx, SourceListItem.tsx |
Rich reading, evidence, claim, source, and offline briefing structures already exist. | redesign | P1 | Evidence and provenance are present but too dense for mobile scan-first reading. | Claim/source/evidence integrity and offline briefing continuity. | V1-MOB-033, V1-MOB-034, V1-MOB-036 |
| Nyx night-observation surface | app/domain/[domainId].tsx Nyx branch |
Night-mode observation, continuity, and offline fallback exist with distinctive visual language. | refine | P1 | Stronger visual identity exists here, but entry, continuity, and offline fallback still need clearer sequencing. | Night adaptation, sky-event continuity, offline sky fallback. | V1-MOB-033, V1-MOB-036, V1-MOB-039 |
| Arete check-in and growth surface | app/domain/[domainId].tsx Arete branch |
Goals, habits, prompts, entries, coach insights, and continuity are all available. | redesign | P1 | Check-in, journaling, and habit flows compete inside one broad surface and need clearer mode separation. | Daily check-in, habit continuity, journal entry, coach insight handoffs. | V1-MOB-033, V1-MOB-036 |
| Nisaba study surface | app/domain/[domainId].tsx Nisaba branch, PassageListItem.tsx, NotebookCard.tsx |
Passage, note, compare, concept-thread, continuity, and offline study states exist. | redesign | P1 | Study depth is real, but mobile reading/note entry still needs a tighter primary lane and better evidence/disclosure compaction. | Passage continuity, note continuity, compare/study handoff, offline study preservation. | V1-MOB-033, V1-MOB-034, V1-MOB-036 |
| Drift recovery cards | app/domain/[domainId].tsx, src/continuity/* |
Domain-specific drift recovery cards exist for Tara, Arete, and Nisaba. | keep | P1 | Contract is already meaningful; redesign should improve visual calm and placement rather than replace the model. | Drift recovery semantics and explicit recovery CTA. | V1-MOB-036, V1-MOB-037 |
| Domain continuity cards | app/domain/[domainId].tsx, src/components/ContinuityCard.tsx |
Each major domain has an explicit continuity card for the next active step. | refine | P1 | Repeated card framing across domains dulls the continuation signal. | Domain-specific continuation logic and saved progress visibility. | V1-MOB-032, V1-MOB-036, V1-MOB-038 |
| Domain offline cache cards | app/domain/[domainId].tsx, src/offline/taraOfflineCache.ts, src/offline/veritasOfflineCache.ts, src/offline/nisabaOfflineCache.ts |
Tara, Veritas, and Nisaba expose explicit offline cache cards and active/offline states. | keep | P1 | Foundation is good, but the visual pattern should align with a calmer reconnect language. | Domain-specific offline cache visibility and actionability. | V1-MOB-036, V1-MOB-037 |
6.5 Governance And Trust Continuity#
| Surface | Entrypoints | Current posture | Disposition | Priority | Primary redesign problem | Must preserve | Next tasks |
|---|---|---|---|---|---|---|---|
| Mobile auth card | src/auth/MobileAuthCard.tsx, app/(tabs)/profile.tsx |
Embedded auth, signup, sign-in, recovery, refresh, and session-signout live inside Profile. | refine | P0 | Capability coverage is strong, but the embedded-in-profile posture still mismatches the shell’s calmer continuity model. | Sign in, sign up, recovery, refresh, sign out. | V1-MOB-034, V1-MOB-037 |
| Mobile onboarding card | src/auth/MobileOnboardingCard.tsx, app/(tabs)/profile.tsx |
Onboarding exists as an embedded card rather than a dedicated route. | replace | P0 | The product still lacks a first-class mobile onboarding experience. | Onboarding state continuity and account-aware setup steps. | Outside this inventory, but still aligned to the onboarding replacement gap already identified in mobile ranking. |
| Notification policy stack | app/(tabs)/profile.tsx, src/notifications/* |
Quiet hours, domain/persona routing, sensitivity, and push/email controls are deep inside Profile. | refine | P1 | Policy depth is strong, but the stack needs better compaction and prioritization for mobile scanning. | Domain/persona routing and quiet-hours logic. | V1-MOB-034, V1-MOB-037 |
| Session and device management | app/(tabs)/profile.tsx, src/auth/mobile-session-helpers.ts |
Linked sessions, revoke actions, sign-out-other-devices, and notices exist. | refine | P1 | Correct governance model, but the section still reads as a dense settings list rather than guided trust management. | Device/session visibility and revoke controls. | V1-MOB-034, V1-MOB-037 |
| Offline download governance | app/(tabs)/profile.tsx, src/offline/*Cache.ts |
Profile owns offline download policy, storage visibility, and clear-cache actions. | keep | P1 | Strong governance layer already exists; redesign should reduce anxiety and visual heaviness rather than replace the model. | Domain-by-domain offline controls and storage stats. | V1-MOB-036, V1-MOB-037 |
| Error and recovery boundaries | app/_layout.tsx, src/components/OshunErrorBoundary.tsx, src/observability/* |
Root error boundary and crash reporting exist as silent continuity infrastructure. | keep | P1 | Not a visual redesign driver by itself, but surrounding recovery surfaces need calmer productized failure states. | Safe retry path and crash context instrumentation. | V1-MOB-036, V1-MOB-037 |
7. Execution Mapping To Follow-On Tasks#
| Next task | Inventory ownership |
|---|---|
V1-MOB-030 |
Home route, daypart hero, return journeys, companion bridges, direct launches |
V1-MOB-031 |
Bottom nav, domain switcher, assistant launcher, contextual assistant entry, thumb docks |
V1-MOB-032 |
Quick actions tray, continuity cards, stacked shell content, library density reset |
V1-MOB-033 |
Explore search posture, Tara/Veritas/Nyx/Arete/Nisaba entry choreography, domain route composition |
V1-MOB-034 |
Evidence, provenance, disclosure, notification policy, profile governance, auth posture |
V1-MOB-035 |
Assistant sheet motion, shell transitions, quick-action and switcher motion, haptic posture |
V1-MOB-036 |
Offline, retry, reconnect, crash-adjacent recovery, trust-preserving degraded states |
V1-MOB-037 |
One-handed validation, interruption recovery, push re-entry, safe-thumb checks |
V1-MOB-038 |
Redesigned mobile E2E signoff for home, navigation, continuation, assistant entry |
V1-MOB-039 |
Device-specific visual captures for the redesigned shell on lower-tier Android and current iPhone |
8. Completion Note#
V1-MOB-029 is complete when the mobile redesign wave no longer depends on the
repo-wide inventory and ranking documents to infer what belongs in scope.
This document now acts as the mobile-specific source of truth for that scope.