45.9K ·GitHub
What is this?
It's a collection of sample implementations of the same to-do app, each built on a different branch with a different Android architecture approach, meant to showcase and compare architectural patterns like MVVM with Compose, Hilt and Room.
It's a collection of sample implementations of the same to-do app, each built on a different branch with a different Android architecture approach, meant to showcase and compare architectural patterns like MVVM with Compose, Hilt and Room.Is this a starter template I can build my app on?No — the README explicitly says it's not a template, not a UI/Material Design showcase, and not a production app with real networking or auth. It's a reference implementation focused purely on architecture.
No — the README explicitly says it's not a template, not a UI/Material Design showcase, and not a production app with real networking or auth. It's a reference implementation focused purely on architecture.How do I open one of the samples?Clone the repo, check out the branch for the architecture variant you want, then open the architecture-samples/ directory as a project in Android Studio.
Clone the repo, check out the branch for the architecture variant you want, then open the architecture-samples/ directory as a project in Android Studio.Do I need anything besides Android Studio?No, just Android Studio — the repo is self-contained and uses Gradle, so opening the directory handles the rest.
No, just Android Studio — the repo is self-contained and uses Gradle, so opening the directory handles the rest.What does the main branch's architecture actually look like?It uses Jetpack Compose for UI, Navigation Compose with a single-activity setup, a ViewModel per screen, Flow/coroutines for reactivity, a repository backed by Room plus a fake remote source, and Hilt for dependency injection — there's no real network layer.
It uses Jetpack Compose for UI, Navigation Compose with a single-activity setup, a ViewModel per screen, Flow/coroutines for reactivity, a repository backed by Room plus a fake remote source, and Hilt for dependency injection — there's no real network layer.Why a to-do app specifically?It's simple enough to understand quickly, but complex enough to surface real architecture and testing decisions, which is exactly what the samples are meant to demonstrate.
It's simple enough to understand quickly, but complex enough to surface real architecture and testing decisions, which is exactly what the samples are meant to demonstrate.Are there other architecture variants besides the main branch?Yes — other branches implement the same TODO app with different architectural approaches, so you can check out each one and compare them side by side.
Yes — other branches implement the same TODO app with different architectural approaches, so you can check out each one and compare them side by side.Does it include tests?Yes, it ships with unit, integration and end-to-end tests, including shared tests that run on an emulator or device.
Yes, it ships with unit, integration and end-to-end tests, including shared tests that run on an emulator or device.Where should I look for an actual project starter instead?The README points to a separate 'Architecture Templates' project for bootstrapping real apps, and to 'Now in Android' for a full production example with networking and auth.
The README points to a separate 'Architecture Templates' project for bootstrapping real apps, and to 'Now in Android' for a full production example with networking and auth.What are similar projects?nowinandroid, compose-samples, Android-CleanArchitecture, android-best-practices, iosched, go-clean-arch, MVPArms, ios-good-practices
nowinandroid, compose-samples, Android-CleanArchitecture, android-best-practices, iosched, go-clean-arch, MVPArms, ios-good-practicesWhich topics is it in?coroutines, sample-app, samples, compose, clean-architecture, mvvm, dependency-injection, unit-testing, examples, architecture, mobile-development, best-practices
coroutines, sample-app, samples, compose, clean-architecture, mvvm, dependency-injection, unit-testing, examples, architecture, mobile-development, best-practices