Deep dive into Wear OS app architecture
summary
Shows how a standalone Wear app reuses mobile data and domain layers to implement a Generic Fitness tracker (150 minutes/week goal) while writing minimal Wear-specific UI. Demonstrates concrete pieces: GetWeeklyProgressUseCase combines historical and current-session flows, Surface Updater requests tile and complication refreshes, and Horologist supplies TileLayoutRenderer, coroutine-friendly TileService wrappers, and a DrawScope→bitmap trick to reuse Compose charts inside tiles. Covers modular project layout, Compose for Wear, and the end-to-end approach that works in practice.
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
44mCreate engaging apps for Wear OS
36mCreating your first Wear OS app using compose
35mIt's Time to Build for Wear OS
32mDeveloping Wear OS Apps with Jetpack Compose
49mBootstrapping Multiplatform Development and Android Wear
28mCreate beautiful, power-efficient apps for Wear OS
22mBuild a modern and expressive Wear OS app