Is Flutter still a good choice for launching a project in the future?

13 Tem 14:44

I've been doing freelance projects on Flutter since 2022, especially developing quick MVPs for startups. With version 3.0, I've thoroughly tested performance improvements (.widget rebuild optimizations, more stable engine) and web/desktop support (Windows/Linux/Mac). Based on my experience, if you're targeting only mobile, you're still ahead of competitors with Firebase integration, the flexibility of Material3 and Cupertino styles; but if you've also transitioned to desktop (in one of my projects, I switched to Flutter and reduced 2,000+ lines of SwiftUI code to 30%, quite an interesting experience), I can confidently say it's stable. There might be minor hiccups when dealing with js_compiler and such materials, but overall, I see it as a preferred choice.

13 Tem 16:40

Thanks for asking a smart question. I think Flutter is still a very valid choice, especially for cross-platform targets, but it depends on the project's requirements, right? Which way are you leaning?

13 Tem 17:09

A couple of years ago, I launched an MVP with Flutter for a local event management app in Madrid, and honestly, the process was easier than I expected. I chose it because we could iterate quickly with a small team, and the hot reload was a lifesaver when debugging. That said, the "cross-platform" part is real: in the end, I had to deal with some weird behaviors on iOS that didn’t show up on Android, but nothing that a few widget tweaks couldn’t fix. What really surprised me was how well it scaled when we added web support just in case—almost no code changes and no headaches. Of course, it wasn’t all perfect. For the desktop version (specifically Linux), some plugins weren’t fully mature, so I had to work around it with a native bridge. Then there’s the cost: while the framework itself is free, if you want more than the basics, premium plugins or Firebase services add up. But looking back, for a project like mine—an MVP with tight deadlines—Flutter was the right choice. Now, for a new project, I’d still pick it, but only if the team is willing to invest time in testing it thoroughly before fully committing. What do you guys think if you’ve had experience with it?

13 Tem 17:34

Since Flutter 3.0, it has gained significant momentum, especially with performance optimizations and web/desktop support—but is it cost-effective for cross-platform beyond mobile? I’d say yes, but only for the right use cases. Flutter’s biggest advantage is its ability to run on both iOS and Android (and now Linux, macOS, and Windows) with a single codebase. This makes it ideal for MVPs, prototypes, or projects where small or large teams need to optimize resources. However, the key here is recognizing that if performance is critical, Flutter may not be the best choice for native components. For example, in low-level control scenarios like game engines, Flutter still has limitations. When comparing alternatives, React Native remains the biggest competitor, but it comes with the baggage of the JavaScript/TypeScript ecosystem. Native solutions like SwiftUI or Jetpack Compose offer performance and platform compatibility advantages, but they come with higher development costs and steeper learning curves. If desktop is your focus, Electron is an option, though I find it lags behind Flutter in performance. Flutter’s downside, however, is that its package ecosystem can sometimes be unstable—especially when you need platform-specific features. That said, it’s maturing rapidly. Personally, I prefer Flutter because it significantly reduces development time and costs. But if a project demands high performance or very specific hardware integration, going native makes more sense. Ultimately, it depends on the project’s requirements. Flutter’s future looks bright, but it’s not a one-size-fits-all solution.