<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>pluma</author><text>Push notifications? Every single messenger or anything that lets you set reminders. Note that features like push notifications are implemented with a discrete opt-in on every other platform already. Don&amp;#x27;t want notifications? Just say &amp;quot;Deny&amp;quot; when you&amp;#x27;re prompted.&lt;p&gt;Offline support? Only if you happen to live in the 99.99% of the world that doesn&amp;#x27;t have 24&amp;#x2F;7 perfect WiFi&amp;#x2F;4G coverage with unlimited data. If you&amp;#x27;ve ever kept a page open in the background and wished the data would still be there when you come back, offline support could have helped with that.&lt;p&gt;The choice is not between a native and a web app. The choice is between a web app or no app. There are certainly apps that could cease developing platform specific native apps when PWAs are supported on iOS but the vast majority of apps that benefit from PWAs being supported universally are apps that simply would never be available as native apps (let alone native apps on more than one platform).</text><parent_chain><item><author>IBM</author><text>Is there a reason for users to care about this at all? Because it seems to me that this just solves problems for developers while making the user experience worse or not as good as it could be. The same goes for Electron-based apps.</text></item><item><author>pluma</author><text>I think push notifications and offline support are the real killer features that Apple currently doesn&amp;#x27;t support.&lt;p&gt;It&amp;#x27;s kind of funny as a web developer because for the longest time Apple seemed to be the one pushing the mobile web forward but now that web apps are reaching for feature parity with native, Apple&amp;#x27;s initial momentum seems to be ancient history.&lt;p&gt;It seems Apple still thinks of the mobile web as a content delivery platform rather than an application platform. Their proprietary additions (mostly CSS) largely focused on making things prettier, their rationale for opting out of standard features (e.g. autoplay) often only work under the assumption that the only use for those features would be in the context of traditional content pages.&lt;p&gt;You want an app? Develop for our walled garden we tightly control to offer our users the best possible experience. If you want it on the web, stick to creating content our users can consume in Mobile Safari, our app for reading websites.</text></item></parent_chain></comment><story><title>Apple’s refusal to support Progressive Web Apps is a detriment to the web</title><url>https://medium.com/philly-dev-shop/apples-refusal-to-support-progressive-web-apps-is-a-serious-detriment-to-future-of-the-web-e81b2be29676</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jvzr</author><text>Exactly. I don&amp;#x27;t want websites to send notifications. And I dislike websites with Offline support: I always have to refresh twice to make sure the content I&amp;#x27;m seeing came from a fresh source and not from cache.</text><parent_chain><item><author>IBM</author><text>Is there a reason for users to care about this at all? Because it seems to me that this just solves problems for developers while making the user experience worse or not as good as it could be. The same goes for Electron-based apps.</text></item><item><author>pluma</author><text>I think push notifications and offline support are the real killer features that Apple currently doesn&amp;#x27;t support.&lt;p&gt;It&amp;#x27;s kind of funny as a web developer because for the longest time Apple seemed to be the one pushing the mobile web forward but now that web apps are reaching for feature parity with native, Apple&amp;#x27;s initial momentum seems to be ancient history.&lt;p&gt;It seems Apple still thinks of the mobile web as a content delivery platform rather than an application platform. Their proprietary additions (mostly CSS) largely focused on making things prettier, their rationale for opting out of standard features (e.g. autoplay) often only work under the assumption that the only use for those features would be in the context of traditional content pages.&lt;p&gt;You want an app? Develop for our walled garden we tightly control to offer our users the best possible experience. If you want it on the web, stick to creating content our users can consume in Mobile Safari, our app for reading websites.</text></item></parent_chain></comment><story><title>Apple’s refusal to support Progressive Web Apps is a detriment to the web</title><url>https://medium.com/philly-dev-shop/apples-refusal-to-support-progressive-web-apps-is-a-serious-detriment-to-future-of-the-web-e81b2be29676</url></story>