Skip to content

Rewrite the spec for Cup's native Android playback engine #429

Closed

Description

@patricktree

Question

How does Spec: Native Android media player read once it is rewritten for the native Media3 ExoPlayer engine? Every decision ticket on Map: Native Android media player is now closed, so the spec can be rewritten from them. Its revision comment lists what changes. The work also re-cuts the built and unbuilt slices, including draft PR #401, and assigns each documentation change from Which documentation does the native Android engine change? to the slice that makes the page untrue. The new ADR goes with the first slice that contradicts ADR 0011. The ticket is done when the spec is ready for /to-tickets and its acceptance check is CUP-41's.


Written by @patricktree's agent (Claude Code, Claude Opus 5.5).

Activity

  1. self-assigned this
    on Nov 16, 2026
  2. patricktree commented on Nov 16, 2026

    @patricktree
    CollaboratorAuthor

    Resolution

    Done AFK on 2026-11-16: Spec: Android app that plays the narration track is rewritten for the native Media3 ExoPlayer engine from every closed decision on the map, and is ready for /to-tickets. Its acceptance check is CUP-41's. The earlier version is in the issue's edit history.

    What the spec now says, in short. ExoPlayer in the plugin's MediaPlaybackService is Android's only engine, and the page drives it through PlayerHostServices.createPlayer behind the Player port. System controls act on ExoPlayer directly, and the web media-session port is a no-op on Android. The plugin saves positions through the new signed position URL, and only the page renews URLs. The lifecycle has four stop reasons. A playing session survives a swipe from recents and is adopted on relaunch. Testing and documentation follow the testing and documentation decisions.

    Re-cut into six slices on draft PR #401's integration branch, which merges to main once:

    1. Web media session port: built (#395, 449d84fa), stands.
    2. Signed position URL on the server: new, no blockers.
    3. Android plays through ExoPlayer, driven by the page: reworks 8e3fbcf9 from Android media session plugin: playback keeps going while locked, and notification commands reach the page #396. It carries ADR 0029, ADR 0011's status, the playback.md carve-out and most of the page updates.
    4. Native stops, URL expiry and adoption: adds the JVM unit tests, turbo:test and the review gate's JDK/SDK prerequisites.
    5. Native position saves: blocked by 2 and 4.
    6. Pixel protocol and CUP-41 acceptance check: HITL.

    Each documentation change from Which documentation does the native Android engine change? is assigned to the slice that makes its page untrue.

    Existing tickets, for /to-tickets to act on. Close #397 as completed. Close #396, #398, #399 and #400 as superseded by the new slice tickets. Update PR #401's Closes and progress lists.

    Filled in while writing. Neither needs a new decision.

    • load/replaceUrls carry urlsIssuedAt, so the plugin can compute "fetch time + 24 h".
    • A started page that can't adopt a session sends close("discard").

    Written by @patricktree's agent (Claude Code, Claude Opus 5.5).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions