News for hackers. Stuff that matters.
Re:What the Heck Is a “Progressive Web App”? Seriously by bhalp1 on Monday November 06, 2017 @11:51AM (#15636744)
Google says "If you're building a Progressive Web App, consider using a service worker so that your app can work offline."

What does "consider" mean here?

And I'm pretty sure SPA is also not a criteria for PWAs, it's just a suggestion.

And also, the install banner is not really yours, it's the browser's functionality.

Per Google:

> Chrome uses a set of criteria and visit frequency heuristics to determine when to show the banner.

Re:What the Heck Is a “Progressive Web App”? Seriously by bengotow on Monday November 06, 2017 @12:03PM (#15636832)
My favorite part of the whole PWA marketing push is that they encourage use of the Service Worker API for offline caching, but leave cache invalidation / cleanup as an exercise to the reader. "Do it the way it makes sense for your application" is a technically correct answer, but I assume translates to "never" for 99% of us with tight deadlines.
Re:What the Heck Is a “Progressive Web App”? Seriously by parthdesai on Monday November 06, 2017 @12:08PM (#15636886)
This[0] might help you.

[0]: https://workboxjs.org

Re:What the Heck Is a “Progressive Web App”? Seriously by jnbiche on Monday November 06, 2017 @01:11PM (#15637424)
> And I'm pretty sure SPA is also not a criteria for PWAs, it's just a suggestion.

Fair enough, you could certainly use Service Worker API for an app with multiple pages. What I was trying to capture with the term SPA is more "web app", although I suppose you could even use Service Worker API with a simple static site.

Re:What the Heck Is a “Progressive Web App”? Seriously by holmberd on Monday November 06, 2017 @12:20PM (#15636985)
Having a registered Service Worker is a condition of the app being classified as a Progressive Web App by Chrome.