Celebrating Flutter's "Production Era"

developers.googleblog.com

13 points·wallflower··5 comments

Am I the only one who has never seen a halfway performant Flutter app?

Also, the examples seem odd? The "Universal Studios performance and reliability" section doesn't say anything about performance. And the LG example just states that native apps are better than web-apps with no further info. So that's 2 production performance examples where performance was apparently not good enough that they feel confident to share any metrics?

Google pay is made with flutter.

https://flutter.dev/showcase/google-pay

And many others https://flutter.dev/showcase

So in 2025, what’s the best way to do mobile apps, React native, flutter, or straight up swift / kotlin?

Define "best". Cheapest, theoretically? Cross platform. Cheapest, realistically? They're all about the same. Fastest to market, theoretically? Cross platform. Best performance? Native. Most features? Native. Best system integration? Native.

Cross platform is really only "best" if you can make the investment needed to make it truly universal. That means sanding over the inevitable platform differences even Flutter and RN still expose, debugging platform specific issues, and bridging new system features ahead of official release. Without such strict discipline, cross platform teams are just as large, and therefore expensive, as native teams.

I usually see cross platform in big corps which want to homogenize their development teams, for better or worse (hence why RN is still popular). It doesn't actually cost them any less or make them any faster (their bottlenecks are in planning and dependent features), but requires less thinking for planning and hiring.

I'm so scared of building something with Flutter and relying on Google to keep it around.

Reply on news.ycombinator.com