558914 - Provide a 'Not Updating?' survey page

Status: RESOLVED WONTFIX

(Toolkit :: Application Update, defect)

Description

[Robert Strong (they/them - no direct email)]

Display a page that provides the option to fill out a survey when the update xml specifies showSurvey="true". It should be shown when
1. When the user clicks "Never" and the update xml specifies showSurvey and
   showNeverForVersion.
2. When the user clicks "Later" and the update xml specifies showSurvey and
   does not specify showNeverForVersion.

Comment 1

[Robert Strong (they/them - no direct email)]

Attachment: sample screenshot

Comment 2

[Robert Strong (they/them - no direct email)]

Comment on attachment 438586 [details]
sample screenshot

Alex, can I get strings and layout for this page. It will only be shown when the prerequisites in comment #0 are met.

Comment 3

[Robert Strong (they/them - no direct email)]

Attachment: patch in progress

Need to finish tests before review

Comment 4

[Robert Strong (they/them - no direct email)]

Attachment: patch in progress

Comment 5

[Robert Strong (they/them - no direct email)]

Attachment: patch rev1

I still need to get strings and layout but the rest of this is done so I'd like to get it reviewed.

Comment 6

[Mike Beltzner [:beltzner, not reading bugmail]]

I actually think that we should be getting input from Ken and Blake on this, as well.

Gentlemen: the idea is that when a user declines a major update, we can have a survey presented in the updater UI. we'd need to pre-package the strings, though, so if you can let us know the questions you like to ask, that'd be great

Comment 7

[Robert Strong (they/them - no direct email)]

Agreed. btw: the placeholder text is from Ken and Blake.

If we are to backport it I would prefer to go with a link in the UI as in the screenshot and implement the ability to present a textbox in the UI later. If you would prefer to go with the text box in the UI and multiple questions we could either go with in product strings as you suggest, with a string provided by the update xml, or a combination of the two. Another question is whether we want multiple questions per survey if it is in product since there is limited room to add questions along with text boxes.

Comment 8

[Mike Beltzner [:beltzner, not reading bugmail]]

If we're backporting without strings, then I think I'd rather that the "No thanks" button just takes users to a survey page instead of showing a link.

Comment 9

[Robert Strong (they/them - no direct email)]

That works for me. It will only do so when the update xml contains showSurvey so I think it should also do this when later is pressed and the update xml doesn't specify that the "No thanks" button should be displayed since if you don't want it to then showSurvey shouldn't be specified.

So I understand what you want (I know Blake wants the survey itself to be in product) can I get feedback on the other questions in comment #7? Thanks

Comment 10

[Mike Beltzner [:beltzner, not reading bugmail]]

