Modern Android learning should lead from Kotlin fundamentals to a complete, tested app—not from isolated syntax videos to another tutorial clone.
Bottom line: New programmers should follow Google's free Android Basics with Compose course in order. Developers who already know another language can use JetBrains' browser-based Kotlin Tour, then move into the Compose course at the UI, data, architecture, and testing units. Treat course achievements as learning records, not professional certification.
The route-specific sequence
| Stage | Official route | Proof before moving on |
|---|---|---|
| Kotlin syntax | Kotlin beginner and intermediate tours | Model a small domain with null safety, collections, classes, and functions |
| Android setup and UI | Android Basics with Compose | Build an adaptive multi-screen Compose app |
| State and architecture | Android architecture recommendations | Explain state ownership, events, and data flow |
| Data and background work | Android course units and Jetpack guidance | Add persistence, networking, loading/error states, and scheduled work |
| Quality | Android testing guidance | Unit-test domain logic and UI behavior |
| Delivery | Android app-quality and publishing docs | Produce a release build and document privacy/accessibility choices |
Stage 1: learn enough Kotlin to read your own app
JetBrains' Kotlin Tour runs in the browser and covers beginner then intermediate language material. Focus on null safety, collections, classes, interfaces, lambdas, extension functions, and error handling. Android Studio and Gradle can wait until you can write and test a small console program.
Java developers can move faster, but should not skip Kotlin-specific nullability and coroutine concepts. Those differences affect Android APIs and state handling.
Stage 2: use Android Basics with Compose as the spine
Google describes Android Basics with Compose as a self-paced course built around Kotlin, Jetpack Compose, Jetpack libraries, adaptive layouts, data storage, network access, architecture, and testing. It starts without a programming prerequisite and includes codelabs, quizzes, and projects.
Do the projects without copying the final solution. Rebuild one screen from a sketch, add a second screen, rotate or resize the device, and verify that state behaves as intended.
Stage 3: make state and data flow explicit
After basic Compose, read Android's architecture recommendations. Your app should have a UI layer and a data layer, use a single source of truth for important data, and expose observable state. The exact module count matters less than whether you can explain who owns state and how an event becomes a data change.
Build a repository backed first by a fake data source, then by local persistence or a network service. Preserve loading, empty, error, and offline states rather than designing only the happy path.
Stage 4: test the behavior that can regress
Write unit tests for domain and data logic, then Compose UI tests for one critical flow. A credible portfolio app should demonstrate that a state transition and user-visible outcome are verified automatically. Manual screenshots alone do not show maintainability.
Capstone: an offline-capable task or field-notes app
Build an app with at least three screens, Compose navigation, local persistence, a remote sync or import boundary, background work, adaptive layouts, accessibility labels, and tests. Include a README with architecture, data ownership, failure cases, and release steps. That capstone directly exercises the official path without pretending to be a production-scale app.
Courses versus certification
Google's training pages may expose badges, achievements, or certification links, but finishing a learning path is not automatically an assessed professional credential. Verify the exact assessment and issuer terms before calling any result a certification. For ranked course alternatives, use Best Kotlin & Android Courses 2026. Compare cross-platform study only after this choice through Best Flutter & Dart Courses 2026.
CourseFacts uses plain outbound links in this guide. No affiliate or sponsored relationship is implied unless a link is explicitly labeled that way.
Sources
CourseFacts checked the Kotlin Tour, Android Basics with Compose, Android architecture recommendations, and Android testing guidance on 2026-08-11. The pages support curriculum and platform practices; the sequence and capstone are editorial recommendations.