1105528 - Settings Languages UX redesign

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Settings, defect)

Description

[Zibi Braniecki [:zbraniecki][:gandalf]]

For 2.3 we want to investigate redesigning Settings>Languages panel to support three new scenarios:

1) installation of additional languages available from marketplace
2) uninstallation of an installed language
3) selection of active languages and reordering to build "language fallback chain"

The preliminary vision from my team would be something like this (based on UX input from bug 1005927):

 - User clicks on Settings > Languages
 - The list of active languages opens
 - User may reorder active languages 
 - User may also click a menu option "Add/Remove languages"
 - This opens another submenu with a (long) list of available languages
   - active languages are marked with a checkbox
   - some of the languages are already on the machine, some are available from marketplace
 - The user may activate any language
 - The user may also download additional language
 - The user may also remove any of the inactive languages from the machine except of source-language (en-US in most cases)
 - We may want to display the langpack size to inform the user on how much it takes and how much he can save by removing a langpack
 - We may also want to display langpack version
 - When the users goes up to the active languages list, the new list should be available for reordering

There are many open questions:
 - does installation/selection of a new language triggers "Do you want to select this language as default?" prompt?
 - how do we mark a language being downloaded currently. Download bar, overlay?
 - what happens if download fails?
 - do we mark langpack versions and autoupdate languages from marketplace? How do we inform user about this?
 - we may want to display more information about the langpack:
    - size
    - version of the langpack
    - version of the app the langpack is for
    - how complete is the langpack (for example: "83% complete")
    - or just mark "partial langpack" vs "full langpack"
 - In the future, we will want to support langpacks per-application including third-party apps. How will that work from UX standpoint?

Comment 1

[[e-mail]]

It's found during settings bug cleaning

ni UX

Comment 2

[BMO Automation]

Firefox OS is not being worked on