If you’ve followed my journey, you know I have a deep-rooted love for Flutter. It has been my go-to tool, my playground, and the foundation of some of my favorite projects. But growth often requires stepping out of our comfort zones, and recently, my career trajectory has started to shift.
I am moving away from being a pure Flutter specialist and stepping into the broader world of full-stack development.
This wasn’t a decision I made overnight, nor is it a knock against the framework. Rather, it’s a reflection of where the industry is heading and where I want to be as an engineer. Here is why I am making the shift.
Reasons for the move
Looking back I can name three main reasons for this shift:
- The full-stack imperative
- The web reality
- The generalist mindset
The Full-Stack Imperative
The market is changing rapidly. With the explosive rise of AI, the industry increasingly demands engineers who can navigate the entire stack, rather than just the frontend. Building end-to-end solutions has become the baseline expectation.
While I think Serverpod is a fantastic initiative for the Dart ecosystem, we have to be realistic. At the moment, it simply misses the deep feature richness, mature ecosystems, and enterprise backing that server-side heavyweights like Go, Python, and Java possess. To build truly scalable, complex backends, I needed to expand my toolkit.
The web reality
We have to talk about Flutter on the web. Is it okay? Yes, for certain use cases like internal dashboards or highly interactive web apps. But companies are justifiably hesitant to use it for public-facing websites.
When you compare Flutter Web to dedicated web technologies like React, Next.js, or Astro, the limitations become apparent. From SEO hurdles to bundle sizes and the lack of a “native web” feel, the DOM-first frameworks still hold the crown for web development. Understanding these tools is crucial for delivering the right solution to the right problem.
Generalist mindset
Last year, in 2025, I had a realization: being a specialist in a single framework is no longer the safest or most fulfilling career choice. Technology moves too fast.
Beyond career strategy, I honestly just felt the itch for a new challenge. I wanted to understand the cloud, build resilient APIs, and master the web DOM. That drive pushed me to dive deep into Golang, Python, and React, and I recently achieved my AWS Cloud Architect certifications. The transition has been challenging, but incredibly rewarding.
The Future of Flutter is Still Bright
Now, does this mean I’m abandoning Flutter? Absolutely not. In fact, I am still super optimistic about the future of the framework and the ecosystem surrounding it.
Architectural Wins: I think the recent move to decouple the UI libraries is a brilliant architectural decision that will allow the team to ship UI features much faster.
Continued Commitment: I remain deeply invested in the community and will continue my role as the maintainer of Flutter Stripe.
Ecosystem Maturation: We are seeing massive companies adopting Flutter for their mobile fleets. Serverpod is becoming an amazing framework that will only get better, and tools like Shorebird are actively breaking down the tedious app release cycles that mobile devs have dreaded for years.
I’m not breaking up with Flutter; I’m just taking off my blinders. I’m evolving from a Flutter developer into a software engineer who happens to love Flutter.