When Flutter was first announced I was into Xamarin development but I quickly soured on the concept of a write-once, run cross-platform mobile app utopia. On e

When Flutter was first announced I was into Xamarin development but I quickly soured on the concept of a write-once, run cross-platform mobile app utopia. On every project I was involved with we ran into the same scenario: 80 to 90% of the app was easy to produce but that last 10% accounted for 95% of the effort and surfaced paradoxes and bugs so nasty we ended up swearing we could have done everything better and faster to have written two separate apps from scratch in Kotlin/Swift as the vendors recommend in their developer documentation. The other practical take-away is that, with only one exception, not a single mobile app I worked on needed to be a mobile app per se: they all would have worked just fine as a mobile website (or as a hybrid app if local storage or push notifications were truly deemed mission critical and essential -- but that's less a product needs argument and more a manager's ego argument). And now with elements of PWA being supported even by iOS the need even for a hybrid app is dwindling to near zero. Which makes it all the more curious to me why React Native still has the following it does. Can it all be explained by inertia?