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 ?
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.
Say you’d like to implement a snapchat-like UX with RN, would that be possible without relying heavily on native custom components ?
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.
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.