pwa

Is it possible to host multiple PWAs under same endpoint. Say, I have three different PWAs Under root and then root should host these 3 PWAs in such a way that when I switch to any other apps via link or menu it shouldn't open in different window. Currently, it is getting opened in different window as web app whenever, I am clicking on different app. Thanks, Rahul You may refer with this thread . It stated that you can accomplish this with scoped apps. Update your manifest files to include a scope parameter with a value of the path that "app" should be served under. "scope": "/r/aizumap/", and

Similar to this question , is IndexedDB guaranteed to be persistent ? ie. Safari will not reclaim disk space if the device is low on memory. Safari have " No Eviction policy ", meaning it will not automatically clean the IndexDB on low disk pressure, without user doing it manually. IndexDB is one of the fast evolving feature and you can expect to have a different eviction policy any time with no announcement. You should always build with fall back options. Chrome has explicit persistent storage option which will guarantee no eviction, on user approval for persistent storage and we can expect

I'm working on a PWA (progressive web app) and I would like to be able to track whether someone is just viewing it as a website or if they installed it and are viewing it as an app. Is there any way to do this? I can't think of any ways, since they both use the same files (both use manifest.json and manifest.json directs both to the same index.html). Windows 10 gives the ability for PWAs to be installed from their app store. At that point, you might be able to gather some analytics. Unfortunately, that would be a limited install-base (compared to just installing it from the browser). Option 1

I'm trying to figure out if it is possible to open a file from a Progressive Web App with the default system application. The idea is that a PWA would store for offline use some files (e.g. a .docx file), and that the user would be able to open them without (re)downloading them. The ideal situation would be that the PWA is able to load into memory the file, make it accessible to the default system application for that file type (e.g. Word for .docx files), watch for changes (i.e. the user saves edits), and then store it back into the PWA storage. Even a read-only solution would be great. Since

The background for this question is that I've been working on what I'd call a tool in which a user can build modules that they can later run. It started out as a small web page and has grown over the last year into something that more closely resembles a desktop application; but, at this point, is still just a set of html, css, and js files. I considered using something like electron to package it as an installable desktop application, but I didn't like that approach and thought it better to stick to something like a progressive web app because everything is done off-line. Because I wanted to