igorwojda/android-showcase

💎 Android application following best practices: Kotlin, Coroutines, JetPack, Clean Architecture, Feature Modules, Tests, MVVM, DI, Static Analysis...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 9th, 2026
Created on November 20th, 2018
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 909
Total Stargazers: 6,795 (+0)
Total Subscribers: 109 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 314.8 days
Mean response time: 845.4 days
90th percentile: 2162.8 days
Tracked items: 3

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,868 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Android Showcase is a reference Android application demonstrating production-ready architecture and development practices using Kotlin, Jetpack Compose, and Clean Architecture principles.

The project addresses the challenge of establishing scalable, maintainable architectural foundations for large-scale Android applications. It implements this through modular design organized into feature modules, each following a layered structure with presentation, domain, and data layers. The application itself is a music discovery app that fetches album information from the Last.fm API, demonstrating real-world scenarios including network requests, local caching, navigation, and state management. The architecture emphasizes separation of concerns through convention plugins, type-safe dependency management, and unified version configuration via Gradle.

Teams building large Android projects should consider this repository as a reference for establishing solid architectural patterns. The modular approach with feature modules makes it suitable for projects that need to scale across multiple teams or features. The project demonstrates advanced Gradle configuration including configuration caching and pre-push hooks for code verification. The README does not position this against specific alternative frameworks or architectural approaches, but rather presents it as a comprehensive example of industry-standard practices.

The project maintains active development with attention to code quality through static analysis and CI pipeline practices. Convention plugins and type-safe project accessors indicate ongoing refinement of the build infrastructure. The inclusion of pre-push hooks and comprehensive code verification suggests a focus on maintaining standards across contributions. Documentation is extensive, covering module types, data flow, and development workflows, reflecting investment in making the codebase accessible to new developers.