Discofork
Repository brief

android/architecture-samples

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T12:48:21.974Z
3mo ago

android/architecture-samples

android/architecture-samples is a well-known, actively maintained Android app sample repo focused on architectural patterns. It uses a simple TODO app to demonstrate Jetpack Compose, Navigation Compose, ViewModel, Flow/coroutines, Room-backed data access, Hilt, product flavors, and a mix of unit, integration, e2e, and shared tests. For fork decisions, it is most interesting as a reference implementation and experimentation base, not as a production app template or polished UI sample.

GitHub
Loading tags...
Stars45,621
Forks11,874
Default branchmain
Last pushed2026-03-25T21:15:52Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose the fork only if you want an older Kotlin/coroutines architecture example and are comfortable working on a stale, heavily diverged codebase. If you want the current Android architecture reference, upstream is the better choice.

Choose this fork only if you want a legacy snapshot of the architecture samples repo. For most adopters, upstream is the better choice because this fork is stale and materially behind on modern Android architecture features.

Prefer upstream for learning or reuse. Choose this fork only if you want a dated snapshot with a README that clarifies the fork's intent.

Choose this fork only if you specifically want a Conductor-style legacy architecture example. For most adopters, upstream is far better because it is much newer, actively maintained, and covers modern Compose-based Android patterns.

Prefer upstream unless you specifically need an old snapshot. This fork adds no visible improvements and is materially behind, so it is a poor choice for learning or adopting current Android architecture patterns.

Prefer upstream unless you need a frozen historical copy. This fork offers little unique value and is materially behind current Android architecture guidance.

Prefer upstream for new work. Choose this fork only if you need a frozen historical version or must stay compatible with its older baseline.

Prefer upstream unless you explicitly need the 2017 snapshot. This fork adds no visible capabilities and mostly represents maintenance lag, so it is a weak choice for new adoption.

Choose this fork only if you explicitly want the older Kotlin MVP sample. If you want a current Android architecture reference or a base for new work, upstream is far more suitable.

Prefer upstream for almost any adoption decision. This fork is too stale and too lightly differentiated to justify choosing it unless you specifically need its older documentation snapshot.