refactor(wear): remove legacy activities - #32
Open
Foxpace wants to merge 1 commit into
Open
Conversation
Foxpace
changed the title
This was referenced Aug 15, 2026
Foxpace
marked this pull request as ready for review
August 15, 2026 21:50
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.
Removes the old wearable activity-per-screen navigation model and leaves lightweight entry points for Compose.
What was added
How it works
The remaining entry activity hosts the Compose navigation flow. Dashboard state and typed effects now choose menus, permissions, sensor views, recording actions, and phone launch behavior without starting a separate Android activity for every screen.
Stack position
Layer 19 of 31 in the SensorBox refactor stack. Review this PR against its configured base to see only this layer.
Validation
./gradlew test— BUILD SUCCESSFUL (160 tasks)