Live data from Hacker News

Apple’s refusal to support Progressive Web Apps is a detriment to the web

medium.com

151–160 of 451 posts

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#151

I hate using web apps. On desktop, mobile, wherever. The author's list of things they want supported by Mobile Safari is just aggravating: > Here are a list of things you still can’t do with mobile safari due to Apple’s refusal to support them: > > Create an app loading screen > Use push notifications > Add offline support > Create an initial app UI to load instantly > Prompt installation to the home screen through b…

I use the Facebook site added to my homescreen rather than a native app. Uses way less space & does everything I want Facebook to be able to do.

I don't want push notifications from every site, but in this case it's valuable.

I wish it worked offline-first, but I know it's something they're looking at.

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#152

Earlier quoted context omitted.

Push notifications and home-screen icons are strictly opt-in. If you don't want them, don't opt, simple as. I use webapps for several things because I can much better protect myself from tracking and data-harvesting with a well-configured browser than I can using a native app.

As I said, desktop Safari allows websites to prompt me for push notifications. I can't stand it: that a web site has the ability to display a modal prompt sheet that I have to cancel.

Disable it.

It's a feature some people like and use. I like getting notifications from some services I use without needing to keep a browser window open on that page to get notified. And I like not having to download and install yet another flipping app to get that feature.

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#153

I hate using web apps. On desktop, mobile, wherever. The author's list of things they want supported by Mobile Safari is just aggravating: > Here are a list of things you still can’t do with mobile safari due to Apple’s refusal to support them: > > Create an app loading screen > Use push notifications > Add offline support > Create an initial app UI to load instantly > Prompt installation to the home screen through b…

I completely disagree, to be frank. Why do I need a native binary, tens of thousands of lines of code, an app with a massive permissions access to my device... To read a news article? To book a flight? To comment on an internet post? Adding a few more "app features" to light web pages sounds a whole lot more attractive than banishing all useful functionality into the den of apps, where only larger teams and more expe…

There is that, and then there are performance intensive apps, and everything in between.

Apple is ensuring that most of its ecosystem is fast and pleasant.

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#154

Earlier quoted context omitted.

This is not surprising of Apple. They've always been a walled garden, that's why I don't buy their products. I like to own products that give me full control as a user. When the iPod came out, I never understood why I couldn't just drag the music files directly onto the device and I had to get iTunes and use iTune's tedious interface. Now they have the app store; another unnecessary restriction. As a developer, it's…

>When the iPod came out, I never understood why I couldn't just drag the music files directly onto the device and I had to get iTunes and use iTune's tedious interface. Because MTP is utter rubbish. Really, people complain about iTunes? It's never failed me as slow as it is. Try using MTP...

The iPod mounted as a perfectly-functional Firewire disk, yet you still had to use iTunes to put music on it for it to be playable on the device. (It was filed away in obfuscated filenames...)

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#155

Earlier quoted context omitted.

This is not surprising of Apple. They've always been a walled garden, that's why I don't buy their products. I like to own products that give me full control as a user. When the iPod came out, I never understood why I couldn't just drag the music files directly onto the device and I had to get iTunes and use iTune's tedious interface. Now they have the app store; another unnecessary restriction. As a developer, it's…

>When the iPod came out, I never understood why I couldn't just drag the music files directly onto the device and I had to get iTunes and use iTune's tedious interface. Because MTP is utter rubbish. Really, people complain about iTunes? It's never failed me as slow as it is. Try using MTP...

NO one said anything about MTP. Copying files > anything.

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#156
post #155

Earlier quoted context omitted.

>When the iPod came out, I never understood why I couldn't just drag the music files directly onto the device and I had to get iTunes and use iTune's tedious interface. Because MTP is utter rubbish. Really, people complain about iTunes? It's never failed me as slow as it is. Try using MTP...

NO one said anything about MTP. Copying files > anything.

Copying files... how? Emulating a FAT32 disk? That sucks. exFAT? Patents. MTP? Sucks. So how?

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#157

I hate using web apps. On desktop, mobile, wherever. The author's list of things they want supported by Mobile Safari is just aggravating: > Here are a list of things you still can’t do with mobile safari due to Apple’s refusal to support them: > > Create an app loading screen > Use push notifications > Add offline support > Create an initial app UI to load instantly > Prompt installation to the home screen through b…

"The web" is a broad concept, but we should break it down to two distinct things: websites and web apps.

You don't need all these extra features for a website. However, they are useful and needed for many web apps. Just because websites sometimes abuse these features doesn't make them bad.

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#158
post #118

Earlier quoted context omitted.

But as an iOS user I expect you to use the technology stack provided by my preferred operating system. I don't want to use your app if you're targeting a lowest-common-denominator feature set. When I change my preferred text size through accessibility settings, good native apps respond correctly. If I need voice over support, the operating system knows how to read the view hierarchy to me in a logical way. When drag-…

>I don't want to use your app if you're targeting a lowest-common-denominator feature set. You might even use a hybrid app without it knowing. Many apps just need to show some buttons, input fields, images or a map and hit a web service. Brushing ALL hybrid apps off as useless is in my eyes just ignorant.

[deleted]

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#159

Safari engineers have attended all service worker working group meetings, and they do contribute. However, I do share the frustrations over transparency. It's tough to get developers to care about things like offline-first, because it's tough for them to convince managers to allow them to spend time on a feature that won't work on iOS (since it won't work in Safari, and Apple has banned other browser engines on their…

Can you share more information about how the ban to other browsers works? Safari can do whatever they want but Apple banning competition is what hurts the web.

Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web

#160

I hate using web apps. On desktop, mobile, wherever. The author's list of things they want supported by Mobile Safari is just aggravating: > Here are a list of things you still can’t do with mobile safari due to Apple’s refusal to support them: > > Create an app loading screen > Use push notifications > Add offline support > Create an initial app UI to load instantly > Prompt installation to the home screen through b…

I completely disagree, to be frank. Why do I need a native binary, tens of thousands of lines of code, an app with a massive permissions access to my device... To read a news article? To book a flight? To comment on an internet post? Adding a few more "app features" to light web pages sounds a whole lot more attractive than banishing all useful functionality into the den of apps, where only larger teams and more expe…

Why do I need a native binary, tens of thousands of lines of code, an app with a massive permissions access to my device...

You don't – but why do you need loading screens, push notifications, or any of that other stuff either?

The web is great in concept for document-oriented information and some application uses. Mobile applications are greater for richer user interfaces and more device integration. They both have their strengths, and I think it's okay to accept that.

Post reply on HN