Our great sponsors
-
I would definitely avoid putting everything in the Activity. Usually you want to separate your code between multiple layers like data, domain and view. Then you can choose a pattern like MVVM, MVI or MVP (MVP is not used that much anymore). Here you have a repo I made with a reactive MVVM example: Github Reactive MVVM with Flows
-
architecture-samples
A collection of samples to discuss and showcase different architectural tools and patterns for Android apps.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
pomodoro-scheduler
Discontinued This is a simple and configurable pomodoro timer [Moved to: https://github.com/emenjivar/pomodoro-timer]
I'm also working in my own small project following the same structure, Just in case you want to see an example.
Related posts
- 3 Reasons Why I'm not Migrating LiveData to StateFlow
- I need a repo with a modern and advanced architecture for an Android project. Can you help me?
- Example code for seprate business logic from UI layer in flutter.
- Delish, a Food Recipes App in Jetpack Compose with MVI architecture
- I am a graduate who wants to become an Android developer. Any advice please?