skydoves/pokedex

🗡️ Pokedex demonstrates modern Android development with Hilt, Material Motion, Coroutines, Flow, Jetpack (Room, ViewModel) based on MVVM architecture.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 7th, 2026
Created on June 1st, 2020
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 1,111
Total Stargazers: 8,358 (+0)
Total Subscribers: 187 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.0 days
Mean response time: 16.0 days
90th percentile: 62.4 days
Tracked items: 6

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 565 days
Stale 30+ days: 4
Stale 90+ days: 4

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

Pokedex is an Android application that demonstrates modern development practices using Hilt, Coroutines, Flow, and Jetpack libraries within an MVVM architecture.

The project addresses the need for a real-world example of contemporary Android development patterns. It showcases how to structure an Android application using dependency injection through Hilt, asynchronous programming with Coroutines and Flow, and Jetpack components including Room for local persistence and ViewModel for state management. The architecture follows MVVM principles, separating concerns between the user interface, business logic, and data layers. Material Design and motion animations are integrated throughout the application to demonstrate modern UI practices.

Pokedex serves as a learning resource for Android developers seeking to understand how established libraries and architectural patterns work together in practice. It is particularly suited for developers building feature-rich applications that require offline data caching, reactive data flows, and clean separation of concerns. The project provides a complete, working example rather than isolated code snippets, making it valuable for those transitioning from older Android development approaches to current best practices.

The project maintains active development with regular updates to dependencies and code patterns. The codebase receives ongoing refinement to reflect current Android development standards. The project includes automated testing infrastructure through continuous integration workflows. Documentation is supplemented with external resources including technical articles and video content that explain the architectural decisions and library usage demonstrated in the code.