Some musings on the PWA "add to homescreen" feature on Android devices.

[Tim Curtis]

Another thing to try is to set CA:TRUE in the req template in /var/www/util/gen-gert.sh like beow.

Code:

[ req_ext ]
basicConstraints        = critical, CA:TRUE

I don't have an Android device and so not able to test this.

[the_bertrum]

OK, making it a CA worked and it installed correctly on my Pixel6 Android14. Oddly, when using this certificate to secure the player, the "Install Application" command re-appears in chrome on my phone and works correctly, even adding an icon the the app drawer rather than just putting a shortcut on the home screen.  This doesn't happen with the independent CA that I set up to sign the certs on my other players.  However, there now comes the issue that Firefox on all my devices (quite correctly) objects to the fact that we are using a CA certificate as an Identity certificate.  In PKI architecture, that is a circular argument and so insecure.

One step forward, one step back.

I'll keep digging.

[the_bertrum]

Actually, a bit more digging and I find that the "Install Application" command is working in Chrome for all my players as long as they are working over https (either using the automatic method with the CA hack or using my own CA).

Still have the Firefox "CA as Identity" problem with the cert-gen.sh CA hack though.

[the_bertrum]

After a bit more experimenting over the festive holidays, the definitive position is this:

HTTP, all browsers - "Add to homescreen" puts a widget on the home screen that launches the moode interface in a new full tab with address bars and all in the browser it was made in. The widget is the moode logo with the browser logo superimposed.

HTTPS, no matter how it's made to work, and assuming any warnings have been accepted
- Chrome: "Add to homescreen" action results in a proper "install" of the web app, it appears as an app like any other and opens full screen with no address bars or what have you.
- Chromium based browsers (most of the others): "Add to homescreen" action results in a widget on the homescreen that looks as it does for the HTTP version, but actually opens a full screen new instance of the interface, as always used to be the case. Not quite as integrated as the Chrome behaviour, but acceptable.
- Firefox: As was always the case, just opens the interface in a new tab.

So in short, it is working pretty much the same as it ever did as long as the browser thinks that the connection is secure.