1210861 - Provide better UI for older versions of supported browsers

Status: RESOLVED INCOMPLETE

(Hello (Loop) :: Client, defect, P2)

Description

[Mark Banner (:standard8)]

Attachment: Current unsupported browser message

Currently if the user hits an older version of Firefox or Chrome that isn't supported we display "Firefox Hello only works in browsers that support WebRTC" (see attached screenshot).

We need to update the sdk to the latest version soon, however, this will stop support for older than Fx38 or Chrome 43. Hence, the message doesn't feel quite right.

Therefore I think we should have a different message if you're using a supported browser, but its just out of date.

Comment 1

[Mark Banner (:standard8)]

Sevaan, can you provide a new string or something here? I think the new layout should wait until a different bug at some stage.

Comment 2

[:shell escalante]

adding Matej for string as well - I think i saw a UX from Sevaan at some point for this with possibly a new string - please verify.

Comment 3

[Matej Novak [:matej]]

(In reply to :shell escalante from comment #2)
> adding Matej for string as well - I think i saw a UX from Sevaan at some
> point for this with possibly a new string - please verify.

I don't recall, but if there is anything, I'm happy to review. I'll look for it in this bug.

Comment 4

[Sevaan Franks [:sevaan]]

I believe Gareth performed some Optimizely tests on this, so he would have the new strings. Gareth, could you provide a link to the options?

Comment 5

[Gareth Cull [:garethc]]

Hey Guys,

Here is a link to the final results for this test we ran among these users. We saw improvement in download conversion across all variations we ran, with the winning variation #1 significantly improving conversions by 166%!

I'd recommend implementing variation 1 for the time being. We should revisit testing this experience in the future to coincide with new changes to the product.
 
https://mana.mozilla.org/wiki/display/FIREFOX/Hello+Unsupported+Browsers+Conversion+Experiment

Gareth

Comment 6

[Mark Banner (:standard8)]

Sevaan, unfortunately those variations don't cover the case where the user already has Firefox, but it needs an update.

Can you mock something up, and then we'll work out how to get it implemented?

Comment 7

[Sevaan Franks [:sevaan]]

Pau will be working on this bug.

Comment 8

[Pau Masiá [:Pau]]

Hey guys, I'll help with this bug but first, I'd need access to that test results Gareth mentions or, at least, know which variation is #1, please.

Comment 9

[Pau Masiá [:Pau]]

To clarify, is this bug for wording only or something else is needed?

Comment 10

[Sevaan Franks [:sevaan]]

Info sent to Pau.

Comment 11

[Pau Masiá [:Pau]]

Attachment: Browser_OutdatedVersion.png

My suggestion per this bug.
Matej, please, could you review if the copy makes sense to you?
Thanks!

Comment 12

[Matej Novak [:matej]]

(In reply to Pau Masiá [:Pau] from comment #11)
> Created attachment 8681839 [details]
> Browser_OutdatedVersion.png
> 
> My suggestion per this bug.
> Matej, please, could you review if the copy makes sense to you?
> Thanks!

A few things:

• I worry that having the first sentence coming off the wordmark may be a challenge for l10n. I think we should make that a complete thought separate from the wordmark: 

"Hello is not supported by this version of your browser."


• Since we're moving towards talking more about sharing than speaking, I think we can simplify that second line:

"Update your browser to start sharing the Web with your friends. Learn more."


• Looking at other buttons in Hello, I think it should be in sentence case. I would also remove the exclamation mark:

"Update now"


Thanks.

Comment 13

[Pau Masiá [:Pau]]

(In reply to Matej Novak [:matej] from comment #12)

> 
> • I worry that having the first sentence coming off the wordmark may be a
> challenge for l10n. I think we should make that a complete thought separate
> from the wordmark: 
> 

I'm not quite sure I understand the challenge for l10n here...Could you be more specific please?

Comment 14

[Matej Novak [:matej]]

(In reply to Pau Masiá [:Pau] from comment #13)
> (In reply to Matej Novak [:matej] from comment #12)
> 
> > 
> > • I worry that having the first sentence coming off the wordmark may be a
> > challenge for l10n. I think we should make that a complete thought separate
> > from the wordmark: 
> > 
> 
> I'm not quite sure I understand the challenge for l10n here...Could you be
> more specific please?

Not all languages would keep the words in the same order, so having Firefox Hello as a wordmark at the beginning and then starting the line with "…is not supported…" may not work in all locales.

Regardless of that, I also don't like using wordmarks in sentences (vs. live text), as a matter of brand and style. Can we go with what I suggested in comment 12?

Comment 15

[Pau Masiá [:Pau]]

Attachment: Browser_OutdatedVersion.png

Hi Matej, I think it worked well your suggestion. Please, take a look at it to make the final strings review.

Thanks!

Comment 16

[Matej Novak [:matej]]

(In reply to Pau Masiá [:Pau] from comment #15)
> Created attachment 8682985 [details]
> Browser_OutdatedVersion.png
> 
> Hi Matej, I think it worked well your suggestion. Please, take a look at it
> to make the final strings review.
> 
> Thanks!

Looks great, but the button still says "Update Now" instead of "Update now." Is that the correct format?

Comment 17

[Pau Masiá [:Pau]]

Attachment: Browser_OutdatedVersion.png

You're totally right ;)

I guess this is done.

Comment 18

[Mark Banner (:standard8)]

Sevaan/Pau: This needs further definition for what happens when the update now button is pressed. We're going to have to deal with non-Firefox browsers here as well as Firefox, so we're going to need something for all of those. We won't have privs for non-Firefox, so we won't be able to put up update dialogs or anything.

Maybe it would be simpler to just say to update the browser? or link to support pages?

Comment 19

[Sevaan Franks [:sevaan]]

(In reply to Mark Banner (:standard8) from comment #18)
> Sevaan/Pau: This needs further definition for what happens when the update
> now button is pressed. We're going to have to deal with non-Firefox browsers
> here as well as Firefox, so we're going to need something for all of those.
> We won't have privs for non-Firefox, so we won't be able to put up update
> dialogs or anything.
> 
> Maybe it would be simpler to just say to update the browser? or link to
> support pages?

A quick chat with :verdi and a look at Bug 998962 suggests that it is not possible to force an update by clicking the button. It may just have to link to https://www.mozilla.org/firefox/new

For other browsers, maybe the messaging should change to something like "Update your browser or download the latest Firefox" and the button also goes to the Firefox download page.

Comment 20

[Pau Masiá [:Pau]]

In other browsers we will need to stick to what is feasible so, as Mark says, it's simpler to say to update the browser and users will know what to do. 

In Firefox, though, can't we manage to trigger the menu or the preferences panel where users can click to update their browser?

It seems a bit odd to point users to the download page if they already have Firefox Installed.

Comment 21

[Mark Banner (:standard8)]

(In reply to Pau Masiá [:Pau] from comment #20)
> In Firefox, though, can't we manage to trigger the menu or the preferences
> panel where users can click to update their browser?
> 
> It seems a bit odd to point users to the download page if they already have
> Firefox Installed.

We're in the content process rather than a privileged one. I don't think there would be an issue punching through like we do for opening a rooms, but we'd need to talk to a few people to check security issues, and to work out the best way to do it (e.g. it used to be that not all users could update, I don't know if that's still true).

Hence, if we want to do that, I'd like to split it out to a different bug, and just use this one to implement the "basic" option.

Comment 22

[Pau Masiá [:Pau]]

(In reply to Mark Banner (:standard8) from comment #21)
> (In reply to Pau Masiá [:Pau] from comment #20)
> > In Firefox, though, can't we manage to trigger the menu or the preferences
> > panel where users can click to update their browser?
> > 
> > It seems a bit odd to point users to the download page if they already have
> > Firefox Installed.
> 
> We're in the content process rather than a privileged one. I don't think
> there would be an issue punching through like we do for opening a rooms, but
> we'd need to talk to a few people to check security issues, and to work out
> the best way to do it (e.g. it used to be that not all users could update, I
> don't know if that's still true).
> 
> Hence, if we want to do that, I'd like to split it out to a different bug,
> and just use this one to implement the "basic" option.

Agree. Let's implement the basic option and try to provide a better experience in a follow-up bug.

Comment 23

[Mark Banner (:standard8)]

Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.