Closed
Bug 891726
Opened 12 years ago
Closed 12 years ago
[User Story] Default Language Runtime Customization by SIM
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: pdol, Unassigned)
References
Details
(Keywords: feature, Whiteboard: [ucid:System24, FT:systems-fe])
Attachments
(1 obsolete file)
User Story:
As an OEM, of the superset of languages that I ship with the build, I want to be able to specify the default language to be used on the device based on the MNC/MCC setting from the SIM card inserted during the First Run Experience in order to target customizations to locales without needing to use separate builds.
Acceptance Criteria:
1. If a certain language is specified to be used for an MNC/MCC combination, and a SIM card with that MNC/MCC combination is in the device during the First Run Experience, the language used on the device is that specified language.
2. If no SIM card is inserted during the First Run Experience, the specified default language is used by the device.
3. If no SIM card is inserted during the First Run Experience, and no default language is specified, the Mozilla defined (WHERE IS THIS DEFINED) default language is used by the device.
Updated•12 years ago
|
Blocks: koi-system-fe
Comment 1•12 years ago
|
||
This won't work when we have a SIM lock enabled.
The current flow in FTU is
1) Choose language.
2) Enter sim lock.
We need clarification if the order should change or how we should handle this scenario.
Flags: needinfo?(pdolanjski)
Updated•12 years ago
|
Whiteboard: [ucid:System24] → [ucid:System24, FT:systems-fe, KOI:P1]
Comment 2•12 years ago
|
||
Candice Serran deleted the linked story in Pivotal Tracker
| Reporter | ||
Comment 4•12 years ago
|
||
Francis, could you provide a UX recommendation on the order of the FTU in the event of a SIM lock?
Specifically, to pull the info from the SIM it needs to be unlocked first, which means the unlock would need to come prior to the choose language screen. Does this makes sense to you?
Flags: needinfo?(pdolanjski) → needinfo?(fdjabri)
Updated•12 years ago
|
Flags: in-moztrap?(atsai)
Updated•12 years ago
|
QA Contact: atsai
Comment 5•12 years ago
|
||
WIP. Mostly done, except the unit test and define the json location.
Attachment #798486 -
Flags: review?(arcturus)
Comment 6•12 years ago
|
||
Comment on attachment 798486 [details] [diff] [review]
Gaia patch [WIP] pending unit test and json location file
Sorry, not for this bug!!!!
Attachment #798486 -
Attachment is obsolete: true
Attachment #798486 -
Flags: review?(arcturus)
Updated•12 years ago
|
Flags: in-moztrap?(atsai) → in-moztrap?(jhammink)
Comment 7•12 years ago
|
||
Josh, can you take a look at Peter's question to Francis? Thanks!
Flags: needinfo?(fdjabri) → needinfo?(jcarpenter)
Comment 8•12 years ago
|
||
Josh, here's some more context from a chat I had with Peter today. The desired behavior is that the default language be based on the sim card. This is not a problem if the sim is not locked.
The problem arises when the sim is locked and a pin is set. If the sim is locked, default language selection can't work. This is compounded by the fact that the default language selection step in FTE comes *before* pin code entry in the flow, so the text on the pin code entry screen itself was not set to the default language based on the sim, and is probably in English.
Peter would like UX to advise on changing order of the FTE flow (more complicated) or perhaps on changing/dumbing down the string on the pin code screen to just "pin code" or similar, to at least diminish user confusion.
This user story was a must have for 1.2. For FTE work, eng is starting this Monday or Tuesday, so if your recommendation is "reverse the flow" we'll need someone from UX (probably you given our team size) to work with implementer to say "do this" with a good degree of precision instead of doing a spec.
Josh, Rob will be in Oslo as will Peter, so if you'd prefer me to ask Rob to take this so they can talk through it there on the ground just say the word. Thanks!
| Reporter | ||
Comment 9•12 years ago
|
||
After partner and UX discussions regarding moving the pin unlock screen prior to the language selection screen in FTE (without the ability to localize the strings), we have decided to not pursue this feature at this time as the workaround is quite straightforward (user selects their language).
Further, a default language can be select for the build which mitigates the need to have it configurable per locale.
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(jcarpenter)
Resolution: --- → WONTFIX
Comment 10•12 years ago
|
||
Peter Dolanjski changed story state to accepted in Pivotal Tracker
Updated•12 years ago
|
Flags: in-moztrap?(jhammink) → in-moztrap-
Updated•12 years ago
|
Whiteboard: [ucid:System24, FT:systems-fe, KOI:P1] → [ucid:System24, FT:systems-fe]
Updated•12 years ago
|
blocking-b2g: koi+ → ---
Comment 11•12 years ago
|
||
Candice Serran deleted the linked story in Pivotal Tracker
You need to log in
before you can comment on or make changes to this bug.
Description
•