Hacker News new | ask | show | jobs
by orange8 1164 days ago
> ask three people, and they will give you five answers on what exactly PWA support means

Or maybe just refer to the definitive docs [1] instead of relying on what 3 random people say?

[1] https://developer.mozilla.org/en-US/docs/Web/Progressive_web...

1 comments

"That PWAs can use", but it's not a requirement.
So what exactly are you asking for here? A list of PWA api's that must be used all the time in every single PWA app? What's the benefit of that? Which application development API has such an asinine requirement in the first place?
> So what exactly are you asking for here?

I'm not asking. I'm telling, and quite clearly: ask three people, and you will have five answers as to what APIs people think PWAs can't live without.

Because of this you will always have people scream "Apple is killing PWAs" because they don't support a yet another random API.

And yet, see bullet point two in my original comment.

> Because of this you will always have people scream "Apple is killing PWAs" because they don't support a yet another random API.

I like the "yet another random API" phrase. It creates the impression that PWA APIs are being generated fast and furious, and apple is trying very hard to keep up with all these "random" new APIs. Yet, the reality is that apple has for a long time deliberately crippled PWAs on their platform by not supporting just 4, crucial, old and fundamental APIs. I will list these for you:

- Background Sync

- Web Push

- Before Install Prompt and Installation Banner

- Background audio for PWAs

They do not have to implement any "yet another random API". Just those four. Everything else is a bonus, considering this is Apple's Safari (the new IE) we are talking about.

> I like the "yet another random API" phrase. It creates the impression that PWA APIs are being generated fast and furious

They are

> not supporting just 4, crucial, old and fundamental APIs.

At least these two are definitely random APIs that you think are "crucial", and not everyone who complains about Safari lists them.

> They do not have to implement any "yet another random API". Just those four.

Just those four that you decided are crucial.

Imagine going 2000 years back with a book and showing it to some caveman. To you they are words, with meaning and purpose. To him, they're just random gibberish scrawled on some leafy stuff. He might even nibble on one of the pages and declare "it doesn't even taste good, what can be its use?"

Random APIs indeed. Lol

You might have five answers, but all of them will agree that ios is lacking important ones.
They won't, of course.