[BW-IOS-00] Establish staged iOS foundation and selective KMP boundary #30
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Classification
Long-horizon planning/foundation issue. Not implementation-ready until Android playback correctness is stable.
Product intent
Create BookWave for iPhone slowly and safely, reusing portable correctness policy where it helps while keeping Apple UI, playback and system integrations native.
CarPlay and Live Activities are explicit target surfaces, not optional afterthoughts.
Recommended architecture
Selective Kotlin Multiplatform portable core/domain + native SwiftUI + native Apple media/system integrations.
Likely portable:
Remain native on Apple:
Stages
Stage 0 — KMP portability spike
Move/compile only a tiny pure-policy slice for JVM + iOS simulator and validate Swift interop. Android behavior must remain unchanged. If the shared boundary makes the architecture worse, fully native Swift remains acceptable.
Stage 1 — iOS shell/auth
Native SwiftUI app, Audiobookshelf sign-in, secure credentials, profile/account switching. No playback.
Stage 2 — read-only library
Books/authors/series/shelves/search/details/art/cached data.
Stage 3 — native Apple playback
Streaming, one-book timeline, chapters, seek, speed, background audio, lock-screen/Control Center, interruptions, Bluetooth controls and Now Playing. No clever cross-device reconciliation until the baseline player is stable.
Stage 4 — progress/session correctness
Apply the same behavioral contracts as Android: session ownership, acknowledged progress, realtime/REST evidence, intentional rewinds, local remembered identity, resume freshness and offline journal semantics.
Stage 5 — downloads/offline
Native Apple background/storage implementation. Preserve authorization/profile ownership and safe physical-copy semantics where applicable.
Stage 6 — Apple system integrations
App Intents, Shortcuts/Siri-facing actions, widgets and any justified Live Activity.
Stage 7 — CarPlay
Native CarPlay audio surface after playback is stable and entitlement has been obtained.
Stage 8 — parity/polish
Value-based parity rather than checklist parity.
Dependencies
Begin Stage 0 only after the Android contracts that are candidates for sharing are stable, especially GitHub PR #93 and #24 BW-PLAY-01.
Explicitly out of scope
Acceptance gate for Stage 0
Effort
Large overall, intentionally split into stages.
Risk
High if treated as a rewrite; Medium if each stage is independently shippable and selective.
Links / future children