Comment by gunian
1 day ago
What are your thoughts on Flutter vs Expo vs React Native for someone that wants to build a native app for fun?
1 day ago
What are your thoughts on Flutter vs Expo vs React Native for someone that wants to build a native app for fun?
React Native renders actual native widgets to the screen, so for example on iOS you would write to cross-platform abstractions but you’d still get real UIKit components on the screen.
Flutter draws its own components that can look superficially like the target platform (or not, it’s up to the developer) in a manner closer to a game engine. HN seems to love Flutter and apparently the developer experience is excellent, but as a user I find Flutter apps to be in general a poor experience. They rarely look or act quite right (assuming the developers even try; I’ve used a number that look like someone has transplanted an Android app onto iOS).
This is fascinating how does Flutter try to make up for the performace hit that comes with adding a layer of abstraction?
My thought is that Expo prioritises web compatibility too much to the point that it leans into conventions with things like navigation that are web-oriented and these contribute towards an app not feeling like a native app.
None of those will get you a "native" app, but they might get you most of the way to a cross-platform app.
fair point but coin toss it is what I'm getting they are all equally good/bad?
Flutter has THE best dev experience out of all platforms, including native. Hands down, Dart tooling + Flutter tooling are just on another level.
1 reply →
> Expo vs React Native
Expo is React Native with some nice things sprinkled on top. I'd go with Expo.
why Expo over Flutter? do React Native and Expo provide better abstractions over the Java/ObjC native APIs? again I've never done native dev just curious sorry if this isnt HN worthy comment
The tooling for Flutter is better, but Expo brings React Native much closer.
I fend that React Native app "feel" more native because they're actually using native components, but controlled via a JS runtime. Flutter on the other hand mostly renders to a canvas and re-implements native controls (although it can also wrap native components like RN does).
This leads to there being less of an "uncanny valley" in React Native apps compared to flutter. It also means that all the little details from the system (the text selecting and editing interactions in text inputs being a major one) are idential to native apps when using React Native, because it IS the native component.
The downside to this is that you need to consider platform differences more with React Native, which is one of the things which leads to developers without mobile experience having issues with it.
As the article says, you get the most out of React Native if you're a mobile developer, or at least have someone on the team who is. You can't abstract away all the details of a mobile platform without some tradeoffs.
Not apples comparison imho. Flutter requires using a new fringe language and while it might be a very nice language it's a heavy lift in most businesses contexts to march off into a new language just to use a mobile framework.
So, the main reason for Expo (there are others) is: get to write in the language most developers already know.