📱 Android Early Access — Sequencing Plan

Ordered for testability: get each feature into a state QA can exercise as early as possible, so we collect feedback while there's runway to fix. Keeps the proposed priority order, front-loads the access spine, fills the gaps.

Ship by

Jun 24

Donald back 22nd

Milestone roadmap

M0 · Access spineowner: Rhys · parallelUNBLOCKS QA

Installable Dev/Alpha/Beta build + Google login + minimal onboarding that reaches the home/call screen. Internal QA confirmed via Firebase App Tester — Alex is in and testing today. M0 now narrows to external/Play distribution for the Open Testing launch.

Exit: Play Open Testing track live; external testers can install via the Play listing.

PMF-3175 Play tracksInternal QA on Firebase App Tester ✓

M1 · CallsSinger / Amos / RhysQA #1

Highest-risk, highest-value, mostly there. Reconnect on drop, session resume, network handover, 5001 recovery.

Exit: QA places a call, survives wifi↔LTE handover, recovers from drops.

PMF-2849 epic PMF-2782 reconnect PMF-2870 /v1/reconnect PMF-3071/3072 handover PMF-3067 5001 PMF-3095 Charlie+Simone ✓PMF-2866 Telecom hold

M2 · TextsAmos (focused)QA #2

Chat reconnect, character-switch history UX, send-button stall recovery.

Exit: QA holds a text conversation, switches characters, recovers from stalls.

PMF-2794 epic PMF-3047 reconnect RPC PMF-3048 switch UX #17369 send button

M3 · Login completenessRhysPARITY

+ gap Apple Sign-In (iOS has it; needed for iOS-user migration & account parity), delete-account (Play policy), sign-out. Locked to M3.

Exit: QA signs in with Google and Apple, can delete account.

Google login ✓#15874/#15880 account ✓PMF-3215 Apple Sign-Indelete-account

M4 · SDUI cardsRhysQA #3

Framework, shell, carousel, Search card all done. Finish card content + post-call rendering.

Exit: QA sees cards in-call and in the post-call activity sheet.

PMF-2719/2720/2721 ✓PMF-2927/2930 ✓PMF-2722 #7 AgentFile PMF-2724 #9 post-call PMF-2723 #8 ExtSearch

M5 · Push + universal linksRhys / DonaldMUST-SHIP

Now in-scope (Open Testing commitment). FCM plumbing → permission prompt → text/waitlist push → deep-link tap-through. + gap: universal links.

Exit: QA receives a push and deep-links into the right screen.

PMF-3085 epic PMF-3182 FCM plumbing PMF-3086 permission PMF-1960 text push PMF-3100 waitlist push PMF-3087 settings

M6 · Waitlist gate + analyticsDonaldLAST

Land the gate early-and-cheap if it blocks sign-in testing; keep analytics events as final polish. Mostly-built framework needs Android wiring + verification.

Exit: non-allowlisted users hit waitlist screen; joined/approved events verified.

PMF-3090 Statsig gate PMF-3089 beta opt-inwaitlist_joined/approvedRudderstack/Bitdrift

Compressed timeline (≈3 weeks)

Wk1 · Jun 2–8Wk2 · Jun 9–15Wk3 · Jun 16–24

M0 Access spine

spine + QA on

M1 Calls

QA #1

M2 Texts

QA #2

M3 Login (Apple)

parity

M4 SDUI cards

QA #3

M5 Push + links

must-ship

M6 Waitlist/analytics

last

Bars overlap intentionally — features land behind flags so a slip in one doesn't block QA of the others. M0 + M1 are the critical path; M6 is the only fully-deferrable bucket.

Gaps the original list was missing

➕ Add to scope

Distribution / release plumbing — Play tracks (PMF-3175), Firebase suffix builds, signing. The true M0; nothing is QA-able without it.
Onboarding flow — gender, agent audio sampler (CHA-55), greeting. Sits between login and calls/texts.
In-app waitlist gate — distinct from analytics; the /waitlist/status → app-or-gate logic is a must-ship.
Universal / deep links — required by Open Testing + push tap-through + sesame.com/beta hand-off.
Settings / account parity — sign-out, delete-account (Play data-safety policy).
Profile / character parity — confirm release profiles reach Android (PMF-3194 was canceled — verify it's covered).

⛔ Out of scope for 6/24

Android Auto (PMF-2704, PMF-2708) — backlog, Level 4, partner application + production rollout. Separate train; explicitly not part of Early Access.

❓ Confirm with team

Waitlist promotion cadence (time / count / manual) — sizes the M6 analytics work.

How to validate each milestone

Per-milestone gates via capture-android (visual evidence) and navigate-android (Maestro flow runs) at each exit.
Calls: wifi↔LTE handover + mid-call drop on a physical device; watch call.connect.duration_ms and reconnect success.
Push: verify FCM token registration server-side, send a test push, confirm deep-link tap-through.
Cross-check Linear board ordering against this sequence (manual — read-only here).

Items to validate in Linear

Plan items that don't reference a Linear ticket — confirm whether each needs to be tracked, is already covered by an existing issue, or can be dropped.

Delete-account flow on Android (M3) — Play data-safety policy requirement; no ticket found.
Universal / deep links on Android (M5 + Gaps) — required by Open Testing + push tap-through; no ticket found.
waitlist_joined / waitlist_approved analytics events on Android (M6) — iOS landed in #16428; verify Android wiring is ticketed.
Rudderstack / Bitdrift sink verification on Android (M6) — sink correctness on the events above; may be covered by an existing analytics ticket.
In-app waitlist gate client logic (Gaps) — GET /waitlist/status → app-or-gate behavior. May be covered by PMF-3090, but the client gating itself may need its own ticket.