as I mentioned in the earlier discussions, I think the manifest should be the source of truth for the app name. Option 3 has the drawback of being a marketplace specific solution and will not work for sideloaded apps and other stores (if they do not implement this feature)
I vote for option 1. I am assuming it is upto the runtime to determine when to display the "name" attribute vs the "short_name" attribute on the device. regards Vishy ----- Original Message ----- From: "Andrew Williamson" <[email protected]> To: [email protected] Sent: Wednesday, April 23, 2014 10:52:21 AM Subject: Re: Adding a 'short_name' to the manifest option one would be my preference, or option two. Option three was what we effectively had a while a back and was more confusing for developers. On 17/04/2014 21:27, Wil Clouser wrote: > Hi, > > We are hitting a scenario in the apps world which warrants some discussion. > The > Marketplace was built to treat the manifest as the ultimate source of truth > and > changing your app's name or authors in the manifest would automatically update > it on the Marketplace. > > Harald has brought up a couple of use cases a few people are hitting (from bug > 991288): > >> Use Case: >> 1) Game developer X has a game with a well-known brand "Give me Cookies!". >> For the device the name would be too long so they set the "name" in the >> manifest to "Cookies!". When submitting the app to Marketplace they want to >> use the full name, as there is no space limitation that would require >> shortening the name. >> >> 2) App studio Iahoo has a weather app. The brand is well known, so for >> Marketplace they want it to be titled "Iahoo Weather", but on the device >> "Weather" would work better. > > Both Apple and Google allow developers to set short and long names on their > stores, so there is some precedent here. From the Marketplace POV, I'd like > to > continue to keep the manifest as the source of truth so my first reaction > would > be to add an optional "short_name" attribute to the manifest which would be > used > on the device in icon grids, but for places where space wasn't an issue (both > on > the device and on the Marketplace) we would use the current "name" field. > > An obvious alternative to that would be the inverse - we add a "long_name" > field > to the manifest and use that in the appropriate places. This may be less work > for the device (I'm not sure) but feels more awkward to me as a developer. > > A third option would be to just let developers choose a name in the > Marketplace > and ignore the manifest altogether, but that means developers have to > maintain a > name in two places and it doesn't help any other marketplaces or websites > displaying apps. > > Thoughts? Ideas? > > Thanks, > > Wil > > PS - there is a potential for confusion between inconsistent short and long > names but we have a review process on the Marketplace so I'm mostly ignoring > that aspect for right now. > _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
