Firefox/Features/Sync Discoverability: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 37: Line 37:


== Next Steps ==
== Next Steps ==
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.
 
* Identify developer(s).
* Project kick-off meeting.
* Start hacking.


== Related Bugs & Dependencies ==
== Related Bugs & Dependencies ==

Revision as of 17:44, 31 March 2011

Feature Status ETA Owner
Improve Sync discoverability UX mockups done, figuring out resourcing. 2011-04-20 Ragavan Srinivasan

Summary

It's really hard for users to discover the Sync feature. By improving discoverability, we hope to:

  • Increase user uptake
  • Ensure users are already syncing & have data waiting when they setup Sync on Fennec.

Team

Who's working on this?

  • Lead Developer: TBD
  • Product Manager: Ragavan Srinivasan
  • QA: TBD
  • UX: Alex Faaborg
  • Project Manager: Jennifer Arguello

Release Requirements

  • Does not affect performance in production/beta channel builds.
  • Promotions can be turned off, if needed.
  • Promotion text is localized.
  • Promotion text may be modified out of band. [P2]

Next Steps

  • Identify developer(s).
  • Project kick-off meeting.
  • Start hacking.

Related Bugs & Dependencies

Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.

Designs

Any and all mockups, design specs, tech specs, etc. Either inline or linked to.

Goals/Use Cases

The high level goals for the feature (which the release requirements checklist should fulfill). These are the guiding light and overall vision for the feature. Refer to this if there is confusion or are disputes about direction, designs, planning, etc.

Non-Goals

Things we are specifically not doing or building as part of this feature.

Other Documentation

Can include things like:

  • Competitive landscape
  • Research & references
  • Whatever else is useful to the project.

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked, but not yet at risk of missing this release.
  At Risk: feature is at risk of missing this release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.


Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.