The title is kind of misleading. I thought it was something specific to GitHub, when in fact it's a generic guide for any static site, no matter where it's hosted.
I don't think it was deliberately misleading. While it'll work for any site if you know what you're doing, the instructions are for making it work with Github specifically because of the paths involved. Without this, some people may have trouble getting it working on Github.
On your own site, you likely wouldn't use a subdirectory, making some parts of it simpler.
PWA still sounds to me like a 2015 buzzword from Google that never quite took off as everyone hoped it would. Perhaps the lack of support on Firefox could have something to do with it.
Firefox removed support for installing PWAs on the few platforms it used to support that on, which is one of the more important features for my usage. I don’t want to see browser chrome on apps that are intended to be peers with traditional apps, and having presence in OS process/windows management is useful.
I understand but you are in the minority. Most people don't use firefox and most firefox users didn't even know firefox supported installing apps that way on desktop.
If you yourself want to install PWAs on desktop then chrome, edge, and maybe even desktop safari all do it fine. You won't see the browser's chrome and you probably won't even know it's not running in firefox.
A browser with less than 4% market share probably has not that much to do with it. Firefox is barely used by "non-tech people" anymore. If PWA "never quite took off", it's not because of Firefox, because 2/3 of the people online use Google Chrome, which used to and still supports them.
Firefox supports PWAs fine, it's just the desktop installing part they don't have. Offline works, push works, installing works on Android, pretty much everything works.
> Perhaps the lack of support on Firefox could have something to do with it.
I'd put this more in the category of natural consequences of trying to push a lot of different things forward under one umbrella. Firefox shipped a ton of stuff but there are plenty of cases where the Google team raced ahead on a proposed functionality which reasonable people might have wanted to implement differently, and since PWA was a Google marketing campaign that means that any pressure to implement it is going to be balanced by questions about whether it really benefits many users.
iOS Safari does support service workers and "add to home screen". You can't however prompt the user for "add to home scree" - the user has to do it via the Safari menu. The notification dialog is a disaster in Chrome as all sites asks for it, few sites asks to be installed on the desktop though.
Safari does lack some functionality that Chrome has - maybe Safari could add that functionality if the user adds the web site/app to the home screen... like native file system, Bluetooth api, etc.
You're probably using PWA sites without realizing it. Many SPA frameworks add a basic service worker automatically. It's the 'install this page as an icon on home screen/desktop' that's super rare and not well supported.
