Neither you nor the parent poster substantiate your assertions with sources, which made me curious of what research might have been done in this area. Some cursory searching lead me to this reasonably well sourced answer, which suggests the parent poster is right in this case:
https://ux.stackexchange.com/a/39295
Sorry, but your linked source is off-topic, ancient (2013!), and compares the wrong things (native mobile apps vs. old-generation-hybrid-web-mobile apps).
The relevant comparison here would be between:
- (1) truly native uni-platform mobile apps (native Android and native iOS apps)
- (2) cross-platform mobile apps using native widgets (not sure if there's any alternative to React Native here)
- (3) cross-platform mobile apps that draw their own ui, but NOT using web technologies: Flutter is the only obvious example (there are older things like Kivy which uses Python and OpenGL but I think it was mostly used for games and kids app, not that popular)
Web-techs-based hybrid-mobile apps are a different thing (Cordova, Ionic etc.) and, yes, there everyone agreed they feel inferior to users, just as mobile optimized websites feel inferior.
Unfortunately this is the problem here, it's incredibly easy to compare apples to oranges here, I don't blame, just saying that all sources are misleading, probably it's better to play with few things and see the "gut feeling"... it's pretty obvious that underlying tech and whether the widgets are drawn natively or not is NEVER a differentiator between successful and unsuccessful apps, it's always all the other things :)
