>>Project/Request Title: Firefox Marketplace promo buttons/creatives >>Project Overview: Partners often want to promote their apps which have been submitted to the Firefox Marketplace on various places online, from blog-posts, their homepage, advertising, marketing and more. They are used to having creative assets similar to these on other platforms such as Android, iOS, Windows Phone and Blackberry. >>Creative Specs & Deliverables: A set of creative assets both vector (PSD, AI) for partner use in print etc. — as well as set or suggested sizes and ratios from us in web ready PNG format. >>Launch Date: 2013-07-26 >>Creative Due Date: 2013-07-19 >>Mozilla Goal: Firefox Marketplace >>Points of Contact: ARRAY(0x7fbed22c0e20)
Created attachment 772991 [details] Eaxmple of 'Available on Google Play' asset This is a single example of a Google Play asset. They are avilable in various sizes and formats that the content/app owner can choose from. Besides web assets (PNG) they also have high-res assets (PSD, AI) so that they can also use in the print and marketing promotional material that's offline.
Assigning this to Sean, who had already done some initial prototyping on this sort of thing several months ago. Dees, two questions for you: - can you confirm that the featured brand here is the Marketplace? As in "Available in the Firefox Marketplace" - that sort of thing? - can you advise on the sizes needed? That's the #1 thing we'll need before getting started.
(In reply to John Slater from comment #2) > Assigning this to Sean, who had already done some initial prototyping on > this sort of thing several months ago. > > Dees, two questions for you: > - can you confirm that the featured brand here is the Marketplace? As in > "Available in the Firefox Marketplace" - that sort of thing? Yes it is — In this case it's Interia (partner) asking. They want to promote their x 8 apps and yes they are all live. https://marketplace.firefox.com/search?q=interia One interesting thing to note, is that being Polish (and having other locale partners) localising the set into at least Spanish, Polish, Portuguese, Hungarian etc would be super useful too. > - can you advise on the sizes needed? That's the #1 thing we'll need before > getting started. I don't have a set size. I'm not aware if these things have had a standard built up around them. Sean may be best to advise. From what I've seen the other stores offer a variety of sizes and formats and content owners choose the one that best suits them. Sean — any thoughts here?
The reason I'm being particular about the sizes is that I don't want to create something and then learn that it wasn't usable b/c the sizing wasn't right for whatever reason. One option would be to download the Apple set of buttons - http://www.apple.com/itunes/affiliates/resources/documentation/badges.html - and base ours off those sizes, as I'd imagine they've put quite a bit of thought into it, but I'd still want to verify with the partners that that sounds right. Dees, would be great if you could dig in a little further on that. Another note is that these sorts of things typically come with fairly detailed instructions on how to use them (ex. http://www.apple.com/itunes/affiliates/resources/AppStoreMarketingGuidelines.pdf). Mentioning that b/c I think, overall, this is an important project to work on but not necessarily a small one.
Yes, this is partners expectations. Having a range of our proposed sizes and dimensions is a what they want rather than taking something and then hacking it around. They also want it to especially when in print and online material and sitting next too the other badges (iOS, Google Pay, Windows Marketplace, Blackberry) Google Play even has an online builder as well as guidelines: http://developer.android.com/distribute/googleplay/promote/badges.html
The batch I had done prior used the App Store and Android sizes. Here's an example of what we could do using those sizes (since partners are already ok with those) http://cl.ly/image/3K2r1Z1X3j1O/o If those are ok, I can package them up - we can offer charcoal and orange versions but the black seems to be a standard... if we want to follow their lead... and contrast clarity. As for a vector version, I'd probably just make a vector version of the largest example there.
One thing to note - I couldn't use the official wordmark since "Firefox Marketplace" is, well, an incredibly long wordmark. :) I think this is a good compromise and I stamp it with my brand approval stamp of justice.
I really like these, thanks Sean. Dees, wdyt?
I like them. My only discussion point would be around the 'rocket/shopping bag icon'. Is this as recognisable as opposed to some form of the Firefox logo or new style visuals? (right now I don't think end users get the difference between the Firefox MArketplace and the Firefox OS Marketplace. They all assume its for Firefox OS) See attachment for other ways content partners are displaying availability. Do we/Could we have an option for this style too?
Created attachment 777058 [details] Another e.g on how partners are displaying marketplace availability In relation to comment #9
Whatever the call, Sean — yes to a package as well as a vector. Ideally if they could live on a url that would be ace, perhaps even linked to from MDN as well as the Developer Hub.
The rocket allows us to not have to shrink the text smaller in this form factor since it is narrower. Since the rocket is the default symbol for an app in FxOS and is on the bag for Marketplace, we should be fine.
As for a one color glyph for your other example, we already have a 1-color glyph of the bag on the assets repo. That should do. It has the rocket, so there is visual consistency with the buttons, unlike the other contenders you see there. ;)
Sounds good to me.
Thanks Sean. Dees, are we all set here? Should Sean prep the final assets?
A for away. Thanks team.
Sean, please post a link to the files here as soon as you're able. Thanks!
The 3 colors and 3 different sizes can be found here: https://assets.mozillalabs.com/Projects/Firefox%20Marketplace/Badges/ I'll post a vector version once complete.
Vector versions up now too. Enjoy!
Ace. Thanks, Sean. Are we considering l10n versions? The highest priority is for ES, PL, PT-BR, DE, HU, RS (Serbia) and ME (Montenegro)
...and what may be it's very first use in the wild. http://ruk.ca/app/checkin
We'd need to outsource the creation of those most likely. What are common practises by Apple and Google? Do they offer translated versions? Not that we model ourselves off them, but would be interesting to see some examples. I ask because space is very tight at these sizes.
I'm not 100% sure. I recall mostly seeing them in English — but I do wonder if localising at least in ES, PT-BR and PL to start would be a good test, perhaps.
Hello, here is José Luiz from Business Development Latam, please find hereunder links to access all the badges for google play and Apple store in several languages: Google Play: http://developer.android.com/distribute/googleplay/promote/badges.html Apple store: https://developer.apple.com/news/?id=08222011a (In reply to Desigan Chinniah from comment #23) > I'm not 100% sure. I recall mostly seeing them in English — but I do wonder > if localising at least in ES, PT-BR and PL to start would be a good test, > perhaps.
So awesome to see this already used in the wild!! Dees, to be clear on the workflow, if you'd like these buttons localized you'll need to work with our l10n team (would suggest Peiying Mo and Pascal Chevrel as starting points) to get the translations done. Once those are ready, my team can help update the actual graphic files. Just want to be clear that you don't need to go through us for l10n, nor are we really staffed to be able to manage those requests directly.
(In reply to John Slater from comment #25) > So awesome to see this already used in the wild!! > > Dees, to be clear on the workflow, if you'd like these buttons localized > you'll need to work with our l10n team (would suggest Peiying Mo and Pascal > Chevrel as starting points) to get the translations done. Once those are > ready, my team can help update the actual graphic files. Just want to be > clear that you don't need to go through us for l10n, nor are we really > staffed to be able to manage those requests directly. Understood. I'll connect with Pascal.
Hey All, Going to resolve this bug. If localized versions of the buttons are needed, go ahead and file a new project with. Thanks! Jennifer