Re: [w3c/manifest] Add Optional Opt-In for UA Default Transition (#504)

Thanks @marcoscaceres.  @jakearchibald's [Navigation Transitions proposal](https://github.com/jakearchibald/navigation-transitions/blob/master/README.md) looks really cool, but I'm not sure it solves the problem that me and colleagues are trying to address.  

Situation: Developer wants to have a minimum viable product (MVP) PWA by adding a web app manifest to an existing website that scales with screen size.  

User Experience: When an end-user of this MVP PWA on a slow Internet connection clicks/taps a link to navigate, it can take some time for the next page to load.  Waiting multiple seconds with no visible indication of progress in the UX may cause the end-user to think the app has hung and exit the app.  :(

Solution for MVP PWA Developer: Enable the developer who just wants a MVP PWA to indicate with one line in the Manifest that they want the web browser to provide some default "transition" like chaser dots, an hourglass, etc. (if it is available.)

MVP PWA -> Better PWA: Once the developer of MVP PWA starts getting users of their PWA app, they will hopefully invest in improved "transitions" and/or improved offline / slow Internet experiences.  

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/504#issuecomment-264056908