// the find
android/architecture-samples
A collection of samples to discuss and showcase different architectural tools and patterns for Android apps.
Google's official reference implementation for Android app architecture, built as a TODO app using the current recommended stack: Compose, Navigation Compose, ViewModel, Flow, Room, and Hilt. It's a teaching tool, not a starter template — the point is to show how the pieces fit together and how to test them. Aimed at Android developers who want to understand the 'why' behind the architecture guidance, not just copy-paste a scaffold.
The test suite is genuinely good — unit tests per ViewModel, Room DAO tests, Compose UI tests, and a shared-test module with fakes that can run on both JVM and device. The mock/prod flavor split for swapping out the network data source is a clean pattern that actually works in real projects. It's actively maintained by Google's Android DevRel team and tracks current recommendations (it moved to Compose and dropped XML layouts). The separation between domain models and local/network models with explicit mapping is the right call and most tutorials skip it.
The 'fake remote' network source is a glorified in-memory list — it demonstrates the pattern but tells you nothing about what happens when real network failures, caching conflicts, or offline sync edge cases occur. The app has no real complexity: no pagination, no search, no authentication, nothing that would expose where the architecture actually gets painful. Use cases / interactors layer is absent; all business logic sits in the repository, which won't scale the moment you have shared logic across features. The branch-per-architecture-variant model sounds clever but in practice the branches diverge and comparing them means switching branches rather than reading code side-by-side.