Closed Bug 1017591 Opened 10 years ago Closed 6 years ago

[FTE][System][Settings] We need a unified style for PIN screens

Categories

(Firefox OS Graveyard :: Gaia, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: fcampo, Unassigned)

References

Details

Attachments

(2 files)

Attached image SIM-PIN-Screens.png
We have three different PIN screens on different apps, but basically all of them does the same, so either we move the style/functionality to shared folder, or we keep the same code updated on all of them.

Whatever we do, we need to synchronize the UX on them. Once we reach an agreement between the apps, and we have a unique style, I can start opening the different (smaller) bugs
Not sure of the priority of this matter, or if it's included on any of the visual refresh in motion, so I'm asking to the UX people involved on the different teams.
FTE, System, Settings

Please forgive me if it's an overkill.
Flags: needinfo?(vpg)
Flags: needinfo?(ofeng)
Flags: needinfo?(jsavory)
Flags: needinfo?(cawang)
NI Przemek as he worked on the unifcation of keyboards and he might give a good input here.
Flags: needinfo?(vpg) → needinfo?(pabratowski)
For sure they should be consistent. ni? Settings UX owner Jenny.
Flags: needinfo?(ofeng) → needinfo?(jelee)
I'll bring this up in next weeks UX Frameworks meeting and get back to you with a set pattern. Thanks for sending this over.
Flags: needinfo?(pabratowski)
Hi Przemek, 

Any update from framework team? Thanks!
Flags: needinfo?(cawang) → needinfo?(pabratowski)
I believe we should be unifying to the pattern at the bottom of the attached image that uses the header 'Done' text. But since this is a pattern issue lets verify with Harly.
Flags: needinfo?(pabratowski) → needinfo?(hhsu)
Also, just to keep in mind for this screen, we do need two versions. One with the skip button and one without since they cover different scenarios.
Flags: needinfo?(jsavory)
This is a framework decision, will wait for Harly's comment on this. Tks!
Flags: needinfo?(jelee)
Jenny - Harly and I met with the frameworks team and put together some recommendations for this bug. Harly will review these with you later today. - Rob
Flags: needinfo?(jelee)
ok got it, thanks Rob!
Flags: needinfo?(jelee)
The framework team has gone through the proposals by Jenny today, and decided that we will have two kinds of PIN UI, one is for FTU, and the other is for System & Settings. FTU will have skip button on the header and back, next button at the bottom. System & Settings page will use a input dialog. Jenny will provide the spec. Thanks
Flags: needinfo?(hhsu)
Hi all, please see attached for PIN screen redesign. Tks!
Hi Jenny and Harly...

Just talking with Alive here in Berlin and we need a separate UI for changing the PIN versus enabling/disabling. Go to "Settings > SIM Manager > SIM Security > Change PIN" to see an example of what he means. 

Also, for System/Settings PIN screen style, do we need to show the scenario where the user gets the wrong PIN 3 times and has to enter their PUK code? Not sure what that flow looks like.

Rob
Flags: needinfo?(jelee)
Flags: needinfo?(hhsu)
(In reply to Rob MacDonald [:robmac] from comment #13)
Hello Rob, for this case ("Settings > SIM Manager > SIM Security > Change PIN"), I think what we should do is to change the current UI of "Change PIN" to an action button (it's currently with a chevron and button like border), tapping action button would trigger the system style PIN screen. I will upload an updated spec on this later. Thanks!
Flags: needinfo?(jelee)
Flags: needinfo?(hhsu)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: