Closed
Bug 1965107
Opened 10 months ago
Closed 8 months ago
Update the flow for when the user hasn't set up screen lock in android settings
Categories
(Firefox for Android :: Privacy, task)
Tracking
()
RESOLVED
FIXED
People
(Reporter: Gela, Assigned: Gela)
References
Details
(Whiteboard: [fxdroid][group2])
Attachments
(1 file, 2 obsolete files)
|
187.23 KB,
image/png
|
Details |
From Aarjav:
- When the user has previously set up screen lock in android settings. - Majority of users [Previous conversations] - Figma Design.
- When the user hasn't set up screen lock in android settings: some users [This new edge case] - Figma Design.
This user who has not set up screen lock in android settings (not firefox settings) will have to set to go set it up in settings, this cannot happen in the background. They would have to provide finger prints, choice of pin lock etc.
We would need to implement the second bullet point.
Pushing this off to phase 2 as it is not MVP and we are too close to release to include this.
Looking at Focus, if user does not have any sort of lock on their device, we simply grey out the toggle. I'm inclined to follow the same pattern.
Updated•10 months ago
|
Here's the finalized workflow:
- If device hardware does not support device lock, do not show the toggle at all
- If device hardware supports device lock and user has lock setup, show the toggle as it is
- If device hardware supports device lock but user does not have a lock setup, grey out the toggle with a link to Settings to enable device lock first (please refer to the Figma for more details)
Updated•10 months ago
|
Attachment #9486354 -
Attachment is obsolete: true
Updated•10 months ago
|
Attachment #9486840 -
Attachment description: WIP: Bug 1965107 - Only show Private Tabs Lock if user has a device lock enabled → Bug 1965107 - If user has not set up a device lock grey out the toggle and take them to the device settings
Updated•10 months ago
|
Attachment #9486840 -
Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•