Deep dive into Wear OS app architecture
summary
Shows how a Wear OS app can be added to an existing mobile project and stay standalone by syncing via the cloud, not the wearable data layer. Reuses data and optional domain layers (a GetWeeklyProgressUseCase combines historical + current session), uses Wear Health Services for sensors, and provides concrete helpers: Horologist’s TileLayoutRenderer and DrawScope-to-bitmap bridge for tiles, plus a Surface Updater to request tile/complication refreshes intelligently.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:58Generic Fitness
- 3:42Structure
- 4:00Modularization
- 6:48Data Layer
- 10:55Domain Layer
- 14:07Horologist
related talks
20mDeep dive into Wear OS app architecture
35mIt's Time to Build for Wear OS
44mCreate engaging apps for Wear OS
36mCreating your first Wear OS app using compose
49mBootstrapping Multiplatform Development and Android Wear
32mDeveloping Wear OS Apps with Jetpack Compose
28mCreate beautiful, power-efficient apps for Wear OS
22mBuild a modern and expressive Wear OS app