canmove, Confirmed users
457
edits
No edit summary |
|||
| Line 90: | Line 90: | ||
== Requirements == | == Requirements == | ||
{| class="fullwidth-table" style="width: 950px" | |||
|- | |||
| style="font-weight: bold; background: #DDD; width: 30px" | Must Have | |||
| style="font-weight: bold; background: #DDD; width: 200px" | Requirement | |||
| style="font-weight: bold; background: #DDD; width: 100px" | Notes | |||
|- | |||
| X | |||
| The user has a streamlined set up experience | |||
| | |||
|- | |||
| X | |||
| The user is reassured that sync data is secure | |||
| | |||
|- | |||
| X | |||
| The user is not confused by any step in set up | |||
| | |||
|- | |||
| X | |||
| The value of Sync is clear to the user | |||
| | |||
|- | |||
| X | |||
| For initial Sync setup, the user must know that Sync is working before set up is complete | |||
| | |||
|- | |||
| X | |||
| When setting up a subsequent desktop browser, the user must know that Sync is set up | |||
| See in Mock up how personas should be updated. Still not clear. Adding to issues list. | |||
|- | |||
| | |||
| For a Sync user, reinforce how Sync works in the background | |||
| This is not part of set up, hence why it would be nice to have. It is not a blocker to completing this feature. | |||
|- | |||
| | |||
| For a Sync user, reinforce the Sync data is secure | |||
| This is not part of set up, hence why it would be nice to have. It is not a blocker to completing this feature. | |||
|} | |||
'''Non-goals''' | '''Non-goals''' | ||
| Line 113: | Line 140: | ||
== Open issues/risks == | == Open issues/risks == | ||
* Risk: There is a risk of a poor set up of a mobile device because a keyboard short cut may be too advanced for the non-techy Firefox users. Mitigation is to socialize this approach and get input from various folks including UR | * '''Risk:''' There is a risk of a poor set up of a mobile device because a keyboard short cut may be too advanced for the non-techy Firefox users. Mitigation is to socialize this approach and get input from various folks including UR | ||
* Risk: Not having the web page updates done by the time this feature is ready to launch is a launch blocker. The mitigation is to work with the web dev team to align schedules. | * '''Risk:''' Not having the web page updates done by the time this feature is ready to launch is a launch blocker. The mitigation is to work with the web dev team to align schedules. | ||
* Issue: There are no engineering resources available to do this work at this time. Jennifer will work with engineering to resolve this and get a timeline of staffing. | * '''Issue:''' There are no engineering resources available to do this work at this time. Jennifer will work with engineering to resolve this and get a timeline of staffing. | ||
* Issue: Are there any security risks? | * '''Issue:''' Are there any security risks? | ||
* Issue: Are there any privacy risks? | * '''Issue:''' Are there any privacy risks? | ||
* '''Issue:''' The way a user would know that a second computer has been setup for sync is unclear. | |||
== Legend (remove if you like) == | == Legend (remove if you like) == | ||