851190 - Implement new design for Persona for Payments on Firefox OS

Status: RESOLVED WONTFIX

(Core Graveyard :: Identity, defect)

Description

[Maureen Hanratty]

We have some new designs to optimize Persona for mobile and create a consistent experience for Payments for Firefox OS. 

FLOWS (user not signed in, user signed in but must enter password, user signed in password saved, error states, password recovery, progress messaging, failure messaging, etc.)
Keynote: https://www.dropbox.com/s/t34t9xcbr2f1ert/Marketplace_Payments_Flows_Persona_031313.key 
PDF: https://www.dropbox.com/s/4xznirpujqidwdr/Marketplace_Payments_Flows_Persona_031313.pdf

VISUAL DESIGN SPEC (CSS to make your life easier)
Keynote: https://www.dropbox.com/s/nloqpw1t9lffsig/Marketplace_Payments_Flows_Spec_031313.key
PDF: https://www.dropbox.com/s/m38d7bfpnwoirmy/Marketplace_Payments_Flows_Spec_031313.pdf

ASSETS (buttons, spinners and stuff)
https://www.dropbox.com/sh/y5xiyftzti70aru/c6oTmFIiQt

Comment 1

[Jason Smith [:jsmith]]

This sounds like something that should be tracked in https://github.com/mozilla/browserid/issues?state=open, not here. It's also sounds like a meta bug too.

Comment 2

[Jed Parsons (use needinfo, please) [:jedp, :jparsons]]

Hi, Jason.  Maureen and I have talked about this, and it was my suggestion to create a meta bug in core::identity.  I'd prefer to track this here so we can more easily spawn bugs pertaining to identity, marketplace, trusted ui, gecko identity components, etc., as they arise, which they probably will since these designs affect the entire identity flow and touch on marketplace through the trusted ui (with inherited titles, for example).

Comment 3

[Jason Smith [:jsmith]]

(In reply to Jed Parsons [:jparsons] from comment #2)
> Hi, Jason.  Maureen and I have talked about this, and it was my suggestion
> to create a meta bug in core::identity.  I'd prefer to track this here so we
> can more easily spawn bugs pertaining to identity, marketplace, trusted ui,
> gecko identity components, etc., as they arise, which they probably will
> since these designs affect the entire identity flow and touch on marketplace
> through the trusted ui (with inherited titles, for example).

I suppose. There's technically already a tracking bug for any v1.next work in bug 846517 that was aiming to simplify the tracking flows for any post v1 work on the client side.  This feels like something though that belongs in Marketplace::Integration though, as that component tracks meta bugs like what you are describing that cross-cuts across components.

Comment 4

[Jason Smith [:jsmith]]

I'll wait for feedback on my comment before doing any component moving. But yeah, this feels like something that fits into the Marketplace::Integration component (which was designed for cases you are describing).

Comment 5

[Jed Parsons (use needinfo, please) [:jedp, :jparsons]]

I hadn't realized at first that these drawings included the marketplace screens as well.  That does broaden the scope.  I do still want to have a core::identity bug for the flow in these drawings that pertains to identity.  Maureen, Skinny, and I worked on the embedded persona flow from the point of view of identity: It is a coherent, end-to-end flow that will affect all RPs, not just marketplace.  If you want to morph this into a marketplace integration bug, that's fine by me; I can open a separate identity tracking bug specifically for the identity component.  Or we can revise the title of this bug and stress that it's just for identity.

Comment 6

[Jason Smith [:jsmith]]

(In reply to Jed Parsons [:jparsons] from comment #5)
> I hadn't realized at first that these drawings included the marketplace
> screens as well.  That does broaden the scope.  I do still want to have a
> core::identity bug for the flow in these drawings that pertains to identity.

That's true this pertains to identity, but core identity focuses on DOM issues, not UI issues. That's why I said this is more appropriate for github to make sure the right people are watching the issue (which is the majority of the identity team). I'd rather not pollute the Core bugzilla product with UX issues, preferably.

Anyways, process aside, the one thing I saw in the UX spec you need to investigate on feasibility is about that system error notification in the final page of the spec - that's making use of something within Gaia System component in a trusted context. Can third-party content make use of that system banner without invoking causing annoyance abuse?

Comment 7

[Jed Parsons (use needinfo, please) [:jedp, :jparsons]]

If it's a question of Core vs some other product, then let's establish a better place for b2g identity issues to reside in bugzilla.  Overall, though, we still prefer having the b2g-touching parts of persona live in bugzilla, and the non-b2g bits in the core browserid issues on github.  The screens here and the flows are b2g.

As for the gaia system banner, yes, that's certainly going to take some thought to get right.  But I very much like the proposal that we have a system-wide way of making announcements like these.  It will be a much more consistent experience for the end user, and a better toolkit for the developer.

Comment 8

[Jed Parsons (use needinfo, please) [:jedp, :jparsons]]

And just to reiterate about the bugzilla vs github issue here - I'm just talking about tracking this metabug in bugzilla.  I'm sure there will be plenty of related issues that come up in github, just as there will be b2g and gaia issues; but we can give global visibility from here.

Comment 9

[Jason Smith [:jsmith]]

Let's take this offline at this point.

Comment 10

[Maureen Hanratty]

Attachment: Failure message - full screen

If sign in fails we will show a full screen (Trusted UI) error message based on Gaia's confirmation message. Keynote and pdf documents have been updated with the change. 

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/UX/Building_blocks/Confirmation

Comment 11

[Jason Smith [:jsmith]]

FWIW, we still haven't resolved this tracking issue we're talking about in the above comments. Still waiting on a response to my email.

Comment 12

[Jason Smith [:jsmith]]

This really belongs under the PayAndID tracking bug.

Comment 13

[Maureen Hanratty]

Revised flows for Persona on payments. Made with input from Crystal.

Keynote:
https://www.dropbox.com/s/t9b16k2tew9pcow/Marketplace_Payments_Flows_Persona_042613.key

PDF:
https://www.dropbox.com/s/8qasgh14gdt9cmu/Marketplace_Payments_Flows_Persona_042613.pdf

Comment 14

[Ryan Kelly [:rfkelly]]

I'm WONTFIXing persona-related bugs now that we've committed to decommissioning in the persona.or service.