Fixed Progressive Web App for Android and iOS

[simoncaron]

Changes

• Fixed manifest.json to allow standalone app start on iOS and Android
• Replaced PWA short name (Emby --> Jellyfin)
• Added files to support launch screens for iOS web app.
• Added a 512px icon png for Android launch screen.

This is an interesting replacement for an iOS app for Jellyfin. Launchcreens are a bit of a pain to implement since they must support every resolution available. If having all these links is problematic, I guess we could do without them but the launch screen will be white.

Before, the home screen link opened the browser and navigated to the jellyfin server:

Now, the home screen link appear as a native app:

[anthonylavado]

I support this

[dkanada]

I think this should go in the next minor release, it's a nice improvement.

[joshuaboniface]

It would need to be rebased off the release branch to make the release, but I'd be OK with that.

[anthonylavado]

There appear to be no merge conflicts... It's a pretty straightforward change tbh, with files we don't touch often.

[simoncaron]

Let me know what you prefer. I could always fix things on my side and submit a new pull request with the release branch as source.

[DrPandemic]

You don't need a new PR. If you would like to keep this PR you can

1. Rebase your branch on your repo on release-10.3.z
2. Force push
3. Change the target branch at the top of this page (you first need to click on edit)

[simoncaron]

Now on release-10.3.z

[skug67]

Doesn't seem to pick up when jellyfin is being served at suburl [https://host.domain.com/emby].

[skug67]

Dug around a bit and you can get the suburl working by modifying the "start_url" entry in manifest.json from "/web/index.html" to "/emby/web/index.html" Given that the system is currently listening at /emby as well as the root url, is there any reason not to change this entry so that it works for both default and non-default users? (In the long run we'll hopefully get the ability to configure the listening url on the dashboard, at which point we'll need to link up that setting with the start_url entry in manifest.json -- not that I know how that could be accomplished.)