Flutter and React-Native are different directions, I think.
For higly customized UIs (think Ableton Live, Photoshop, Excel, etc.), I'd say use Flutter, because of the non-native rendering, it will look the same everywhere. Otherwise use React-Native.
Flutter renders onto a "canvas" and has a completely custom implementation of "native-like" views for each platform. They need to reimplement everything about platform views from scratch.
React Native lets the native OS render actual native views, but lays them out and controls their properties using Javascript. You get the native behaviours "for free", but you do sometimes end up in the lowest common denominator position.
Sure. But what if the entire world doesn’t want to learn JavaScript? What if you don’t already know HTML, CSS, and JS? RN makes ZERO sense at that point.
As a C developer, man, Flutter looks pretty damn logical!
I don't know if you read your own link or not, but he's first off complaining about a community plugin and not an official one.
There is some truth that overlapping isn't well supported in Flutter CURRENTLY, but I can think of things that were well supported in RN 4 years ago either.
I can't think of a single reason I would want an overlay EXCEPT an alert, and even then, I don't think he's right.
The last time I was using React Native even text input was broken on Android. It made any app using it basically unusable. Android profiler didn't work either, opening it crashed the runtime.
Flutter has its bugs but they're certainly not that fundamental issues.
Flutter renders onto a "canvas" and has a completely custom implementation of "native-like" views for each platform. They need to reimplement everything about platform views from scratch.
React Native lets the native OS render actual native views, but lays them out and controls their properties using Javascript. You get the native behaviours "for free", but you do sometimes end up in the lowest common denominator position.