Android operator parity with the iOS baseline #46
erik-sutton95
started this conversation in
Ideas & Feature Requests
Replies: 1 comment
|
Maintainer tasks:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
OpenPocketCine's iOS app is the operator baseline. Android already has the connection spine (BLE → camera Wi-Fi → DUML → live HEVC) and a real Compose shell, but it is not a 1:1 monitor yet.
This thread is the parent for Android operator-visible parity. Pick one workstream at a time. Do not open a single mega-PR.
Related: roadmap index ·
ANDROID.md·docs/ROADMAP.md(dual-platform parity is Later)What already works on Android
SurfaceView) for Pocket 4 / 4 ProProtocol encode still comes from Swift (
OpenPocketCineAndroidFacade). Kotlin owns BLE, Wi-Fi, UDP, decode, and Compose.Workstreams
Treat each checkbox as its own shippable slice.
1. GPU looks
LiveViewScreen.kt2. Scopes
LiveColorScience/AudioLevelMeterfrom the Swift core (JNI), do not copy OpenZCine Android3. Remaining camera writes
zoomFactorRaw), no writeAndroidSessionWire.CommandKindpast 35 using existingCommands.swiftbuilders4. Osmo Nano on Android
HevcDecoder.ktis hardcoded HEVC5. Face AF + ActiveTrack
FacePriorityExposure.swift)6. Media library
enterPlayback, HTTP catalog, thumbs, player, LUT preview7. Chrome, Operator Setup, recovery
FeedWatchdog/SessionRecoveryinstead offailLink→ FAILEDThread.sleep(350)× 20)Out of scope here
ANDROID.md)Done when
An operator can run a Pocket 4 / 4 Pro (and Nano AVC) session on Android with the same control writes, monitor assists, media review, and reconnect behavior they get on iOS — minus Play distribution and Frame.io.
Concrete threads: Nano · reliability audit
All reactions