For instance, I just installed an app on my Android that creates a blacklist of phone numbers to reject, both calls and SMS and also cleans up the phone's logs. Basically once you add a phone number to that app, it may as well not exist anymore. I love this little app so much that I would rather do without all available web apps out there on my phone ... because the main purpose of my phone is to connect with people and not having API integration with its core functionalities, like voice calls and SMS would make whatever "smartness" it has basically useless.
I'm still baffled as to why this isn't a standard feature in phones, but whatever, at least on Android you can add it (versus the iPhone, which requires rooting).
And exposing these low-level features in the browser through proprietary extensions wouldn't help the fragmented market. It also doesn't help that each environment has its own look&feel, so you'll have to add lots of platform specific stylesheets and Javascript for emulating standard behavior.
The best combination for me (as in fast development, not the best user experience) is building native apps with a web interface exposed through an embedded web view.
In some cases, you might get away with a worse user experience -- if you want Netflix's content, you have to use Netflix's application, and a competitor can't edge out Netflix without providing replacement content, as well.
However, this is unlikely to be to your benefit if another competitor does offer content of equivalent value to users, and they choose to spend their attention on an application with a superior user experience.
edit: this is my opinion as a web developer who is thinking of getting into the mobile market, not as a mobile developer.