On Wednesday, March 2, 2016 at 7:46:23 PM UTC+1, Myk Melez wrote: > > Benjamin Francis <mailto:[email protected]> > > 2016 February 23 at 07:24 > > Sorry for being late to this thread but I just wanted to speak in > > support of "Progressive Web Apps" and to highlight the difference > > between web apps and apps which are built using web technologies. > No worries, I'm glad to hear it! > > > As I've said before I'm in full support of Web Manifest, Service > > Workers and Push for Firefox with a standalone display mode for > > Firefox similar to the web runtime, but using Firefox' instance of > > Gecko. I'm looking for ways to help move this forward. > There's a tracking bug for the Web App Developer Initiative that > references a variety of issues in Firefox: > > https://bugzilla.mozilla.org/show_bug.cgi?id=wadi > > In general, Service Workers are the farthest along, implemented on both > desktop and Android (with active development of enhancements like > DevTools support); Push is on desktop, but not yet on Android (although > it's being actively developed); and Web Manifest is implemented in > Gecko, but it isn't yet being used to implement a standalone display > mode, neither on desktop nor on Android. > > Nor has there been any movement to do this on desktop. (FWIW, Chrome > doesn't support this either, except as the experimental feature > chrome://flags/#enable-add-to-shelf for development/testing purposes). > > On Android, however, there are a handful of bugs to track aspects of > both a standalone mode and "add to homescreen" generally: > > *Bug 1126479* <https://bugzilla.mozilla.org/show_bug.cgi?id=1126479> > -"Add to Homescreen" from home screen does not open in fullscreen > *Bug 1208195* <https://bugzilla.mozilla.org/show_bug.cgi?id=1208195> > -Show sites opened from Android home screen bookmarks as separate > entries in the Android recent apps list > *Bug 1232706* <https://bugzilla.mozilla.org/show_bug.cgi?id=1232706> > -Promote "Add to home screen" if user visits website often > *Bug 1234558* <https://bugzilla.mozilla.org/show_bug.cgi?id=1234558> > -Use icon from app manifest for "Add to home screen" > *Bug 1237045* <https://bugzilla.mozilla.org/show_bug.cgi?id=1237045> > -Allow user to edit home screen shortcut name > *Bug 1240560* <https://bugzilla.mozilla.org/show_bug.cgi?id=1240560> > -When adding website to homes screen, no notification of success/failure > is presented > > That's where I think we could have the most impact on Firefox support > for Progressive Web Apps!
Hi Myk, All, following the removal of DOM:Apps from desktop firefox I had some success converting by firefox os app, which I also installed as Desktop packaged app, to a progressive web app using a service worker. It works fine when run from my self-hosts https site both in linux desktop nightly firefox and nightly firefox os browser. I can go offline and online while in the browser in both environments and the app keeps functioning using cached file (following an immediate claim service worker pattern). The use case I need to get working is when I need to restart the browser or the device while offline. How do I get to my progressive web app while still offline? It could function perfectly well, as in the case when I go offline with the app running, but there is just no way to get to it until I go online again. Any thoughts on this use case? Thanks, Adrian > > -myk _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
