Mitch Koko

So recently I became less stubborn and decided to give a try to other frameworks besides Flutter for mobile apps. I worked with React Native, Swift and Kotlin Multiplatform. Here are my conclusions so far: 1) Indeed, native (Swift and Kotlin) looks and feels much better and "premium" almost out of the box 2) Claude Opus is doing way worse with Swift compared to Flutter or even React Native. Lots of mistakes. Lots of thread issues. It feels like we're back to Claude 3.5 Sonnet. I needed to do a lot of iterations to make something look or work right. Sometimes I needed to delegate it to Codex. With Flutter... it just worked. 3) Flutter indeed looks flat and kind of unpolished compared to native (or maybe even React Native), but it's way faster to build with it (both because Claude is good with it and also because builds are fast) 4) React Native is good and looks good, but takes a long time to build (yes yes I know Expo). Also it requires extra time on adjusting UI on both platforms so it's not as out-of-the box as Flutter. 5) KMP -- I'm still testing it and I'm still undecided whether to have one common UI or two separate. I have high hopes regarding this framework as it combines best of both worlds (native UI + cross platform logic) So right now I'd say: - if you go for the look and feeling, go with native or KMP or maybe with RN - if you just build for one platform, choose native - if you want cross-platform and you want to build it fast, have a limited budget for testing, and you don't care that much about the app "feeling", Flutter is great

A high quality "portable runtime for apps" is inevitable. Flutter is inevitable. 🚀🚀🚀

The best part about crafting personal software—like this little budget app—is adding extra touches of delight and humor. Watch til the end 🙈