CloudServices/FirefoxAccount: Difference between revisions

m
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=NOTE: This page is defunct and archived for historical purposes. Please visit the *active* [https://wiki.mozilla.org/Identity/Firefox-Accounts Firefox Accounts] page.=
= People =
= People =


Line 10: Line 12:


== UX ==
== UX ==
* Desktop: Zhenshuo Fang (fang)
* Desktop: Zhenshuo Fang (zfang)
* Android: Ian Barlow (ibarlow)
* Android: Ian Barlow (ibarlow)


Line 32: Line 34:


* Sync next generation technical plan: https://wiki.mozilla.org/Services/Sync/NextGen/TechnicalPlan.
* Sync next generation technical plan: https://wiki.mozilla.org/Services/Sync/NextGen/TechnicalPlan.
* Sign into Browser: https://wiki.mozilla.org/Identity/Features/Sign_into_the_browser


== UX ==
== UX ==
Line 38: Line 42:


* ibarlow's initial Android flows: http://cl.ly/image/2r3B1C2i462g
* ibarlow's initial Android flows: http://cl.ly/image/2r3B1C2i462g
Older UX prototype for "Sign Into Browser"
* New user on desktop: http://people.mozilla.com/~zfang/SignIn/Home.html
* New user on Mobile first run: http://people.mozilla.com/~zfang/SignInMobile/Mobile.html
* Existing sync user: http://people.mozilla.com/~zfang/SignIn_SyncUser/Upgrade.html


== Backend ==
== Backend ==
Line 43: Line 52:
* Draft PIdP spec: https://wiki.mozilla.org/Identity/FirefoxAccount
* Draft PIdP spec: https://wiki.mozilla.org/Identity/FirefoxAccount


* Draft Keywrapping spec: https://wiki.mozilla.org/Identity/CryptoIdeas/02-Recoverable-Keywrapping
* Draft Keywrapping ideas:
** https://wiki.mozilla.org/BrowserID_Key_Wrapping
** https://wiki.mozilla.org/Identity/CryptoIdeas/01-PBKDF-scrypt
** https://wiki.mozilla.org/Identity/CryptoIdeas/02-Recoverable-Keywrapping


* Standing dev token server: https://dev-token.services.mozilla.com
* Standing dev token server: https://dev-token.services.mozilla.com
* warner's initial server API repo and docs: https://github.com/warner/fxap-server/ and https://github.com/warner/fxap-server/blob/master/docs/server-api.md
* fmarier's inital server repo: https://github.com/fmarier/fxap-server


== Frontend ==
== Frontend ==
Line 52: Line 68:


* Speculative Firefox Account + Token Server flows: [[Services/FirefoxAccount/TokenServerFlows]]
* Speculative Firefox Account + Token Server flows: [[Services/FirefoxAccount/TokenServerFlows]]
* liuche's initial desktop addon repository: https://github.com/liuche/fxap-ff/tree/develop
* Android implementation bug tree: https://bugzilla.mozilla.org/showdependencygraph.cgi?id=799726&display=web&rankdir=TB
* Screencast of prototype Android UI (Bug 809210): http://people.mozilla.com/~nalexander/Firefox.Accounts.Android.UI.preview.webm with code at https://github.com/mozilla-services/android-sync/tree/nalexander/bug-809210-ui
** Product comments/questions about prototype Android UI: [[image:Product_Questions_about_Firefox_Accounts_Android_prototype.png|thumb|600px]]
**# Who's writing the copy?  Can we standardize on language?
**# What's the status of the branding?
**# I'd like the error UIs to match Persona.
**# Need link to terms and conditions.
**# Where does this link to?
**# Need forget password functionality.
** nalexander's responses as of December 6, 2012:
**# Who's writing the copy?  Can we standardize on language?
**#* I assume UX and Product will write the copy.  The existing copy is a mashup of ibarlow's original mocks with nalexander's tender loving.
**# What's the status of the branding?
**#* That's a good question.  As benadida hinted via email, what the branding should be is very much open for debate.
**# I'd like the error UIs to match Persona.
**#* I think this is a great idea, since the Identity product team has done good work in this area.  I haven't tried to convince Android to match the Persona look and feel, but we'll do what we can.  If we don't go with Persona-style UI and branding, I think this is very much open game.  I put some ad hoc error and progress UI in place mostly to give ibarlow a framework to hang a second iteration of his mocks.
**# Need link to terms and conditions.
**#* Agreed.  Further: we're connecting to Sync, and possibly a Mozilla Services token server.  Each service has ToS.  How do we display 3 ToS in a meaningful way?
**# Where does this link to?
**#* Unspecified, but I kind of assumed persona.org.  At this point, it seems like that may not be valid.
**# Need forgot password functionality.
**#* With the key-wrapping scheme proposed by Identity and Services, making a Persona-like "forgot password" flow is not really possible.  If this is a strong product requirement, we need to surface this immediately.  As of some months ago, this was not an immediate requirement for Sync: https://wiki.mozilla.org/Services/Sync/NextGen#TBD
canmove, Confirmed users
1,173

edits