1862264 - UI Integration Managing States

Status: RESOLVED FIXED

(Firefox for Android :: Translations, task, P3)

Description

[Olivia Hall [:olivia]]

Translations has many states we need to think about for showing UI. (See more at Figma.)

The purpose of this bug is to reflect on the current logic, name all states we have, and name what screen should be shown.

This may end up being more of a research bug than actionable bug, but is important for ensuring integration can proceed more orderly.

Comment 1

[Olivia Hall [:olivia]]

Translations:

• First Run
• Standard Run

Translations States:

• Initial - no action taken
• Pre-translate - user has signaled a translation
  • In low-data + off WiFi mode, show warning
• Translating - user has signaled a translation and it has began
• Translated - translation completed

Translations Error States:

• General Error
  • Any issue occurs
• Couldn't Load Languages
  • Could not load drop-downs
• Language not supported
  • Drop-downs are populated, but the page detected language is not an option in the drop-down

Settings:

• Page settings
  • Global Offer Setting
  • Language Setting
  • Site Setting
• Global Settings
  • Global Offer Setting
  • Data saving mode setting
  • Automatic translation for languages
  • List of sites to never translate
  • Download language model settings
    • Has a data saver popup

Comment 2

[Olivia Hall [:olivia]]

Error states are defined in AC here:
Bug 1862263

Comment 3

[Olivia Hall [:olivia]]

• Plan on creating a TranslationsDataCoordinator to handle translation store data queries and data preparation that implements TranslationsStore.
• Plan on creating a TranslationsRequestInteractor to handle translation requests that implements TranslationsInteractor.

(Names need some more thought.)

Fenix/AC Architecture links for later reference:

• Architecture
• Readme

Comment 4

[Olivia Hall [:olivia]]

Should have enough information to continue, resolving this bug, but will possibly add more notes and ideas to it.