Add the watch's queue and now-playing screens (issue #276) - #283
Merged
Merged
Conversation
Step 6 of Wear OS phase 1 -- the last step before this is a real, usable watch app. Replaces the placeholder MainActivity screen with two Wear Compose screens over a SwipeDismissableNavHost: - QueueScreen: the local (synced) Next Up list as Chips, read-only (no reorder/remove -- those stay phone-side edits that sync down). Tapping an episode starts it via WearPlaybackController and navigates to the now-playing screen. - NowPlayingScreen: title/feed/position and a play/pause Chip, a thin pass-through to WearPlaybackController's state -- no seek bar/chapters/speed controls, trimmed the same way WearPlaybackUiState itself is. QueueViewModel/NowPlayingViewModel are both thin StateFlow pass-throughs over QueueRepository/WearPlaybackController, mirroring :app's QueueViewModel/in-page player relationship to their own equivalents. Verified end-to-end on the mycasts_wear_test emulator: seeded a test episode directly into the watch's local database (no phone pairing available in this environment -- see the sync bridge PR's same caveat), launched the app, confirmed the queue Chip renders, tapped it, confirmed navigation to the now-playing screen, confirmed real audio actually streamed and played over the emulator's network connection, and confirmed auto-advance correctly emptied the queue and reset the UI to "Nothing playing" once the episode finished.
This was referenced Sep 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Step 6 of #276 (see #278-282 for steps 1-5) -- the last step for phase 1. Replaces the placeholder
MainActivityscreen with two real Wear Compose screens over aSwipeDismissableNavHost:QueueScreen: the local (synced) Next Up list as Chips, read-only (no reorder/remove -- those stay phone-side edits that sync down). Tapping an episode starts it viaWearPlaybackControllerand navigates to the now-playing screen.NowPlayingScreen: title/feed/position and a play/pause Chip, a thin pass-through toWearPlaybackController's state -- no seek bar/chapters/speed controls, trimmed the same wayWearPlaybackUiStateitself is.QueueViewModel/NowPlayingViewModelare both thinStateFlowpass-throughs overQueueRepository/WearPlaybackController, mirroring:app'sQueueViewModel/in-page player relationship to their own equivalents.This closes out phase 1 (issue #276) -- phase 2 (#277) is sending downloaded episodes to the watch for offline playback.
Test plan
./gradlew assembleDebug testDebugUnitTest lintDebugpasses across:app/:core/:wearmycasts_wear_testemulator, since no phone pairing is available in this environment (same caveat as the sync bridge PR): seeded a test episode directly into the watch's local database, launched the app, confirmed the queue Chip renders correctly, tapped it, confirmed navigation to the now-playing screen, confirmed real audio actually streamed and played over the emulator's own network connection, and confirmed auto-advance correctly emptied the queue and reset the UI to "Nothing playing" once the episode finished