|
Hey MailingR
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
8.01.2024.
You get:
- 6 weeks online program
- 12 months access to course materials and future updates
- Practical assignments for each module
- Private channel on Discord
- TWO GUARANTEES
I believe in this program.
But you don't have to at a moment. And that's OK.
How could possibly you believe in it's effectiveness if you're not learning from it?
I want you to make an informed decision - I'm giving you TWO guarantees.
Double guarantee
First one – 14 days guarantee – if you decide that this program is not for you, you get your money back.
Unconditionally.
I may ask you what you didn't like about it, but I will ask AFTER I'll issue a refund. You have 14 days no-questions-asked guarantee (starting from first lecture on 8.01.2024).
Second one – 90 days guarantee.
If it turns out that you didn't learn anything or that processes described in program don't work for you or your team – you can get your money back.
You have 90 days for it.
But there's one condition. You have to show me that you did your assignments.
Deal?
|
