Flutter or native? Start with the product.
The questions I use to make a platform decision: who will use it, what must feel native and who will maintain it.
Start with the experience you want to build. List the platforms your users need, the interactions that matter most and the device features the product depends on. That list gives a technology discussion something concrete to work with.
Flutter is an option to explore when a shared mobile codebase fits the product. SwiftUI is an option to explore when the work centers on Apple platforms. Neither choice removes the need to test the experience on real devices and plan for platform-specific details.
Before committing, prototype the interaction with the most uncertainty. It might be a complex screen, a device integration or a demanding workflow. Review it with the team who will maintain the app. A small working example makes trade-offs easier to discuss than a framework comparison alone.
Independent developer. Mobile, backend & AI.
Keep reading