3 ms·
From what I’ve seen in the corporate world, it’s the overwhelming default. The business simply will not pay for separate native iOS & Android apps, even if you
by turnsout 3y ago
From what I’ve seen in the corporate world, it’s the overwhelming default. The business simply will not pay for separate native iOS & Android apps, even if you present convincing evidence that it’s better, faster and cheaper.
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.
- noname120 3y agoWhy not Flutter or any other cross-platform framework?
- tomduncalf 3y agoIn my experience, apps rewritten in Flutter are janky, to the point where I can spot them a mile off - especially in animations/transitions and fake native widgets (based on a sample of 2 apps which I use often and have been rewritten in Flutter recently: Philips Hue and EE mobile network). 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.
- sdflhasjd 3y agoFlutter is React Native jank times two because it tries to render the entire UI itself. 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.
- davidmigloz 3y agoFlutter jank is almost non-existent with Impeller, the new rendering engine that Flutter uses in iOS (and in preview in Android). Compose multiplatform uses Skia, so it suffers from the same shader compilation issues in iOS that Flutter has been suffering from all these years.
- noname120 3y agoI keep hearing that Flutter is bad because it “tries to render the entire UI itself”. This argument sounds good — at least on paper — because all the previous attempts at doing that failed miserably. 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.
- sdflhasjd 3y ago> better, faster and cheaper 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.