In Android communities you often hear question…
"What's the best UI architecture for Android apps?"
The internet is filled with debates, articles, and tutorials championing one approach over another. MVVM, MVI. Let’s answer it once and for all.
Beyond the Hype
It's easy to get caught up in the latest trends and just use MVVM because it’s “recommended” by Google. After all, if it's making waves in the developer community, it must be the best, right? Not necessarily. The best choice isn't always the most popular or the most talked about. It's the one that fits your app's needs, your team's expertise, and your project's long-term goals.
Understanding Your Needs
Before settling on an architecture, it's crucial to understand the specific requirements and challenges of your app. - Does your app rely heavily on real-time data?
- Is it UI-intensive?
- Does it makes sense to use unidirectional data flow?
- Or is it overkill?
The answers to these questions can guide you towards an architecture that addresses your app's unique challenges.
I generally go: - focus on display - MVVM
- focus on events - MVI
Team Expertise Matters
The best architecture on paper can quickly become a nightmare if your team isn't familiar with it. It's essential to consider your team's expertise and comfort level. Sometimes, it's more beneficial to go with a well-understood architecture rather than spending valuable time climbing the learning curve of a new one. That’s right. The question is not “what’s the best approach”, but “what’s the optimal approach for us” So, what's the best MV(x) for Android apps? It's not a one-size-fits-all answer. It's not necessarily MVVM, MVI, or MVP. It's the one that aligns with your app's needs, leverages your team's strengths, and sets you up for future success. It may be something in between. What’s really important, is separating the View from the Model.
And if you don’t want to follow the hype and make conscious architectural decisions, join The Android Architect.
It’s the only program that teaches you: - Clean Architecture
- Model-View patterns
- Working with domain layer
- Mobile dev ops
Enrollment is open and we’re starting 2.10.2023.
You get: - 6 weeks online program
- 12 months access to course materials
- Practical assignments for each module
- Private channel on Discord
- 100% satisfaction guarantee. 14 days since to course starts to get a full refund. No questions asked.
Check the course website - you will find there FAQ section with most common queries.
But if you want to ask me anything directly, do not hesitate and reply to this email. I read every message and I answer to all of them.
In the upcoming days I’ll be online everyday, so you can catch me here, on Twitter or LinkedIn.
Thank you for everything! See you in The Android Architect!
Best, Jarosław Michalik
ps. Remember - you risk nothing. You have 14 days since the first lecture start to get 100% refund. Your satisfaction is my nr #1 priority. pps. Are you wondering how to use training budget for financing The Architect program? I’ve put 3-step instruction for you (with copy-paste ready emails for your boss)
| 