[gitgud]

Because Flutter has it's own rendering engine, it's inherently more consistent in refresh rates and UI components.

Although React Native shows Native elements, they vary slightly across different; devices, platforms, OS's etc.. this can create many weird edge cases, which makes it unreliable in some cases.

[bsaul]

I'm actually investigating getting some skills on react native, but i've got the suspicion it isn't all sunshine and rainbows. From what i've seen so far, a real-world stack has many more dependencies other that react native itself, and becomes a convoluted mess.

However, i'm surprised that i haven't found a similar post to OP detailing real-world React Native pain points.

Do you have more info ?

[rhodysurf]

RN pain points are upgrading more than anything else. Also as a native dev I don’t understand why the JS dev ecosystem is full of disjointed tooling instead of just making the process more streamlined.

I have also developed a production flutter app for a client and am now working on a RN app for another. I like RN so much more just because I can create custom native views that use the platform toolkits. You can also share a lot of code with an SPA web app and set up a monorepo for everything pretty easily.

Flutter dev tools are incredible though and much easier to use than react native.

[bsaul]

how is the view animation / vc transition story on RN ?

Say you’d like to implement a snapchat-like UX with RN, would that be possible without relying heavily on native custom components ?

[rhodysurf]

Animation with RN is very good.

Snapchat like UI is definitely possible, but for the performance to be really good youd probably want to do something native. I consider that a good thing though. RN is better if you just treat it as the coordinator on top of native view components IMO.

[ex3ndr]

Yes