It’s not the worst thing in the world, but React Native makes your entire app feel kind of janky and clunky. It’s frustrating when something as simple as a push transition looks and works 1000X better with a few lines of SwiftUI.
It’s not the worst thing in the world, but React Native makes your entire app feel kind of janky and clunky. It’s frustrating when something as simple as a push transition looks and works 1000X better with a few lines of SwiftUI.
Better is subjective, faster - in my opinion - is no longer as much of a factor with even cheap modern phones unless you're doing something like AR. Not sure how you can build two native apps for cheaper though.
Jank... I agree there a little. I would say most of it can easily be avoided though if you've got developers who have native experience and know what they're looking at.
Same can also be true of RN (or native!) of course, and I’m sure with enough work the apps in question could be made slicker and it probably wasn’t a priority; but they’re both developed by large companies and to me as an iOS user, feel pretty bad compared to their previous native implementation, so Flutter is definitely not a magic bullet.
MAUI has just gone through a rough migration from Xamarin and has some maturing to do, and developers are feeling neglected by Microsoft.
Cordova is Electron for phones - just do a PWA.
Kotlin multiplatform is good, but the Compose multiplatform has only Alpha support for iOS.
But — to my disbelief — I must admit that Flutter didn't just try, it actually nailed it. I can't tell the difference between a Flutter app and a native app in terms of look and feel.
Compose multiplatform uses Skia, so it suffers from the same shader compilation issues in iOS that Flutter has been suffering from all these years.