827582 - MWC2013: Custom Chrome for Carriers (in the form of lightweight themes)

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: Theme and Visual Design, defect)

Description

[Erin Lancaster [:elan]]

In order to fortify conversations with individual carriers during MWC, we would like to have brand-centric, customized content for each of the targeted carriers (including one generic one that is spanish friendly). This bug covers the Chrome, or better put custom light weight themes but I am sticking to "Custom Chrome" nomenclature because the themes won't be distributed they way traditional, light weight themes are for our users. 

The design elements being requested include:
- Brand specific color and icons for the browser “theme,” the navigation bar, and settings for each *language*

3) The list of languages include: english, spanish, polish, german, and japanese

Outline of Carriers:
1) Generic (english, spanish)

2) Deutsche Telekom (english, polish, german)
   * http://www.telekom.com/home

3) ATT&T (english)
   * http://www.att.com/

4) NTT Docomo (english, japanese)
   * http://www.nttdocomo.com/

Comment 1

[Karen Rudnitski [:kar]]

I'm looking to clarify this request, as well as outline some structure / guidelines (that we can work on writing up / formalising BEFORE we get into customisation talks with partners) around how far we want and should go with this in the first instance (ie demo).

For context, if a carrier or partner sees that we can and are willing to give the world over to them, they'll demand it. Therefore we need to show what we ARE willing to give up from a branding standpoint, and stay strong on what still constitutes a 'firefoxy' experience that is not compromised for our users.

For this bug, I expect it just requires some clarification. I am assuming that we are looking to provide a 'light-weight theme' in the vein of each potential partner's branding colours. 

When we're referring to language, that's a question of locale (default locale?). This would, presumably, then satisfy the list of languages (which we all currently support in our multi-locale build). I am not sure what other customisation, if any, is being asked around language in this bug.

I am, however, looking for clarification on the 'settings' ask - what exactly does this refer to?

In my mind, I see this particular bug requesting support for 'light-weight themes' for targeted potential partners (and limited to our current implementation of light-weight themes). Then we should clarify how to ensure we can switch to our supported languages easily enough during MWC (to satisfy the language request) and clarify the 'settings' ask.

Comment 2

[Erin Lancaster [:elan]]

This is done. Closing.