(In reply to comment #7)
> could either go with in product strings as you suggest, with a string provided
> by the update xml, or a combination of the two. Another question is whether we
> want multiple questions per survey if it is in product since there is limited
> room to add questions along with text boxes.

I think we want a standard set of questions from Blake and Ken, and then the ability to add one with update.xml; I suspect that will be rarely used, as the l10n community isn't set up to submit their translations in a way, and the build team isn't set up to build the XML snippets that way, but it's a nice ability to have it.

(In reply to comment #9)
> That works for me. It will only do so when the update xml contains showSurvey

Yup, understood.

> so I think it should also do this when later is pressed and the update xml
> doesn't specify that the "No thanks" button should be displayed since if you
> don't want it to then showSurvey shouldn't be specified.

You mean on a minor update (where option is "OK" or "Later")?

> So I understand what you want (I know Blake wants the survey itself to be in
> product) can I get feedback on the other questions in comment #7? Thanks

Done!

Comment 11

[Robert Strong (they/them - no direct email)]

(In reply to comment #10)
> (In reply to comment #7)
> > could either go with in product strings as you suggest, with a string provided
> > by the update xml, or a combination of the two. Another question is whether we
> > want multiple questions per survey if it is in product since there is limited
> > room to add questions along with text boxes.
> 
> I think we want a standard set of questions from Blake and Ken, and then the
> ability to add one with update.xml; I suspect that will be rarely used, as the
> l10n community isn't set up to submit their translations in a way, and the
> build team isn't set up to build the XML snippets that way, but it's a nice
> ability to have it.
Will figure out how best to implement.

> > so I think it should also do this when later is pressed and the update xml
> > doesn't specify that the "No thanks" button should be displayed since if you
> > don't want it to then showSurvey shouldn't be specified.
> 
> You mean on a minor update (where option is "OK" or "Later")?
Yes, it is configurable only shown when the app's update xml states it should be shown.

> > So I understand what you want (I know Blake wants the survey itself to be in
> > product) can I get feedback on the other questions in comment #7? Thanks
> 
> Done!
Thanks!

Comment 12

[Robert Strong (they/them - no direct email)]

(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #7)
>...
> > > so I think it should also do this when later is pressed and the update xml
> > > doesn't specify that the "No thanks" button should be displayed since if you
> > > don't want it to then showSurvey shouldn't be specified.
> > 
> > You mean on a minor update (where option is "OK" or "Later")?
> Yes, it is configurable only shown when the app's update xml states it should
> be shown.
I really should have been more specific. The tie between major / minor and whether to show the "No Thanks" button has been removed and the "No Thanks" button will only be shown when the update xml has showNeverForVersion="true". One reason for this is that major / minor are also tied into which update to display and another is that this provides more flexibility for applications vs. always showing the "No Thanks" button for major updates where an app may not want to provide the "No Thanks" option for a major update.

Comment 13

[Alex Faaborg [:faaborg] (Firefox UX)]

Comment on attachment 438586 [details]
sample screenshot

We need to either load a tab with the survey and close the window, or embed the survey in the window.  having a two step process (click no thanks, click survey) is going to significantly cut down on the response rate and is a bit too much work for busy users.

Comment 14

[Robert Strong (they/them - no direct email)]

So, the proposal as outlined in comment #8 for backporting will be to open the survey page when clicking the "No Thanks" or "Ask Later" button when showSurvey is present.

The trunk patch which will happen after the patch that can be backported will be implemented per comment #10 with the survey in the UI and needs strings from Blake and Ken.

Comment 15

[ken kovash]

(In reply to comment #10) 
> I think we want a standard set of questions from Blake and Ken, and then the
> ability to add one with update.xml; I suspect that will be rarely used, as the
> l10n community isn't set up to submit their translations in a way, and the
> build team isn't set up to build the XML snippets that way, but it's a nice
> ability to have it.

Can we use what's here -- http://www.mozilla.com/en-US/firefox/mu-survey/ -- as the standard set of questions?

Comment 16

[Robert Strong (they/them - no direct email)]

Ken, did you find from the previous surveys that any of the pre-existing choices could / should be removed or that any new choices should be added based on the responses that chose "Other reason"?

Comment 17

[Robert Strong (they/them - no direct email)]

Attachment: screenshot using text from survey web page

To get an idea of what this will look like and how it will display with different screen resolutions I threw a page together using the text from the existing survey web page. Increasing my DPI to 150% shows that the content won't fit in the UI. :(

Comment 18

[Robert Strong (they/them - no direct email)]

Comment on attachment 441066 [details]
screenshot using text from survey web page

Ken, though the UI is much larger than previously it isn't large enough for the number of existing questions as can be seen in the screenshots. Asking you for feedback review so you can come up with fewer questions and possibly shorten a couple of the informational strings as well. Thanks

Comment 19

[ken kovash]

How about a one question survey?  Virtually all of our insights come from the "other" option in question #1 and from the open ended feedback in question #2.

"We're sorry you don't want to update to Firefox 3.6.  Please comment in the box below to help us understand why you're choosing not to update.

Tell us why you aren't upgrading to Firefox 3.6... for example: add-ons support, crashes, upgrade problems, performance issues (speed, memory), still very much satisfied with prior version.  Please leave any specific details related to your experience.

[comment box here]"

Comment 20

[Robert Strong (they/them - no direct email)]

That will work MUCH better! Thanks

Comment 21

[Robert Strong (they/them - no direct email)]

Now that we have test pilot I am wontfixing this in favor of having a single utility add-on for gathering user data instead of creating one-off's in the app.