Open j26design opened 8 years ago
Well, although RFG generates the manifest, it's not intended to a a "universal web app manifest generator" if you see what I mean. I only made available the two options that made sense for Android Chrome (the two others where not supported; or were they similar to standalone
? Can't remember), without puzzling the user who only came from a simple set of icons for his site.
My rational is the following: if you need additional flexibility with the manifest, it means you are serious about web app development (you are not just coding a regular web site; else the manifest generated by RFG would be just good). If so, you are probably using modern build tools such as Gulp. And RFG has an option for this: the existing_manifest
parameter (in its API). The idea is to make RFG patch your hand-written manifest with the icons section.To see this in action, go to http://realfavicongenerator.net/favicon/google_web_starter_kit and look for existingManifest
in the generated code.
What is your opinion about this?
Chrome will parse these, but for instance fall back to standalone for fullscreen for now - That might change in the future.
As @phbernard mentioned, I managed to manipulate manifest creation.
You need to set existingManifest parameter with your default manifest settings.
... "display": "standalone", "orientation": "portrait", "onConflict": "override", existingManifest": "{ \"name\": \"SOME FULL NAME\", \"short_name\": \"SOME SHORT NAME\", \"start_url\": \"\/?utm_source=homescreen\", \"display\": \"standalone\", \"orientation\": \"portrait\" }" ...
There are 2 other display options that are available for the android manifest: