Closed Bug 827169 Opened 11 years ago Closed 11 years ago

[Flicks] R2: Sign-in flows & video submission UX/IA

Categories

(Websites :: Firefox Flicks, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Habber, Unassigned)

Details

Attachments

(1 file, 2 obsolete files)

This bug contains flows and wireframes for sign up and video submission for the Flicks 2013 campaign. 


There are 3 entry points to initiate Persona flow:
1. Favoriting a video on the site (keep in mind that we are NOT using the Vimeo liking system which presents likes as a "heart" icon upon hover of the video player. We need to use a different icon than a heart (ie: star) to represent liking. This icon will live outside the video player. 

2. Stand-alone sign in via persona button in header 

3. Video Submission Button on landing page


We need Copy and action points for Thank You screen. I have suggested copy and links (ie: sharing) in the wireframes to start from.

If necessary, we will need copy for confirmation email. See attached wireframes for screenshot of current Vimeo confirmation email - how is this handled by Vimeo API and what control do we have over it?

Take a look at the interaction details for once a user has submitted a video. We need to be sure we can communicate this and that each step is designed if we can't directly pull in Vimeo visuals.
Summary: R2: Sign-in flows & video submission UX/IA → [Flicks] R2: Sign-in flows & video submission UX/IA
Attached is an updated PDF for the Submission and Sign-in flows.

There are some outstanding questions for Arcadio & team that we can discuss on Monday.

Copy: Matej, can you take a look at the copy for the submission screens? We will also need an email written confirming the posting of the user's video once processing is complete.

There are 2 points of sharing that will need copy for Twitter and Facebook. 
1) general sharing about Flicks at end of video submission process (user can not share link to their video until processing and review is complete)

2) sharing link in user's confirmation email that allows them to share the actual link to their video. 


We can review annotations and outstanding items in our Jan 14 dev meeting. I can go over copy with Matej at any time.


Direct link to latest file uploaded on Jan 13, 2013:
http://cl.ly/2b3K3B2l3Q1l
Attachment #698477 - Attachment is obsolete: true
* note that above wireframes only include video submission and sign-in flows for R2. Other R2 updates (such as adding submission button, brief, and assets pack for submitters on landing page, were complete during R1 discussions. They can be found here:

https://bugzilla.mozilla.org/show_bug.cgi?id=818104
(In reply to Holly Habstritt [:Habber] from comment #1)
> Attached is an updated PDF for the Submission and Sign-in flows.
> 
> There are some outstanding questions for Arcadio & team that we can discuss
> on Monday.
> 
> Copy: Matej, can you take a look at the copy for the submission screens? We
> will also need an email written confirming the posting of the user's video
> once processing is complete.

Sorry for the late reply. When do we need this copy by?
Matej, arcadio is organizing all the creative/copy tasks.
I've made updates to the R2 sign-in/submission wireframes per our last conversation on January 14th. These can also be used to help guide copy. Matej, let me know if you have any questions.
Attachment #701602 - Attachment is obsolete: true
Hi Holly,

I'm working on the copy for these screens in the individual bugs that Arcadio filed, but there are a few general things I wanted to point out that might not be captured in what I'm doing there.

• Headings and most copy should be in sentence case rather than title case. This affects things like the name and address fields, "Rules for uploading" and the "Choose a video to upload" button.

• Across the top, let's make the second one "Enter your information" so they all start with a verb.

• "Flick" and "flicks" should be capitalized if we're talking about the contest, lowercase if we're talking about individual videos.

If I think of anything else, I'll add it here.
Thanks, Matej. 

Everything you said makes sense to me. The wireframe copy is definitely FPO, so change anything you feel is necessary. 

I hadn't planned on updating the wireframes with copy changes unless absolutely necessary. If it's helpful to the designer, I can do so, but if we can make the changes directly in the implementation phase (and in a dedicated copy doc that you have control of), that would be best.
Sounds good, Holly. I'm adding Arcadio to this bug so he and I can both track all the copy changes.

Aracadio, there are some general comments in comment 7, in case you're going to be collecting all the sign-in stuff in one place.
Thanks, Matej and Holly. 

These sound good to me as well. As the copy starts to drop in I'll copy it to a word doc and share with Matej when final. 

Arcadio
Holly: There's not more R2-specific work going on, right? If so, can you close this?
Flags: needinfo?(hhabstritt.bugzilla)
Hi Mike, is there a transfer from the modal display of the submission flow to the page version happening? If so, when?

After using the submission flow I had some feedback that I haven't had a chance to make a bug for. This is feedback regarding mostly simple things like spacing in the form, placing "optional" next to Nickname field, add a "." after "Be concise, yet unique" message, etc. 

However, there is one larger issue regarding this error: http://cl.ly/image/0q2d1y061m1s

If the user submits a video that is not the right format, they get stuck at this error. This may be fixed by moving to the page by page flow instead of modal. 


Could you ping me when this design is transferred into the page by page flow so that I can check it out? It might be best that I file any bugs for you once that version is complete. I'd also like to let you know before it goes live or before your attentions goes to another project. :)
Flags: needinfo?(hhabstritt.bugzilla)
Bug 848000 covers de-modalizing the submission form. Craig's working on it, but we don't have a solid timeline yet as he's being pulled away to other work. I've CC'd you on it so you'll know when it's done and up on dev for you to walk through.

I agree that it would be better to wait until after the de-modalizing to address these so we don't duplicate work. Given that, I'll close this bug and you can file new bugs once bug 848000 is resolved. :D
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: