Mobile/Projects/Firefox Accounts with Sync 1.1 integration: Difference between revisions

← Older edit

Mobile/Projects/Firefox Accounts with Sync 1.1 integration (view source)

Revision as of 18:57, 10 March 2014

994 bytes added , 10 March 2014

→‎Security/Encryption

ErinL ancaster

canmove, Confirmed users, Bureaucrats and Sysops emeriti

5,401

edits

@@ Line 31: / Line 31: @@
 * {{mok}} Users can create a Firefox Account
 * {{mok}} Users can delete their Firefox Account
-* {{mok}} Firefox Account will enable the current Sync (v1.1) service, and the new Sync (v1.5) service? '''<== rnewman'''
+* {{mok}} Firefox Account will enable the new Sync (v1.5) service
 * {{mok}} Users can sign in to their Firefox Account
 * {{mok}} Users can sign out of their Firefox Account
-* No support for federated accounts (although it is understood persona may be leveraged) '''<= is this true? I thought we want the new, non-persona protocol because we want accounts to be federated'''
+* No support for federated accounts
 * Current sync functionality must be supported, with the following being must-haves:
 ** {{mok}} Bookmarks must be synced, with no requirement to manage bookmarks from the non-originating
-** {{mok}} History must be synced (to make the awesomebar relevant) using the current sync algorithm for number of days we sync '''<== Is this what we are doing?'''
+** {{mok}} History must be synced (to make the awesomebar relevant) using the current sync algorithm for number of days we sync
 ** {{mok}} Passwords must be synced to make the mobile experience that much tighter
