Add transport-agnostic Wear OS sync interface (issue #276) - #279
Merged
Merged
Conversation
Step 2 of Wear OS phase 1: the WearSyncClient interface, its SyncQueueItem/PositionUpdate DTOs, and QueueSyncMapper give the queue- push and position-sync logic a real Kotlin API to compile against before the Play Services-backed implementation exists. FakeWearSyncClient keeps that logic unit-testable without touching the real Data Layer API, which needs Play Services and isn't practical under Robolectric. Still no working Wear OS functionality -- no :wear module, no real DataClient-backed implementation, no watch UI. This just gives the next steps something to build against.
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 2 of #276 (see #278 for step 1). Adds the
WearSyncClientinterface, itsSyncQueueItem/PositionUpdateDTOs, andQueueSyncMapperto:core— a transport-agnostic seam over the Wear OS Data Layer API that the queue-push and position-sync logic (steps 3-4) will compile against.FakeWearSyncClientlets that logic be unit tested without a realDataClient, which needs Play Services and isn't practical under Robolectric.Still no working Wear OS functionality on its own — no
:wearmodule, no real Play Services-backed implementation, no watch UI. This is groundwork for the remaining steps toward #276.Test plan
./gradlew assembleDebug testDebugUnitTest lintDebugpasses