Use as a blueprint when setting up Clean Architecture layers in your own Android Kotlin app.
Study how feature modules keep screens self-contained and prevent cross-area breakage.
Copy the GitHub Actions CI setup to add automated linting and unit tests to your Android project.
Learn how Jetpack Compose, Room, and Coroutines fit together in a real multi-screen app.
Requires Android Studio with Kotlin support and a device or emulator to run the app.
Android Showcase is a sample Android application built to demonstrate how to structure a production-ready mobile app using modern tools and patterns. The app itself is a music discovery tool: it fetches album information from the Last.fm music API and displays it in a browseable list, with a detail view for each album and a favorites screen still in development. It is not a finished product for end users but a reference project for Android developers who want to see how the pieces fit together. The project uses Kotlin as its programming language and builds its screens with Jetpack Compose, Google's approach to constructing Android UIs in code rather than XML layouts. For background work like network calls and data loading, it uses Coroutines and Flow, which are Kotlin tools for managing tasks that happen asynchronously without freezing the screen. Data retrieved from the network is cached locally using Room, a database library that stores information on the device. The code is organized around Clean Architecture, a pattern that separates an app into three distinct layers: presentation (what the user sees), domain (the business rules), and data (where information comes from and how it is stored). On top of that structure, the project uses feature modules, meaning each screen or section of the app lives in its own self-contained code package. This keeps different parts of the app from tangling together and makes it easier to work on one area without accidentally breaking another. Testing is built in throughout. The project uses JUnit for unit tests and Mockk for creating controlled test substitutes. Static analysis tools including Detekt and Ktlint scan the code for formatting problems and potential bugs before anything is submitted. A CI pipeline on GitHub Actions runs all of these checks automatically on every pull request. The README covers the full architecture with diagrams, explains each layer and module type, and lists every library with a short description of its role. It is aimed at Android developers who want a single concrete reference showing how all of these tools work together in one project, rather than piecing together separate documentation for each tool individually.
← igorwojda on gitmyhub — every repo by this author, as a profile.
Verify against the repo before relying on details.