Bill Walker wrote:
I think adding a short_name field makes sense. For sure the manifest needs to
be the source of truth about app names. We'll also need to think about what
happens when we install these apps on Android and Windows, I'm not sure if
other OS'es support long and short app names; if not, we'll want to document
that so we set developer expectations appropriately.
Android doesn't require apps to display a name/icon in its "top-level
launcher" (Home/All Apps screens or third-party interface) at all! And
apps can choose arbitrary names and icons for an arbitrary number of
"launcher intents" (main entry points) to display there.
But most apps I've installed have a single launcher intent whose name is
identical to or resembles the name of the app in the store. And our
Android runtime does exactly that for webapps. It currently uses the
manifest's "name" field, but it should be trivial to make it use a
shorter name, if available and desirable.
And the same should be true for the desktop runtime on all desktop
platforms: we can name a webapp's executable/alias/shortcut/bundle
anything we want.
So a short_name manifest field shouldn't present any problems on our
other runtimes, and I agree that it makes sense.
But I've been surprised and confused before on Android when an app I
installed gave its launcher intent a completely different name.
So we should consider steps to reduce the risk of such user confusion,
like requiring long and short names of apps in Marketplace to be
reasonably similar, or perhaps simply displaying both names in various
representations of the app (its Marketplace page, the "confirm install"
dialog, etc.).
-myk
_______________________________________________
dev-webapps mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-webapps
