zlacker

[return to "Apple’s refusal to support Progressive Web Apps is a detriment to the web"]
1. interp+W9[view] [source] 2017-07-27 12:48:02
>>jaffat+(OP)
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 browser-guided dialog

Why do I want these things, as a user. App loading screens?

I love the web. I love hyperlinks, text and images. The web of connections that lead you to information. Everything in that list is detrimental to a good experience on the web.

I don't want push notifications, I barely enable them for native apps. And it bugs the hell out of me when every second website in desktop Safari prompts to send me push notifications. No. Why would I want this on mobile?

Same thing with the home screen. I love the fact that the address bar in my web browser is my history, my reminders, my bookmarks, my open tabs. I start typing what I want and I'm there. Finding native apps on my home screen is only just getting to the same place with Spotlight, why would I want to make the web worse by sticking icons for pages on my home screen?

And browser-guided dialogs to put more icons on my home screen? Seriously?

This author's post is a great argument against web apps on mobile.

◧◩
2. criley+Lh[view] [source] 2017-07-27 13:54:10
>>interp+W9
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 experienced developers can roll out even basic functionality.

◧◩◪
3. interp+3l[view] [source] 2017-07-27 14:14:20
>>criley+Lh
I think we agree in some sense.

> To read a news article?

I refuse to use a native app for this (e.g., Apple News, Flipboard). I love reading my news on the web. In a browser. Where the page is the content and the browser is the convenience. Even better is having Safari's "Reader Mode" enabled constantly so every article is consistently and nicely formatted and I get just the text and links.

> To book a flight?

Same thing for booking a flight, last time I did that was on a web site. With some forms and a few "Next" links to go to the next page until I was done.

It was nice to get the boarding pass in Apple Wallet though and then use that to board.

> To comment on an internet post?

I'm commenting on this post right here in Safari. I wouldn't ever want to use an app for it.

I don't need more "app features" on light web pages. Especially not the ones mentioned in the article.

◧◩◪◨
4. Ajedi3+pm[view] [source] 2017-07-27 14:23:09
>>interp+3l
Now imagine if you could do all of that faster and offline, while still avoiding the need to install a native app. That's something PWAs would enable.
[go to top]