How I think about building mobile apps in 2026

There are a lot of opinions about how mobile apps should be built. Frameworks, architectures, best practices… everyone has a take. But over time, I realized something: Building apps is less about following rules and more about making good decisions. So instead of talking about “the right way,” this is how I personally think about building mobile apps today. Start simple (really simple) It’s very tempting to start with a full structure: Clean architecture Multiple layers Abstractions everywhere But most apps don’t need that on day one. What they need is: To work To be understandable To be easy to change So I start simple. And only add complexity when it’s justified. Structure follows problems I don’t decide architecture upfront anymore. Instead, I let the app push me toward structure. If logic starts repeating → I extract If data sources grow → I separate If things get hard to maintain → I refactor Architecture becomes a response. Not a starting point. State is the real challenge Screen