The OP wasn't talking about users, but rather best practices on how to get the App Store makers to feature you. I've heard the App Store editorial team specifically give the "go native" advice.
It's definitely not required, it just helps. Our app got featured in one of the App Store's daily stories despite it being written in React Native.
I kind of doubt that whoever does the feature pics looks at the binaries to figure out if it is native or not. As long as the end result is not easily distinguishable from native, I'm sure you are just as likely to be featured.
Yea if you play around you can really make an app look like native. Even in desktop it's difficult to figure out web apps wrapped under electron when they are done right..
I'm an Android developer and a few times in 2017 I confused a Corodva app with a native app. With Chrome 63 and customized over-scroll behavior Twitter PWA is really impressive, no reason to install native Twitter app. 2018 might be breakthrough year for hybrid and PWA apps.
I'd say there's no point just framing your site in a native container, but it's still viable to use webviews where it makes sense. Particularly if you're just delivering loads of static content.
And you're the reason I don't use very many phone apps.
Developer apathy becomes user apathy. If you make great apps, your customers will be enthusiastic about using them. If you make mediocre apps, you will attract mediocre users, or no users at all.
For a very long time, and it may still be true, both Uber and Instagram were hybrids. While you may not use them a lot of other people certainly aren't apathetic about those app. Facebook was a hybrid app for years although it's a native app now.
Mediocre apps are annoying, I agree, but that rarely has anything to do with the underlying technology.
It's definitely not required, it just helps. Our app got featured in one of the App Store's daily stories despite it being written in React Native.