Apple declined to implement 16 Web APIs in Safari due to privacy concerns

Re:Apple declined to implement 16 Web APIs in Safari due to ... by strbean on Monday June 29, 2020 @02:17PM (#23680486)

Are you talking specifically about add-to-home-screen / offline capabilities? Because PWA is a very broad term, and most descriptions I've seen consider those features necessary to be a PWA.

Ignoring those two, you get damn near every major web app. All of Google's applications, Facebook, Twitter, etc. etc.

[ Parent | on HN ]

Re:Apple declined to implement 16 Web APIs in Safari due to ... by Abishek_Muthian on Monday June 29, 2020 @02:43PM (#23680895)

This is a good question.

You can enable add-to-home-screen for websites with a single meta tag,

   <meta name="mobile-web-app-capable" content="yes">

e.g. Here's one of my website with that tag[1], Ironically this feature was introduced by Apple and is considered part of PWA specs.

But for the sake of this discussion, let's consider PWAs to be one which uses app manifest[2] and uses some high level device features.

[1]https://needgap.com

[2]https://web.dev/what-are-pwas/

[ Parent | on HN ]

Re:Apple declined to implement 16 Web APIs in Safari due to ... by strbean on Monday June 29, 2020 @05:22PM (#23683257)

Woops! I left off the word "don't" in regards to those features being necessary to be considered PWAs!

[ Parent | on HN ]