3 ms·
Flutter vs. Native vs. React-Native: Examining Performance
- mikece 6y agoWhy go with any of these over PWA mobile web or hybrid mobile app using a stack like Ionic/Capacitor? I'm reminded of a Q & A from the mid 1990s: what is faster, a desktop app written in C++ or one written in Visual Basic? The answer is "The on written in VB -- by six to nine months." The non-joke part of this answer was that in the gap between when a VB app shipped and the C++ equivalent would have shipped you could have identified the performance bottlenecks and replaced only those parts with a C++ COM upgrade and ended up with an overall app that was as fast as it needed to be. It's the same with a hybrid mobile app: you can deliver the initial app far, far faster than with any "native" stack and in the gap between delivering that and how long the native app would have taken you could re-code the performance bottlenecks -- if you even have any! -- in Swift/Obj-C or Kotlin/Java (or even C++ if you want) and load that into your Ionic/Capacitor app. My belief remains that CSS+HTML+JavaScript is always the right answer unless and until the client can articulate in detail why they need something else. Those cases where non-hybrid is needed do exist, but they are exceedingly rare.
- mikece 6y ago"Objective C is the best option for iOS app development. Swift is 1.9 times slower compared to Objective-C." I would like to see this documented in more detail. If this were true then Apple has wasted billions of dollars and countless developer hours making and pushing Swift, especially since they insist Swift results in faster compiled code both for iOS and macOS.