Services/Sync/Sync Setup Improvements Mobile

From MozillaWiki
< Services‎ | Sync
Jump to: navigation, search
Please use "Edit with form" above to edit this page.

Status

Sync Setup Improvements - Mobile
Stage Shelved
Status `
Release target CY2011 - FF9 (tentative)
Health OK
Status note This feature is now being covered in Sync Setup Impovements Conducting UR studies this week and next. Aiming to be requirement complete by 8/16.

Team

Product manager Jennifer Arguello
Directly Responsible Individual Jennifer Arguello
Lead engineer Richard Newman
Security lead Yvan Boily
Privacy lead `
Localization lead Axel Hecht
Accessibility lead `
QA lead Tracy Walker
UX lead Alex Faaborg
Product marketing lead Jaclyn Fu
Operations lead `
Additional members Ibai Garcia (SUMO)

Open issues/risks

Risk/Issue Status
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. UR studies in progress week of 7/18 and 7/25
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.
Are there any security risks? 7/18: JA spoke to infrasec and they have no security concerns. I need to speak to Lukas to make sure there are no browser security concerns.
Are there any privacy risks?

Stage 1: Definition

1. Feature overview

Sync is a service to keep the Firefox experience consistent across multiple devices. The adoption rate of new Sync users has plateaued and the percentage of single-device Sync users is the majority of users. The two main themes of this feature are to increase the adoption rate for Sync and to increase the number of Sync users with multiple devices (namely mobile devices). The goals below represent the findings of Sync Set Up usability testing and the culling of various feedback channels.

Goals

  • Decrease non-essential messaging in the Set Up flow
  • Insure the user is confident Sync will keep synced data secure and private
  • Let the user know that Sync is set up and working

2. Users & use cases

User: The user is a Firefox 4.0+ user. She/he has multiple devices that she/he would like to keep in Sync. The user may be span the spectrum of technical aptitude.

  • A user would like to set up Sync on a mobile device
    • Non-Sync user flow
    • Sync user flow

3. Dependencies

Dependency Owner Status
Provide updated setup flow to Web Dev Jen Due date TBD
Sync Web Page Copy Updates PMM (Jaclyn?) Due date TBD
Updated Sync Mobile Setup Video on Sync Web Page PMM? Due date TBD
Provide updated set up flow to Support Jen Due date TBD
Update support documentation Ibai Garcia Due date TBD
Provide l10n team en-us copy Jen? Due date TBD
Update l10n Sync pages Axel? Due date TBD
Update blogs of changes Jen Due date TBD

4. Requirements

Must Have Requirement 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

  • Enhance the Firefox Home set up experience

Stage 2: Design

5. Functional specification

`

6. User experience design

Initial UX mock ups. http://people.mozilla.com/~faaborg/files/projects/sync/usabilityProblems/#

In progress UR Study flow: http://people.mozilla.com/~faaborg/files/projects/sync/setup-i2/index.html

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

`


Feature details

Priority P1
Rank 999
Theme / Goal `
Roadmap Sync
Secondary roadmap `
Feature list Services
Project `
Engineering team Services

Team status notes

  status notes
Products ` `
Engineering ` Sketch notes from mcoates and ibai: Services/Sync/SetupConfusion.
Security sec-review-active imelven
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `