Pokedex – Modern Android development for Pokémon
Pokedex demonstrates modern Android development with Hilt, Coroutines, Flow, Jetpack (Room, ViewModel), and Material Design based on MVVM architecture.
Tech stack & Open-source libraries
- Minimum SDK level 21
- Kotlin based, Coroutines + Flow for asynchronous.
- Lifecycle: Observe Android lifecycles and handle UI states upon the lifecycle changes.
- ViewModel: Manages UI-related data holder and lifecycle aware. Allows data to survive configuration changes such as screen rotations.
- DataBinding: Binds UI components in your layouts to data sources in your app using a declarative format rather than programmatically.
- Room: Constructs Database by providing an abstraction layer over SQLite to allow fluent database access.
- Hilt: for dependency injection.
- MVVM Architecture (View – DataBinding – ViewModel – Model)
- Bindables: Android DataBinding kit for notifying data changes to UI layers.
- Repository Pattern
- Retrofit2 & OkHttp3: Construct the REST APIs and paging network data.
- Sandwich: Construct a lightweight and modern response interface to handle network payload for Android.
- Moshi: A modern JSON library for Kotlin and Java.
- WhatIf: Check nullable objects and empty collections more fluently.
- Bundler: Android Intent & Bundle extensions, which insert and retrieve values elegantly.
- ksp: Kotlin Symbol Processing API.
- Turbine: A small testing library for kotlinx.coroutines Flow.
- Material-Components: Material design components for building ripple animation, and CardView.
- Glide, GlidePalette: Loading images from network.
- TransformationLayout: Implementing transformation motion animations.
- Custom Views
- Rainbow: An easy way to apply gradations and tinting for Android.
- AndroidRibbon: A simple way to implement a beautiful ribbon with the shimmering on Android.
- ProgressView: A polished and flexible ProgressView, fully customizable with animations.
- Timber: A logger with a small, extensible API.
Pokedex is based on the MVVM architecture and the Repository pattern, which follows the Google’s official architecture guidance.
The overall architecture of Pokedex is composed of two layers; the UI layer and the data layer. Each layer has dedicated components and they have each different responsibilities, as defined below:
Pokedex was built with Guide to app architecture, so it would be a great sample to show how the architecture works in real-world projects.
- Each layer follows unidirectional event/data flow; the UI layer emits user events to the data layer, and the data layer exposes data as a stream to other layers.
- The data layer is designed to work independently from other layers and must be pure, which means it doesn’t have any dependencies on the other layers.
With this loosely coupled architecture, you can increase the reusability of components and scalability of your app.
The UI layer consists of UI elements to configure screens that could interact with users and ViewModel that holds app states and restores data when configuration changes.
- UI elements observe the data flow via DataBinding, which is the most essential part of the MVVM architecture.
- With Bindables, which is an Android DataBinding kit for notifying data changes, you can implement two-way binding, and data observation in XML very clean.
The data Layer consists of repositories, which include business logic, such as querying data from the local database and requesting remote data from the network. It is implemented as an offline-first source of business logic and follows the single source of truth principle.
Pokedex is an offline-first app is an app that is able to perform all, or a critical subset of its core functionality without access to the internet. So users don’t need to be up-to-date on the network resources every time and it will decrease users’ data consumption. For further information, you can check out Build an offline-first app.
Pokedex adopted modularization strategies below:
- Reusability: Modulizing reusable codes properly enable opportunities for code sharing and limits code accessibility in other modules at the same time.
- Parallel Building: Each module can be run in parallel and it reduces the build time.
- Strict visibility control: Modules restrict to expose dedicated components and access to other layers, so it prevents they’re being used outside the module
- Decentralized focusing: Each developer team can assign their dedicated module and they can focus on their own modules.
For more information, check out the Guide to Android app modularization.
Pokedex using the PokeAPI for constructing RESTful API. PokeAPI provides a RESTful API interface to highly detailed objects built from thousands of lines of data related to Pokémon.
Mobile App Development Best Practices – 23.03
iOS TextEffects With SwiftUI and Physics MVVM, SwiftUI, Async/Await, and Combine: The Ultimate API Call Dream Team An Aurora Gradient...
Epic launches Unreal Editor for Fortnite and will pay creators 40% of revenue
Epic Games has announced a new payment system for the creators of Fortnite, the popular free-to-play battle royale game.
Circuit – A Compose-driven architecture for Kotlin and Android applications
Circuit is a simple, lightweight, and extensible framework for building Kotlin applications that’s Compose from the ground up. Compose itself...
Mobile App Development Best Practices – 22.03
iOS The operation couldn’t be completed: solving errors in Swift 10 Best Practices for Writing Clean and Efficient Code in...
Duolingo is working on a music app
Duolingo is gradually expanding and launching new ancillary projects that could generate significant revenue in the coming years.
Yattee – Privacy oriented video player for iOS, tvOS and macOS
Privacy oriented video player for iOS, tvOS and macOS. Features Native user interface built with SwiftUI with customization settings Player queue and...