Get live statistics and analysis of Jesse Ezell's profile on X / Twitter

Open source, but not open to your contributions.

👏

Compose Multiplatform and React Native already support Liquid Glass. Flutter's official stance: "We don't support it, we ain't gonna tell you anything about our plan to support it, and we won't accept any PRs if you want to help make it happen"

Interesting. I heard from the Flutter team that bundle size is more important than features.

Apple: got serious about phones, built a new modern language (swift) to make writing apps easier, ports their frameworks to the language, and evolves it with the frameworks to make apps easier to build. Google: got serious about phones and picked an old crappy language to use (java). Language sucks so much that everyone leaves it for a language made by another company (kotlin). Meanwhile, they make their own language (dart) that's pretty amazing, and build a complete rendering engine and framework on top of it (flutter) but continue to squander their investments by not actually using it in a first class way in any OS or platform they ship.

A lot of people think it's weird that I still use Flutter despite talking about the challenges we face on a regular basis. I still believe it's the best cross platform framework by far. The reason we use Flutter is because there are a community of people solving the same problems with us. React Native is great if you only ship mobile apps, but React Native only recently even started to think about a real cross platform story that includes web. Expo DOM components show potential, but they haven't even been around a year yet, and even they aren't really the same thing (more like the inverse of the old Flutter web renderer that got canned because it wasn't good enough). Maybe at some point there will be something equivalent or better shipped by some other team, but even with all the rough edges, Flutter is still a lot farther along than the rest of the people trying to do the same thing. The grass isn't always greener on the other side. Sometimes you just have to deal with the grass in your own yard even if there are a few weeds.

Flutter is trending on Github. Maybe my prediction that AI boom is gonna give a massive boost to Cross Platform tools is coming true...

My iOS 26 impressions so far. Flutter needs to bring back the jank so the apps feel like the native ones.

Flutter on Twitter has 264k followers. Flutter on the other one has 926 followers. Totally makes sense that they are deleting their Twitter info from their socials list in github.

Apple sure likes hiring Flutter leadership….

It took me an afternoon to build a go_router replacement with support for path based routing that solves all the problems we had with go_router like no ability to replace state in the browser history, stateful shell routes being garbage, etc. Only 150 lines of code. Go router should be deleted from every Flutter project. It's so bad. The lower level routing API docs aren't that great and the linked examples don't use the current APIs, but it's easier to make them work than it is to make go_router work.

Compose Multiplatform and React Native already support Liquid Glass. Flutter's official stance: "We don't support it, we ain't gonna tell you anything about our plan to support it, and we won't accept any PRs if you want to help make it happen"

Open source, but not open to your contributions.

Apple: got serious about phones, built a new modern language (swift) to make writing apps easier, ports their frameworks to the language, and evolves it with the frameworks to make apps easier to build. Google: got serious about phones and picked an old crappy language to use (java). Language sucks so much that everyone leaves it for a language made by another company (kotlin). Meanwhile, they make their own language (dart) that's pretty amazing, and build a complete rendering engine and framework on top of it (flutter) but continue to squander their investments by not actually using it in a first class way in any OS or platform they ship.

First things you should do with any Flutter project: 1) Setup CI with codemagic 2) Don't allow people to push to main 3) Enforce checks on pull requests for formatting and dart analysis that must be passed before pull requests can be merged. You'll save yourself a lot of pain later if you start out with this.

Flutter on Twitter has 264k followers. Flutter on the other one has 926 followers. Totally makes sense that they are deleting their Twitter info from their socials list in github.

Apple sure likes hiring Flutter leadership….

It's decided. We're going down the path of running our own flutter web builds as part of our standard build processes. Too much work to try to file issues about memory leaks and hangs with the Flutter team just so they can close them. We'll run our own fork.

New idea. All packages are removed from the packages repo and split into normal Github repos. New requirement for Flutter GDEs: you must maintain one of those packages and be able to show how you made it better, or you are no longer a GDE.

SnapChat releases their internal ReactNative competitor.

Dynamic is used way too much in dart. Dynamic sucks.

👏