Closed
Bug 829487
Opened 12 years ago
Closed 12 years ago
[FTE] PIN/PUK Screen should be placed after language selection
Categories
(Firefox OS Graveyard :: Gaia::First Time Experience, defect)
Tracking
(blocking-b2g:tef+, blocking-basecamp:-, b2g18+ fixed, b2g18-v1.0.0 fixed)
VERIFIED
FIXED
People
(Reporter: fcampo, Assigned: fcampo)
References
Details
Attachments
(1 file)
Better user experience (properly localized) if we show PIN screen after we select the language. If not, the screen and the errors will be shown in default language.
Assignee | ||
Comment 1•12 years ago
|
||
Nominating as is FTE, first app the user sees, and PIN screen is right now the first screen from the app. Users can be discouraged to keep using it if they don't understand what they see.
blocking-basecamp: --- → ?
Updated•12 years ago
|
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → fernando.campo
Comment 2•12 years ago
|
||
This is not tef+, because it will only impact users buying phones from outside their market.
blocking-b2g: tef+ → -
Assignee | ||
Comment 3•12 years ago
|
||
I don't understand what you mean about the impact only outside their market.
This will impact on any user with a PIN blocked simcard. Being shown before choosing the language may end up on user not understanding the messages and getting an awful first time experience.
Hence, I'm renominating, but please explain :)
blocking-b2g: - → tef?
Assignee | ||
Comment 4•12 years ago
|
||
Attachment #704268 -
Flags: review?(francisco.jordano)
Comment 5•12 years ago
|
||
This is a certification blocker for Telefonica, please mark again as TEF+. Please note that the PIN screen must be understood by all the users (e.g. Including Non Brazilian speakers that live in Brazil). Users not understanding this screen are potential callers to the Customer Care center because of locked phones.
Comment 6•12 years ago
|
||
Comment on attachment 704268 [details]
https://github.com/mozilla-b2g/gaia/pull/7692
Hi,
some comments on the PR.
Checked and seems to be working. Also got clear from Fernando the current behaviour:
If we pass the pin input and we press back, we will be again asking for pin to give the user the chance of reentering if skipped incorrectly.
Once comments on github are addressed the PR is looking good to me.
Thanks a lot Fernando.
Updated•12 years ago
|
Attachment #704268 -
Flags: review?(francisco.jordano) → review+
Comment 7•12 years ago
|
||
Daniel suggests this is a certification blocker, so this will remain tef+.
blocking-b2g: tef? → tef+
Updated•12 years ago
|
Blocks: b2g-v1-certification
Assignee | ||
Comment 8•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
status-b2g18:
--- → fixed
Comment 11•12 years ago
|
||
Landed on mozilla-b2g18/gaia master prior to the 1/25 branching to mozilla-b2g18_v1_0_0/v1.0.0, updating status-b2g-v1.0.0 to fixed.
status-b2g18-v1.0.0:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•