Closed
Bug 1060170
Opened 10 years ago
Closed 10 years ago
[PP] Guided Tour Flow
Categories
(Firefox OS Graveyard :: Gaia, defect, P5)
Tracking
(feature-b2g:2.2+)
RESOLVED
FIXED
| feature-b2g | 2.2+ |
People
(Reporter: marta, Assigned: marta)
References
Details
(Keywords: privacy)
Attachments
(2 files, 1 obsolete file)
The layout description
This is the bug for the Guided Tour where user should be educated on good privacy practices.
GT purpose is to educate the users on good privacy practices and inform them in a friendly and easy way about the consequences of their decisions. We will only include the explanation for features already implemented. Maybe one screen should be on the general issues. The user should be informed about the consequences of his decision (eg. If I choose the blurring method how will my usability be impacted? Why would I choose a blurring? WHy is it important to protect my location details?). If you hand the UI to a newbie, he should understand why he should even care. The GT, in case of RPP, should answer questions like - why would I want to use SMS to do the settings? Will I be charged for them? If so, what is the benefit? What are my incentives (no account, no need to access internet...). Similarly to the First Time Use, the GT should contain some graphics and an explanation. Illustration is important to give people an instant idea what is it about and how to use a feature. Our studies showed that having a graphic added to the GT is one of the factors people notice and value a lot.
QA Whiteboard: STATUS: waiting for UX decision, waiting for engineering decision
Priority: -- → P5
QA Whiteboard: STATUS: waiting for UX decision, waiting for engineering decision → STATUS: not started
QA Whiteboard: STATUS: not started → STATUS: implementation work
This is the final workflow of Guided Tour for PP. Illustrations will be provided later.
Attachment #8486527 -
Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
||
Updated•10 years ago
|
feature-b2g: --- → 2.2+
You need to log in
before you can comment on or make changes to this bug.
Description
•