Closed Bug 588647 Opened 9 years ago Closed 9 years ago

Feedback page for Firefox Releases

Categories

(Input :: General, enhancement, P1)

enhancement

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: aakashd, Assigned: wenzel)

References

Details

Attachments

(1 file, 1 obsolete file)

Attached image general feedback page mock (obsolete) —
We've got a generic "Submit Feedback" in Firefox Releases (and betas) that we should make better use of instead of just the "sad form". Therefore, here's the plan:

We have a generic feedback page named "input.mozilla.com/feedback" that is an entry point for a user to get a number of routes:

1. "Rate Your Experience" goes to input.mozilla.com/survey
2. "Report a Broken Website" goes to input.mozilla.com/sad (its a new form)
3. "Offer an Idea for Firefox" goes to input.mozilla.com/suggestion
4. "Support page" is a hyperlink that goes to support.mozilla.com/

There is a PRD forthcoming, so more details will be located there. Before we go forward though, we'll need a sign off from Beltzner on the approach.
Depends on: 588208
Depends on: 588650
Attached image feedback mock-up
here's the correct screenshot
Attachment #467252 - Attachment is obsolete: true
wfm; gotta use those graphics, though! :)
Target Milestone: 2.0 → 2.1
Update: "Report a Broken Website" shouldn't go to our sad form, but instead go to a new form as we're going to need a new message and icon set. So, the link should be input.mozilla.com/brokensite
Target Milestone: 2.1 → 3.0
It's mock-up time!

Here are a few preliminary ideas for the feedback page, based on Aakash's wireframe. All icons are tentative.

1. A simple panel of icons, in the style of the Mozilla.com:
http://people.mozilla.com/~chowse/drop/mozilla.com/input/3.0/v1/release/01_landing.png

2. A more playful version of (1), using speech balloons:
http://people.mozilla.com/~chowse/drop/mozilla.com/input/3.0/v2/01_landing.png

3. A variation on (2), with warmer colors:
http://people.mozilla.com/~chowse/drop/mozilla.com/input/3.0/v2/02_landing_colorful.png

4. An accordion form, in the style of Fx4's in-content UI:
http://people.mozilla.com/~chowse/drop/mozilla.com/input/3.0/v2/03_landing_incontent.png

Let me know if anyone has a preference, or what qualities you like or dislike about each.
Assignee: nobody → chowse
I think the decision here is if we want this to look like the rest of the mozilla.com webspace or more like an "in product UI" feature. If the former, then let's choose #2 which carries the right type of whimsy and approachability. If the latter, then let's use #4.
Chris, can we see a variation of the simple panel of icons with the same header  in (2)?
(In reply to comment #6)
> Chris, can we see a variation of the simple panel of icons with the same header
>  in (2)?

Sure:
http://people.mozilla.com/~chowse/drop/mozilla.com/input/3.0/v2/01_landing_uncluttered.png
I'm a fan of that version, let's go with that :)
Design looks good, just a comment on the copy.  I'd prefer to change "Share your thoughts" to something more actionable ("share" seems a bit fluffy) "Submit your feedback", "Give us your feedback", "Tell us your thoughts", etc.
Hm, yeah, "share" does seem a bit off. I do like "Tell us your thoughts" though. Chris, what do you think?
(In reply to comment #10)
> Hm, yeah, "share" does seem a bit off. I do like "Tell us your thoughts"
> though. Chris, what do you think?

"Tell Us Your Thoughts" comes off a little bit creepy to me, almost interrogational. "Give Us Your Feedback" is a little commanding, too, but not too bad. "Submit Your Feedback" is neutral (if a bit clinical) and also reinforces the first action they took (clicking "Submit Feedback").

If we're going for serious vs. whimsical, I'd choose "Submit Your Feedback".
For completeness: navigating between the landing page and various feedback pages. Click on the red boxes for CSS transition goodness:

http://people.mozilla.com/~chowse/drop/mozilla.com/input/3.0/v2/transition/transition.html
I am in the process of getting this code into the app. Please ping me with any additional changes you might have, as I need to pull in these diffs by hand from now on.
Assignee: chowse → fwenzel
Do we enforce a specific user agent here somehow (i.e., the latest stable release, perhaps)? On the beta pages, we enforce the latest beta or newer (i.e., nightly).
(In reply to comment #15)
> Do we enforce a specific user agent here somehow (i.e., the latest stable
> release, perhaps)? On the beta pages, we enforce the latest beta or newer
> (i.e., nightly).

That's a really good question. I'm partial towards enforcing the latest release user agent as we can't really do anything with the data submitted on an older version of a stable release. Also, it'd be a nice security and web development win to push users toward newer versions of the browser.

I might be missing some aspects here; Christian and Beltzner, do either of you have any reservations?
This landed on master: http://github.com/fwenzel/reporter/commit/9c41019
Please file new bugs if anything needs tweaked.

The URL should be: http://input.stage.mozilla.com/feedback
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Verified this page exists- any issues will be filed separately
Status: RESOLVED → VERIFIED
Component: Input → General
Product: Webtools → Input
You need to log in before you can comment on or make changes to this bug.