android/architecture-samples

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.