[MCArth]

This just isn't true! There are so many features that have not been supported long after other browsers implemented them (webgl 2 comes to mind, though that is finally available - 4% of global web users still don't have support due to this, though!)

[mtomweb]

Exactly: Install Prompts - 7 Years. Fullscreen API - 11 Years. Push API - 7 Years. Badging - 5 years. Screen Orientation Lock - 11 years. Bluetooth - 5 years.

[frumper]

Nope, nope, definitely nope, not critical in the slightest, nope, and sounds like a very niche case that a native app would do just fine with.

[agust]

"A native app would do just fine", why would we want to build a native app using proprietary tech, be forced to go through an app store, risk to be turn down by Apple and be taxed 30% of our revenue otherwise? All this when we can build web apps using open standards, working on all platforms and without being extorted by a giant abusive conglomerate?

[frumper]

You would want to because you want access to Apple's customers. Also, your example doesn't sound like it'd hold up to real world practice. If you're selling someone proprietary tech then your revenue isn't subject to 30% of Apple's fee. Only the software portion done through the app is. You obviously have a motivated buyer at this point if they bought a physical device. You could route them to a website to create an account, sign up for any subscriptions and launch the startup process that eventually has them install your native app. You want what you want, but you describe hyperbole. Plenty of apps have users manage subscriptions on a website, not on native apps.