1128577 - Firefox OS language picker changes for MWC

Status: RESOLVED WONTFIX

(www.mozilla.org :: Bedrock, defect)

Description

[Mike Alexis [:malexis]]

Filing this bug as a placeholder for discussing whether the language picker needs to be rebuilt or updated. 

What improvements, if any, can we make in time for MWC March 1?

original work done here: https://bugzilla.mozilla.org/show_bug.cgi?id=1037239

Comment 1

[Mike Alexis [:malexis]]

Notes from requirements meeting:

https://etherpad.mozilla.org/fx-os-language-selector-2015-02-04

Comment 2

[Alex Gibson [:agibson]]

I will attempt to recap where we ended up in the last meeting. If any of this is incomplete or incorrect, anyone please feel free to follow up:

On the redesigned page, Geo-Location will be required for the following two reasons:

1.) to show the green "Buy a phone" CTA button (as per the existing page).
2.) to show the appropriate phone graphics in the middle section of the new page.

To determine the users geographical location, we have two options:

1.) Use GeoDude [1] on the client (as per the current page) to hide/show appropriate content.
2.) Determine location on the server side and redirect the user to the appropriate page.

Consensus was that we probably don't have time for 2.) before MWC is here, so 1.) is probably the most realistic choice for now.

Other notes:

- The middle section of the page will feature different phone visuals for the OS versions available. Which OS gets shown is dependent on the users geographical location.

- For areas where more than one phone/OS version is available, the page will always default to showing the most up-to-date phone visuals.

- There will be no additional requirements to show any other software/hardware differences for individual countries (e.g. dual-sim in India). This will help simplify things.

- We should show the latest OS version by default for users with JS disabled.

- Try to progressively enhance for those with JS enabled to show the most appropriate visuals.

- It was also noted that it might be nice to still offer users a way to select their location like on the devices page [2], instead of making assumptions about what the user is there to find out.

[1] https://github.com/mozilla/geodude
[2] https://www.mozilla.org/en-US/firefox/os/devices/

Comment 3

[Jennifer Bertsch [:jbertsch]]

Thanks for this summary, Alex.

An update on requirements:

1.  We continue to need to "show the green "Buy a phone" CTA button (as per the existing page)" 

2.  For launch on March 1, we have reduced the scope to only show graphics for the 2.0 version regardless of location.  However, as of today, we are continuing to scope out showing the 1.1, 1.3, and 1.4 versions at a later date.  This may change.

3.  We do continue to need to show the language picker for India where we want to let people know the phone is available in languages different from their browser locale, but images won't change.

Comment 4

[Jonathan Petto [:jpetto]]

(In reply to Jennifer Bertsch [:jbertsch] from comment #3)
> 3.  We do continue to need to show the language picker for India where we
> want to let people know the phone is available in languages different from
> their browser locale, but images won't change.

What will this language picker change? Will it just redirect to an alternate locale version of the same page? Wouldn't an available country picker (like we currently have on the devices page) visible to all users (regardless of locale/build) be a more scalable solution?

Comment 5

[Alex Gibson [:agibson]]

(In reply to Jon Petto [:jpetto] from comment #4)
> (In reply to Jennifer Bertsch [:jbertsch] from comment #3)
> > 3.  We do continue to need to show the language picker for India where we
> > want to let people know the phone is available in languages different from
> > their browser locale, but images won't change.
> 
> What will this language picker change? Will it just redirect to an alternate
> locale version of the same page? Wouldn't an available country picker (like
> we currently have on the devices page) visible to all users (regardless of
> locale/build) be a more scalable solution?

+1 to this if it's a viable option. I think it makes more sense to present a language picker to all locale pages, as country specific UI/logic is going to be less maintainable much like what we have now.

Comment 6

[Jennifer Bertsch [:jbertsch]]

(In reply to Alex Gibson [:agibson] from comment #5)
> (In reply to Jon Petto [:jpetto] from comment #4)
> > (In reply to Jennifer Bertsch [:jbertsch] from comment #3)
> > > 3.  We do continue to need to show the language picker for India where we
> > > want to let people know the phone is available in languages different from
> > > their browser locale, but images won't change.
> > 
> > What will this language picker change? Will it just redirect to an alternate
> > locale version of the same page? Wouldn't an available country picker (like
> > we currently have on the devices page) visible to all users (regardless of
> > locale/build) be a more scalable solution?
> 
> +1 to this if it's a viable option. I think it makes more sense to present a
> language picker to all locale pages, as country specific UI/logic is going
> to be less maintainable much like what we have now.

Thanks, Jon and Alex!

If the use case is "let visitors to the /firefox/os page in India know that the phone is available in 3 languages in their country," what would you think about handling that with conditional copy on the page rather than the language picker?

Comment 7

[Jonathan Petto [:jpetto]]

It would be great if we could make this kind of condition somewhat generic/maintainable. For example, if we could have an array of locales that get a common "Firefox OS is available in multiple languages in your country" message, that's much better than writing copy and code every time this situation comes up.

Is that a possibility?

Comment 8

[Jennifer Bertsch [:jbertsch]]

After great discussion, we are closing this as out of scope for the 2015 redesign of this page.