- From: Andrew Betts <notifications@github.com>
- Date: Thu, 02 Jun 2016 19:26:37 -0700
- To: w3ctag/spec-reviews <spec-reviews@noreply.github.com>
- Cc:
- Message-ID: <w3ctag/spec-reviews/issues/123/223475610@github.com>
This is a topic of great interest in the developer community. Lots of commentary on this members may like to review. W3C member orgs are indicated. * [Beyond Progressive Web Apps](http://cssence.com/blog/2016-05-beyond-progressive-web-apps) Matthias Beitl * [The importance of URLs](https://www.kryogenix.org/days/2016/05/24/the-importance-of-urls/) Stuart Langridge * [On URLs in Progressive Web Apps](http://www.brucelawson.co.uk/2016/on-urls-in-progressive-web-apps/) Bruce Lawson (Opera) * [Regressive web apps](https://adactio.com/journal/10708) Jeremy Keith * [The ideal web experience](https://medium.com/ben-and-dion/the-ideal-web-experience-d3df0178a25d) Dion Almer * [State of the Gap](https://remysharp.com/2016/05/28/state-of-the-gap) Remy Sharp * [Regression towards being mean](https://adactio.com/journal/10736) Jeremy Keith * [Progressive web apps and our regressive approach](https://www.christianheilmann.com/2016/05/31/progressive-web-apps-and-our-regressive-approach/) Chris Heilmann (Microsoft) * [Not the post I wanted to be writing](https://infrequently.org/2016/05/not-the-post-i-wanted-to-be-writing/) Alex Russell (Google) * [Yet another blog about the state and future of progressive web apps](https://ada.is/blog/2016/06/01/yet-another-progressive-webapp-post/) Ada Edwards I would suggest we consider these issues: 1. **Definition of "progressiveness"**: What does it mean, should people do it, etc. 2. **Canonical content addressing**: Is it a problem if the same content is available in different forms from different URLs (eg intended to be used with different devices or viewing contexts, m-dot etc). Do PWAs encourage non-canonical copies of content and is that an architectural problem for the web? 3. **Containment**: Features that make websites less integrated into the fabric of the web and more like self-contained applications (often called "seamless"), are these bad for the web? Eg. hiding URLs and browser chrome, lack of deep linking ability, lack of discoverability in search etc. It's also worth noting ad applauding the fact that the campaign to promote progressive web apps has had a positive impact on the reputation of the web as an alternative to native apps on mobile platforms. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/spec-reviews/issues/123#issuecomment-223475610
Received on Friday, 3 June 2016 02:27:19 UTC