Note
What four years of Flutter taught me
Four years is long enough for a framework to stop feeling like a choice and start feeling like a place you know.
Flutter has taken me from rough prototypes to apps in the store. Along the way, it taught me things that are useful far beyond Flutter.
Consistency creates speed
The biggest advantage was not hot reload or one codebase. It was accumulated familiarity. I know where problems tend to live. I know which abstractions I will regret. I can feel when a widget tree is about to become a small forest.
That kind of speed is difficult to benchmark, but very real.
Cross-platform is still product work
Sharing code does not remove platform decisions. iOS and Android users carry different expectations, and the details still matter:
- navigation behaviour
- keyboard handling
- permissions
- typography
- the tiny pauses that make an interface feel native or strange
The goal is not identical pixels. The goal is an experience that feels at home.
The framework matters less over time
Early on, I thought good Flutter work was mostly about knowing Flutter. Now I think it is more about product judgement: what to leave out, where to spend time, and how to make the common path feel obvious.
Framework knowledge gets the app built. Taste decides whether it is worth using.
I still reach for Flutter when it fits. I just reach for it with fewer strong opinions and more useful questions.