Personally I'm obsessed with efficiency and performance - and platform specific native toolkits are rarely beaten at that. I really don't like seeing wasting many megabytes of (V)RAM and long seconds of CPU time just to display a marquee...

If the app is useful, nobody cares.

If it isn’t useful, it doesn’t matter.

Sure some developers have strong opinions about this…and if you are selling to developers those opinions matter (most commonly, a job interview ).

But apps are gonna be shit for other reasons and the attraction of native-or-not is that fixing those reasons are much harder. Even when you choose to use theory to make GUI choice to add to complexity of development).

Or to put it another way, the simplest thing that might work means you stay working instead of thinking (thinking != working). Good luck.

They look and feel similar to the user, I still think native is better but React Native looks and feels pro so I'm cool with it.

I think usability almost always suffers when the native UI isn’t used. It’s not that platform-neutral UIs aren’t usable, or good looking. However when native UIs were prevalent, there were standards built up over years of hard-earned experience: for a Windows app, you wanted to get your tab order right, and you knew the convention of getting the Cancel button mapped to the escape key etc etc. See also the Mac and the HIG, encouraging apps to look and work roughly the same.

There were always outliers and ugly UIs, but it always felt like there was a uniformity that made it easier to get around in an unfamiliar app. Whereas now, electron apps look and work very differently (comparing slack to Spotify to VSCode and so on).

That said, I think very few people care as much as I do about it, and cross-platform UIs save a ton of development work.