916970 - Change - Add an appropriate bookmark for feedback on metro Aurora

Status: RESOLVED WONTFIX

(Firefox for Metro Graveyard :: General, defect)

Description

[Allison Naaktgeboren :ally]

a low touch low risk way to direct users to leave us feed back: a defualt bookmark that points to a sumo feedback page or bugzilla.

discussed in team meeting today, Asa needs to check that on correct endpoints and expectations.

Comment 1

[Asa Dotzler [:asa]]

Matthew, Michael, do either of you two know how we could best gather Metro feedback? I'd suggested we have a default bookmark that points to Input.  Is that reasonable?  If so, what URL should we use. If not, do you have other suggestions?

Comment 2

[Verdi [:verdi] Best to slack me]

A bookmark could work. Desktop Firefox has the link in the help menu. I would think the regular input link would work https://input.mozilla.org/feedback but it doesn't look like we have a way to distinguish metro from desktop. Here's one that I submitted https://input.mozilla.org/en-US/dashboard/response/4008739

Comment 3

[Matt Grimes [:Matt_G]]

I think a bookmark link to Input is a great idea. I might be able to get a new product created as well so that we can distinguish feedback more effectively. I'll talk to Will about that tomorrow. Input will gather the best organic feedback, but I'd also like to be able to do targeted surveys as well. 

Asa: What other vehicles do we have? Is there any chance of having a doorhanger or something similar that we can use to sample a % of users and offer them a targeted survey based around a specific feature or problem we are investigating?

Comment 4

[Will Kahn-Greene [:willkg] ET needinfo? me]

(In reply to Verdi [:verdi] from comment #2)
> A bookmark could work. Desktop Firefox has the link in the help menu. I
> would think the regular input link would work
> https://input.mozilla.org/feedback but it doesn't look like we have a way to
> distinguish metro from desktop. Here's one that I submitted
> https://input.mozilla.org/en-US/dashboard/response/4008739

Sounds like the code needs some tweaking to work correctly. I looked at Verdi's feedback response and the user agent looks like this:

Mozilla/5.0 (Windows NT 6.2; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0

There's nothing I can key off of there to know it's Firefox on Metro, so we're going to need a product-specific route. Then we could use a url like this and know exactly what we're looking at:

https://input.mozilla.org/%LOCALE%/feedback/%PRODUCT%/%CHANNEL%/%VERSION%/

Input doesn't support that, yet. That's covered in bug #857056 which probably needs a better title.

I don't own a device with Metro on it. So in order to help here, I need to get a device or a simulator or an emulator or someone else needs to do the testing work. Getting a device/simulator/emulator is a lot easier and then we'd have a device for SUMO development, too. I don't really have a preference. What options do we have here?