[Feature Request] PWA (Progressive web app) support

[edersong]

It would be a nice feature to be able to install the website as an app on Android and iOS.

Ref.: https://blog.heroku.com/how-to-make-progressive-web-app

[OzGav]

There is s desktop app in Alpha. There is no developer capacity to develop apps for other platforms although it is on the road map. If you want to take on the job that would be great.

[marcelveldt]

The MA frontend is already a PWA so ....

Navigate to the MA interface directly (bypass HA ingress) http://youripgoeshere:8095

But you may have to expose the webserver in the settings to allow this.

[ItsHarper]

Wow I hadn't even processed that Music Assistant doesn't have an authentication system

[cephos]

After some research I found we probably need the following option in the vitepwa config:

useCredentials: true

Tried now to find the config file in an attached console of my prod ma-installation in ha os to make quick test, but without succcess. Can someone point me to the right path? Or is this 'compiled' in and only available in a dev container?

[jace]

This isn't working for me either. I've setup a Cloudflare Tunnel for HTTPS and authentication. Confirmed from view-source that the manifest is still present. Chrome doesn't recognise it as a PWA, nor do other Android browsers.

[jace]

I've found a workaround for Cloudflare Tunnel. The trick is to make a separate Access Application pointing specifically to the manifest URL (<domain>/manifest.webmanifest) and link it to a new Bypass Policy that applies to Everyone. The manifest no longer requires authentication. Chrome Android showed an Install App prompt rightaway.

The downside is that the PWA isn't LAN-only.

[sameleff]

Were you able to get the PWA app working? I am using Firefox on iOS and reverse proxying the Music Assistant webserver with nginx. No auth is enabled in nginx. I have tried adding the shortcut by connecting directly to the ip:port and also to the proxied url - in both cases, the shortcut opens a new tab in Firefox rather than a full screen and standalone PWA app. Other services I self-host and configured analogously (e.g. OpenWebUI) successfully open in a standalone app when setup in the same manner through Firefox.