Native Android — Kotlin + Jetpack Compose
An Android app with Compose screens and Kotlin services around platform APIs, with explicit state ownership, device testing, and task-specific background scheduling.
Sources verified Sep 2026
Circumstances — when to use it
- Android is the first platform being implemented
- Device APIs and Android-specific behavior shape the product
- The team can maintain Android-specific code and test across device vendors
- A separate iOS implementation is acceptable if it is needed later
Synergy — how the pieces fit
Jetpack Compose renders UI from state; ViewModels expose screen state and receive user actions, while repositories and platform services own data and device operations. Kotlin coroutines coordinate asynchronous work without putting side effects in composable rendering. Choose a background API for the actual task: WorkManager handles persistent deferrable work, while user-visible ongoing operations may need a foreground service under Android's restrictions. Native code does not bypass permission, battery, or lifecycle rules. Test the core hardware flow on physical devices and handle process recreation before polishing screens.
The tech and its role
Architectural examples
Each example links to a public source — no claims about private internals.
Now in Android
Google's public reference app is built with Kotlin and Jetpack Compose and documents its architecture and adaptive UI. Reference app example; not a claim that it implements Bluetooth or AR.
sourceJetchat
Google's Compose chat sample shows state management, a ViewModel, and interoperability with existing Views. A UI learning sample, not a production messaging backend or background-service template.
sourceSkip if
Skip if iOS is the first target, or one shared UI implementation across iOS and Android is a hard requirement.