Closed Bug 986071 Opened 10 years ago Closed 10 years ago

ux work for choose-your-product page

Categories

(Input Graveyard :: Submission, defect, P1)

Product:
Input Graveyard
Component:
Submission
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2014Q2

People

(Reporter: willkg, Assigned: espressive)

References

Details

(Whiteboard: u=user c=feedback p= s=input.2014q2) 

We need to do some UX/UI work for the choose-your-product page.

In the future, when someone goes to /feedback/, we'll greet them with a product picker page which has links for all the products we're collecting feedback for allowing them to go to a product url to leave feedback for that specific product.

I have a stub page at https://input.mozilla.org/cyoa/ (which somehow isn't working right now, probably because of a height thing) which we can enhance and when the time comes to do a product picker on /feedback/, we can swap it in.
Fix for the cyoa page landed in master: https://github.com/mozilla/fjord/commit/126bd8c

Pushed to prod just now.
Making this a tracker for 2014q2.
Summary: ux work for choose-your-product page → [tracker] ux work for choose-your-product page
Target Milestone: --- → 2014Q2
Schalk: Laura said you might be able to lend some time to UX/UI work for Input this quarter. If you have some time, I sure could use some help on this one.
(In reply to Will Kahn-Greene [:willkg] from comment #4)
> Schalk: Laura said you might be able to lend some time to UX/UI work for
> Input this quarter. If you have some time, I sure could use some help on
> this one.

Sure thing, let me have a look.
Awesome! I'm noticing this bug is sort of bereft of some important details. I'll flesh it out on Monday. Things like "how many products are we talking about?" and "what resolutions are we targeting?" and all that.

Schalk: If there are other questions you want answered, let me know.
(In reply to Will Kahn-Greene [:willkg] from comment #6)
> Awesome! I'm noticing this bug is sort of bereft of some important details.
> I'll flesh it out on Monday. Things like "how many products are we talking
> about?" and "what resolutions are we targeting?" and all that.
> 
> Schalk: If there are other questions you want answered, let me know.

Hey Will,

For now, I will await the flesh and ask my questions after ;)

Thanks
Thank you for replying--I forgot to do this yesterday amidst all the crazy.

Right now we have 4 products, but we'll be adding some more. I think we should design it for 5 with an upper bound of 10 with the expectation that if we hit 10, we can fix it then.

We have people using desktop and mobile devices. Currently we have one feedback page that covers everyone in a "it works, but it's not the best thing ever" kind of way. It'd be nice if we could have one product-picker page that works for desktop and mobile devices, too, but we do have the infrastructure for doing a desktop template and a mobile template.

I think we should use Firefox OS devices as the minimum resolution target at 320x480.

I'd like to use images and text to denote products like SUMO <https://support.mozilla.org/> does. We can probably re-use their images, too.

That's everything I can think of.

Does that cover everything?
(In reply to Will Kahn-Greene [:willkg] from comment #8)
> Thank you for replying--I forgot to do this yesterday amidst all the crazy.
> Currently we have one feedback page that covers everyone in a "it works, but it's not the best
> thing ever" kind of way.

So, the current page you are referring to is https://input.mozilla.org/en-US/feedback/
Assignee: nobody → schalk.neethling.bugs
Sort of.

I have a stub page here: https://input.mozilla.org/cyoa/

So, we should do the work there. Then when we can slide that into /feedback/, we'll do that part then.
(In reply to Will Kahn-Greene [:willkg] from comment #10)
> Sort of.
> 
> I have a stub page here: https://input.mozilla.org/cyoa/
> 
> So, we should do the work there. Then when we can slide that into
> /feedback/, we'll do that part then.

What is the browser support requirements for input.m.o?
Flags: needinfo?(rrosario)
(In reply to Schalk Neethling [:espressive] from comment #11)
> What is the browser support requirements for input.m.o?

Hey Schalk! I was about to update the sumo requirements yesterday and we should just use the same on input:
https://wiki.mozilla.org/Support/Browser_Support

I'll update it today, but it is mostly correct. A grade for the latest two versions of major browsers and IE9+. Others dont need to be pixel perfect, but they should work. I dont think this page should have any problems though, right? It shouldn't have too much bleeding edge fancy?
Flags: needinfo?(rrosario)
(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #12)
> (In reply to Schalk Neethling [:espressive] from comment #11)
> > What is the browser support requirements for input.m.o?
> 
> Hey Schalk! I was about to update the sumo requirements yesterday and we
> should just use the same on input:
> https://wiki.mozilla.org/Support/Browser_Support
> 
> I'll update it today, but it is mostly correct. A grade for the latest two
> versions of major browsers and IE9+. Others dont need to be pixel perfect,
> but they should work. I dont think this page should have any problems
> though, right? It shouldn't have too much bleeding edge fancy?

Thanks Ricky! No, I just wanted to make sure I test it in all the relevant versions.
Changing metadata so this is no longer a tracker and it's a bug in the 2014q2 sprint.
Priority: -- → P1
Summary: [tracker] ux work for choose-your-product page → ux work for choose-your-product page
Whiteboard: u=user c=feedback p= s=input.2014q2
In a PR: https://github.com/mozilla/fjord/pull/266

Landed in master: https://github.com/mozilla/fjord/commit/dd33599

Waiting until monday after release week to push out.
Pushed this to production today. Whee!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.