-** {{mok}} Security standards must be adhered to in order to protect my saved passwords during syncing '''<== is there anything to note, here?'''
+** {{mok}} Security standards must be adhered to in order to protect my saved passwords during syncing '''as strong as your password vs. a randomly generated key.'''
-** Add-ons must be synced between desktop machines only '''<== when do we think addons will be in scope or will they ever?'''
+** Add-ons must be synced between desktop machines only '''protocol is designed to do it for android, go to backlog (same as syncing prefs)'''
-* 'Clearing Private Data' in the Settings menu results in current, existing behaviour (which we all know is confusing and convoluted, but we don't have agreement on expected behaviour)<== '''what's the latest on this'''
+* 'Clearing Private Data' in the Settings menu results in current, existing behaviour
 * {{mok}} 'Sync' as a name remains unchanged in the UI or corresponding materials
@@ Line 49: / Line 49: @@
 * {{mok}} COPPA requirements when creating a Firefox Account must be adhered to within the creation flow
 * {{mok}} Present to the user what data will be synced and how this relates to ''their'' Firefox experience
-**{{mprop}}Includes messaging what 'history' really means to the user and what benefit syncing history provides
+**{{s}}Includes messaging what 'history' really means to the user and what benefit syncing history provides {{/s}}
 **{{mok}} Provide an option for which sync data types can be synced before the initial sync begins, applied to the Firefox Account level and not on a per-device level
 ** https://wiki.mozilla.org/User_Services/Sync/Datatype_Selection_Fx29
 * {{mok}} Users must not be forced to set up a Firefox Account if they either wish to defer the setup experience or never sign up at all. In this case, the user must be able to continue using the browser as expected, but without any benefits to having a Firefox Account
 ** This also means the user will not be able to benefit from sync - if a user wishes to set up sync, they can only do so via a Firefox Account come the introduction of Firefox Accounts
-* {{mok}} Users with an existing current Sync account (2+ devices attached to existing sync) must still be able to continue using their sync account using their existing connected devices for a transition period (minimum 3 months / 2 releases from when outbound communication has begun) '''<== do we have a transition plan?'''
+* {{mok}} Users with an existing current Sync account (2+ devices attached to existing sync) must still be able to continue using their sync account using their existing connected devices for a transition period (minimum 3 months / 2 releases from when outbound communication has begun) '''we don't stop existing sync users for Fx29'''
 * {{mprop}} Users with an existing current Sync account (2+ devices attached to existing sync) should have a link somewhere that they can follow to explain what Firefox Accounts is and that it will be 'coming soon', given that upsell / migration will not be available to them until Fx30 '''<== how is this manifested? SUMO?'''
 * {{mok}} Users must be able to change their Firefox Account passwords '''different from reset/forgot password flow'''
-* {{mok}}Users must be able to reset their Firefox Account passwords  '''<== this happens via https://accounts.firefox.com'''
+* {{mok}}Users must be able to reset their Firefox Account passwords  '''<== this happens via https://accounts.firefox.com, not in-app quite yet'''
-;elan placeholder
 * {{mprop}} For users who have not signed up to Firefox Account upon initial install, they may be notified or prompted to set one up in order to enable Sync '''this looks like a Fx30 thing'''
 * {{mok}} For users who have not signed up to Firefox Account upon initial install, they must be able to initiate and complete the process from somewhere in the Settings menu
 * {{mok}} For users who do not have an existing sync account in Fx 29, be able to present a snippet in the promo banner advertizing and linking to the FxA account flow to enable sync
-* {{mprop}} For users who have not signed up to Firefox Account or have existing sync enabled, present the ability to create an account to enable sync from the 'sync tabs' panel. NB - this is a nice-to-have in Fx 29.  '''there isn't a sync tabs panel'''
+* {{mprop}} For users who have not signed up to Firefox Account or have existing sync enabled, present the ability to create an account to enable sync from the 'sync tabs' panel. NB - this is a nice-to-have in Fx 29.  '''there isn't a sync tabs panel for fx29, tracking Fx30'''
 === Existing sync ===
-* By setting up Firefox Account on a desktop or Android device, users expect the sync experience to propagate across all attached instances where Firefox Account signed-in and used; including bookmarks, history (awesomebar results), passwords, ability to send open tabs, add-ons [between desktop instances only]
+* {{mok}} Frequency of syncing should remain the same when we transition to the new account creation model '''this has actually improved for existing sync users on android'''
-* Frequency of syncing should remain the same when we transition to the new account creation model
 === Detaching Sync ===
@@ Line 74: / Line 72: @@
 === Security/Encryption ===
 * It is expected that synced data is encrypted securely along with their Firefox Account password
-* Security defaults should be the same as per existing Sync 1.1 logic, with higher-level security options available
+* Security defaults should be the same as per existing Sync 1.1 logic, with higher-level security options available '''data is as secure as your password, also could be open to phishing. Self-hosting and higher sec options are blockers for EOLing current sync. We need an optional secondary credential'''
-** Expected: all user data currently irrecoverable
+** Expected: all user data currently irrecoverable '''cannot recover password is plan of record'''
 === Performance & Stability ===
-* In the event of service interruption to Sync, this must have no impact with current use of the browser
+* <s> In the event of service interruption to Sync, this must have no impact with current use of the browser. </s>
-* In the event of service interruption, all data that should be synced will sync once service is restored in a way that is seamless to the user and without degradation to browser usage
+* {{done|}} In the event of service interruption, all data that should be synced will sync once service is restored in a way that is seamless to the user and without degradation to browser usage
-=== Migration ===
+=== Fx30 Migration ===
 * We want to encourage existing Sync users to migrate to a Firefox Account, without harming the experience of existing users (defined as those who have 2+ devices attached to an existing sync account) who aren't ready to move for a minimum period of 3 months from when outbound communication has begun.
 * There must be overlapping support for current sync accounts who haven't signed up to Firefox Account and to the new Firefox Account & sync v1.1 for a minimum period of 3 months from when outbound communication has begun
@@ Line 92: / Line 90: @@
 * As a user, I want the option of setting up a new Firefox Account when I first install Firefox, so I can sync my browser data between my devices.
 ** AC 1.
-*** A new user installing Firefox for Android for the first time, there is at least one obvious entry point for setting up a Firefox Account that allows me to enable sync (whether from the promo banner or settings menu)
+*** {{mok}} A new user installing Firefox for Android for the first time, there is at least one obvious entry point for setting up a Firefox Account that allows me to enable sync (whether from the promo banner or settings menu)
-* As a user, I want a way to clearly understand what data Sync is actually Syncing, what that data means in terms of my browser functionality, and what happens to that data when I have logged out of my Firefox Account.
+****ACTION: Set milestone for turning on promo banner. We need the banner to be intelligent until it has an API to talk to it so it knows that people have {{bug|917942}}
+* {{mok}} As a user, I want a way to clearly understand what data Sync is actually Syncing, <s> what that data means in terms of my browser functionality, and what happens to that data when I have logged out of my Firefox Account. </s>
 ** AC 1.
-*** Well worded messaging around the relevance of 'history' is explained or reworded to better reflect the benefit (which is consolidating awesomebar results regardless of the screen used to visit a website)
+*** {<s> Well worded messaging around the relevance of 'history' is explained or reworded to better reflect the benefit (which is consolidating awesomebar results regardless of the screen used to visit a website) </s>
 ** AC 2.
-*** Messaging to inform the user prior to starting the initial sync to ensure 'no surprises'
+*** <s> Messaging to inform the user prior to starting the initial sync to ensure 'no surprises' </s>
-* As a user, I want to set up a Firefox Account using an email address and password of my choice, so I am not required to use any particular third-party sign-in service - I am comfortable using an email address of  my choice for this purpose.
+* {{mok}} As a user, I want to set up a Firefox Account using an email address and password of my choice, so I am not required to use any particular third-party sign-in service - I am comfortable using an email address of  my choice for this purpose.
 ** AC 1.
-*** User can chose to use an email address of their choice
+*** {{done|}} User can chose to use an email address of their choice
 ** AC 2.
-*** User can chose whatever password of choice, provided it adheres to the security standard we wish to employ (password strength rules)
+*** {{done|}} User can chose whatever password of choice, provided it adheres to the security standard we wish to employ (password strength rules)
 ** AC 3.
-*** If the password chosen does not adhere to Mozilla's password strength rules, messaging must be presented to the user clearly indicating the rules and allow them to try again
+*** {{mrisk}} If the password chosen does not adhere to Mozilla's password strength rules, messaging must be presented to the user clearly indicating the rules and allow them to try again
-* As a user, I don't want to be forced to create a Firefox Account when I first start using Firefox, so I can start using the browser as quickly as possible once I've downloaded and installed it.
+* {{done|}} As a user, I don't want to be forced to create a Firefox Account when I first start using Firefox, so I can start using the browser as quickly as possible once I've downloaded and installed it.
 ** AC 1.
-*** In the FxA setup flow, users must be able to cancel out of the flow
+*** {{done|}} In the FxA setup flow, users must be able to cancel out of the flow
 ** AC 2.
-*** If a user does not chose to initiate or complete the FxA creation flow, the user can still use the browser without any change in browser functionality EXCEPT that they cannot enable sync
+*** {{done|} If a user does not chose to initiate or complete the FxA creation flow, the user can still use the browser without any change in browser functionality EXCEPT that they cannot enable sync
-* As a user, I want all of my data (history, bookmarks, etc.) to be saved on my local machine whether or not I've set up a Firefox Account, so I am  still able to build up a collection of data and personalize my Firefox  experience over time.
+* {{done|}} As a user, I want all of my data (history, bookmarks, etc.) to be saved on my local machine whether or not I've set up a Firefox Account, so I am  still able to build up a collection of data and personalize my Firefox  experience over time.
 ** AC 1.
 *** No loss in current browser functionality in terms of storing history, passwords, etc whether a FxA has been created or not
-* As a user, I want to be able to change the password for my Firefox Account data from any device that allows me to sign into my Firefox Account, so if someone does steal my  laptop or other mobile device they won't be able to access any ''new''  data that is added to my Sync Account, even though they will be able to  access the data that had been previously synced and is local on the  device.
+* {{done|}} As a user, I want to be able to change the password for my Firefox Account data from any device that allows me to sign into my Firefox Account, so if someone does steal my  laptop or other mobile device they won't be able to access any ''new''  data that is added to my Sync Account, even though they will be able to  access the data that had been previously synced and is local on the  device.
 ** AC 1.
-*** There is an intuitive flow in the Settings / Sync menu that allows a user to change their FxA password
+*** <s> There is an intuitive flow in the Settings / Sync menu that allows a user to change their FxA password </s>
 ** AC 2.
-*** Once password change, other screens logged into FxA must prompt the user at the earliest possible stage to enter the new password
+*** {{done|}} Once password change, other screens logged into FxA must prompt the user at the earliest possible stage to enter the new password
 ** AC 3.
-*** Although current synced data cannot be undone, new data cannot be synced to other screens logged into FxA until the new password has been entered
+*** {{done|}} Although current synced data cannot be undone, new data cannot be synced to other screens logged into FxA until the new password has been entered
-* As a user, I want to be able to reset the password for my Firefox Account data from any device that allows me to sign into my Firefox Account, so I can continue using my Firefox Account even if I have forgotten my password.
+* {{done|}} As a user, I want to be able to reset the password for my Firefox Account data from any device that allows me to sign into my Firefox Account, so I can continue using my Firefox Account even if I have forgotten my password.
 ** AC 1.
-*** There is an intuitive flow in the Settings / Sync menu that allows a user to reset their FxA password
+*** <s> There is an intuitive flow in the Settings / Sync menu that allows a user to reset their FxA password </s>
 ** AC 2.
-*** Once password change, other screens logged into FxA must prompt the user at the earliest possible stage to enter the new password
+*** {{done|}} Once password change, other screens logged into FxA must prompt the user at the earliest possible stage to enter the new password
 ** AC 3.
-*** Although current synced data cannot be undone, new data cannot be synced to other screens logged into FxA until the new password has been entered
+**{{done|}} * Although current synced data cannot be undone, new data cannot be synced to other screens logged into FxA until the new password has been entered
-* As a user, I want to be prompted to create a Firefox Account when I first install my browser, but I want it to be easy to dismiss with a prompt to dismiss either forever (so I don't get bothered again), or to be reminded again later.  I also want it to be very easy to get more details about what a Firefox Account is and why I would want it before I go through the process of creating one.
+* {{mprop}} As a user, I want to be prompted to create a Firefox Account when I first install my browser, but I want it to be easy to dismiss with a prompt to dismiss either forever (so I don't get bothered again), or to be reminded again later.  I also want it to be very easy to get more details about what a Firefox Account is and why I would want it before I go through the process of creating one.
 ** AC 1.
-*** If there is a first-run experience to create a FxA upon initial browser install, users must be able to either complete the flow or dismiss the flow with no adverse effect in browser functionality EXCEPT that they cannot enable sync
+*** {{mprop}} If there is a first-run experience to create a FxA upon initial browser install, users must be able to either complete the flow or dismiss the flow with no adverse effect in browser functionality EXCEPT that they cannot enable sync
 ** AC 2.
-*** Users can either be reminded later to set up a FxA or be able to dismiss the prompt forever
+*** {{mprop}} Users can either be reminded later to set up a FxA or be able to dismiss the prompt forever
 ** AC 3.
-*** Any time a user is presented with a prompt to set up a FxA [in order to enable sync], clear and concise messaging must be provided as to the benefit of doing so before creating the account
+*** {{mprop}} Any time a user is presented with a prompt to set up a FxA [in order to enable sync], clear and concise messaging must be provided as to the benefit of doing so before creating the account
-* As a user, I want to be able to go into a settings menu to create my Firefox Account [to enable sync], so that I can set up it up in my own time.
+* {{mprop}} As a user, I want to be able to go into a settings menu to create my Firefox Account [to enable sync], so that I can set up it up in my own time.
 ** AC 1.
-*** Users without an existing sync account can go into the Settings / Sync menu to create a FxA in order to enable sync
+*** {{mprop}} Users without an existing sync account can go into the Settings / Sync menu to create a FxA in order to enable sync
-* As a product manager, I want to use the 'promo banner' real estate on the about:home default page to advertize the ability to create a Firefox Account to enable sync for new users only (not visible to users with an existing sync account) in Fx 29 as a real ideal way of spreading the message in-product.
+* {{mok}} As a product manager, I want to use the 'promo banner' real estate on the about:home default page to advertize the ability to create a Firefox Account to enable sync for new users only (not visible to users with an existing sync account) in Fx29 as a real ideal way of spreading the message in-product.
 ** AC 1.
-*** A snippet message can be displayed to a specific set of users (by geography, channel, Fx release) to encourage them to set up a FxA to enable sync
+*** {{mprop}} A snippet message can be displayed to a specific set of users (by geography, channel, Fx release) to encourage them to set up a FxA to enable sync
 ** AC 2.
-*** Tapping on the promo snippet takes the user to a FxA creation flow to enable sync
+*** {{mprop}} Tapping on the promo snippet takes the user to a FxA creation flow to enable sync
 ** AC 3.
-*** Existing sync users do not get this promo banner
+*** {{mprop}} Existing sync users do not get this promo banner
 ** AC 4.
-*** Users who have created a FxA to enable sync do not get this promo snippet again
+*** {{mprop}} Users who have created a FxA to enable sync do not get this promo snippet again
 * As a user, I want to be able to go into the 'sync tab' panel and be presented with an option to create my Firefox Account to enable sync to serve as another entry point a user may stumble upon. NB this is a nice-to-have for Fx 29, otherwise can be moved to Fx 30.
 ** AC 1.
-*** When a user taps the 'sync tab' in the tab tray, concise & clear messaging is provided about the benefits of creating a FxA to enable sync with a link taking the user to the account creation flow
+*** When a user taps the 'sync tab' in the tab tray, concise & clear messaging is provided about the benefits of creating a FxA to enable sync with a link taking the user to the account creation flow '''elan needs help on this'''
-* As a user, my only option to enable sync is to create a FxA from Fx29 onwards.
+* {{done|}} As a user, my only option to enable sync is to create a FxA from Fx29 onwards.
 ** AC 1.
-*** Current existing sync sign-up and device pairing is no longer supported from Fx29
+*** {{mprop}} Current existing sync sign-up and device pairing is no longer supported from Fx29
 ** AC 2.
-*** The only way to enable sync is by completing the FxA creation flow for new users
+*** {{mprop}} The only way to enable sync is by completing the FxA creation flow for new users
-* As a user, I want to be able to verify my email address and my desire to set up a Firefox Account by clicking a link in the verification email I received from Firefox
+* {{done|}} As a user, I want to be able to verify my email address and my desire to set up a Firefox Account by clicking a link in the verification email I received from Firefox
 ** AC 1.
-*** Users can open the verification email after completing the appropriate steps in the FxA creation flow
+*** {{done|}} Users can open the verification email after completing the appropriate steps in the FxA creation flow
 ** AC 2.
-*** Users can click a link in the email to verify their email address
+*** {{done|}} Users can click a link in the email to verify their email address
-* As a user, I want the option to review the ToS and Privacy Policy so that I can make sure I’m comfortable providing my information to Mozilla.
+* {{done|}} As a user, I want the option to review the ToS and Privacy Policy so that I can make sure I’m comfortable providing my information to Mozilla.
 ** AC 1.
-*** Users can link to the ToS from the “Create Account” page
+*** {{done|}} Users can link to the ToS from the “Create Account” page
 ** AC 2.
-*** Users can link to the Privacy Policy form the “Create Account” page
+*** {{done|}} Users can link to the Privacy Policy form the “Create Account” page
 ** AC 3.
-*** Both the ToS and PP will open in a mobile-friendly format
+*** {{done|}} Both the ToS and PP will open in a mobile-friendly format
 ** AC 4.
-*** A user may accept or decline the ToS and/or PP
+*** <s> A user may accept or decline the ToS and/or PP </s>
 ** AC 5.
-*** If a user declines the FxA creation flow is stopped
+*** <s> If a user declines the FxA creation flow is stopped </s>
 ** AC 6.
-*** If a user accepts, the FxA creation flow continues
+*** <s> If a user accepts, the FxA creation flow continues </s>
-* As a user I want to tell Firefox how old I am so that I can be cleared for COPPA restricted activities
+* {{done|}} As a user I want to tell Firefox how old I am so that I can be cleared for COPPA restricted activities. Birth Year only. 1990 and earlier for old foggies.
 ** AC 1.
-*** Users will be asked to provide their year of birth on the account set up page where they enter their email address and password
+*** {{done|}} Users will be asked to provide their year of birth on the account set up page where they enter their email address and password
 ** AC 2.
-*** If a user enters a year that indicates their age is less than 13 years old on the day they attempt to set up an accountm she will be denied a Firefox Account
+*** {{done|}} If a user enters a year that indicates their age is less than 13 years old on the day they attempt to set up an account she will be denied a Firefox Account. '''status:''' Times out for 15 minutes, or until browser is re-started.
 ** AC 3.
-*** If a user enters a year that indicates their age is at least 13 years old on the day they attempt to set up an account, she will be granted a Firefox Account
+*** {{done|}} If a user enters a year that indicates their age is at least 13 years old on the day they attempt to set up an account, she will be granted a Firefox Account
 === Core existing sync user stories ===
@@ Line 187: / Line 186: @@
 *** Screens I have signed in to FxA with the same credentials are all attached to the same sync profile so that the data is replicated across all linked machines
 ** AC 3.
-*** Users cannot detect any performance differences between current sync and FxA+Sync1.1
+*** Users cannot detect any performance differences between current sync and FxA+Sync1.5
 * As a user with several devices, I want my core Firefox experience to be available on all devices, so I don't have to spend a lot of time rebuilding my top sites & awesome screen experience.
 ** AC 1.
@@ Line 226: / Line 225: @@
 * As a user, I expect Firefox Sync to securely encrypt all my Firefox server data with my Firefox Account password.
 ** AC 1.
-*** Data is encrypted as per current security standards
+*** {{mok}} Data is encrypted as per current security standards
 ** AC 2.
-*** Data management must adhere to Mozilla security & privacy policies
+*** {{mok}} Data management must adhere to Mozilla security & privacy policies
 === Performance & Stability ===
@@ Line 237: / Line 236: @@
 *** Users must detect no change to browser performance when sync service is resumed and the backlog of sync data is being processed
-=== Migration ===
+=== [NOT MVP] Migration ===
 * As a user who currently has an existing sync account with 2+ devices attached to it, I cannot migrate to FxA+Sync1.1 using the standard points of entry in Fx29 but I can find out what's going on.
 ** AC 1.
@@ Line 260: / Line 259: @@
 *** Once EOL hits, existing users will not be able to access their sync unless they migrate to FxA
-==Quality Criteria for Fx29==
+==Goals and Quality Criteria for Fx29==
-*No migration
+* FxA set up and sign in
+* No Send Tab
+* No self-hosting, password only
-==Quality Criteria for Fx30==
+==Goals and Quality Criteria for Fx30==
+* Migration
+==Goals and Quality Criteria for Fx31==
+* EOL Legacy Sync
 == Tickets ==
@@ Line 276: / Line 281: @@
      "include_fields": "id, priority, summary, status, assigned_to, whiteboard",
      "order": "bug_id"
+}
+</bugzilla>
+</onlyinclude>
+=== Bugs that folks other than rnewman and nalexander can tackle ===
+<onlyinclude>
+<bugzilla>
+{
+    "include_fields": "id, priority, summary, status, assigned_to, whiteboard",
+    "order": "bug_id",
+    "product":"Android Background Services",
+    "whiteboard": "parallel"
 }
 </bugzilla>