1855500 - Fullpage Translations feature - Support Article Content [Android V126]

Status: VERIFIED FIXED

(support.mozilla.org :: Knowledge Base Content, task)

Description

[Usama Khan]

Did you check out the steps and FAQs for submitting requests to the CX content team?

Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content

Is the content embargoed (yes or no)? [REQUIRED]

Note: If yes, please open Advanced Fields at the top left of this ticket, and check the Confidential Mozilla Employee Bug (non-security) box found near the bottom of the page.
No

Product

Choose one below and delete others. [REQUIRED]
Firefox for Android

Select the type of request.

Choose one or more below and delete others. [REQUIRED]
New article
Update existing article
In-product link request

Please provide a summary of the request. [REQUIRED]

Fullpage Translations was launched in Firefox V118 for Desktop users. We are launching the same feature for Android users now. We need to have a relevant support article created for the Android users on how to use and access the feature on Android.

Is this an on- or off-train release? Please indicate the product version number, if applicable and add to the Summary field using the format of [Product V123]. [REQUIRED]

Firefox for Android V121

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.
December 19, 2023 - Firefox V121 Release day

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

No

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

Note: Minimum of 10 days required for translation requests.
No

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://mozilla-hub.atlassian.net/browse/FXDROID-751

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

Note: Please include final visual assets only.
https://www.figma.com/file/GT6oZLFw32LiCwKl5GOMWD/Translation?type=design&node-id=7191-52840&mode=design

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Please review the Figma file above.

Does the content need approval prior to publishing? If so, by who? [REQUIRED]

Yes, please post in #firefox-translations when the article is ready for review by the relevant stakeholders.

Comment 1

[Emily Wachowiak [:emilyw]]

Thanks, Usama! We will need a placeholder URL for Eng to use since we link to the article within the product. Is it possible to get this by October 13?

One of the main key differences between the desktop feature and the Android feature is that Android has a separate flow for when users have their device in data saver mode and are off WiFi. Look for "Data Saver mode" within the Figma for more info, but feel free to reach out to #Firefox-translations with questions.

Comment 2

[Lucas Siebert]

Hey Emily! Just checking in – did we ever create a placeholder for this content? Let me know if it's still needed and I'll take care of it.

Comment 3

[Emily Wachowiak [:emilyw]]

(In reply to Lucas Siebert from comment #2)

Hey Emily! Just checking in – did we ever create a placeholder for this content? Let me know if it's still needed and I'll take care of it.

No, I don't believe we did. Can you please generate one? Thank you! FYI the new target release is v124

Comment 4

[Lucas Siebert]

Sure, here it is:
In-product redirect: https://support.mozilla.org/1/mobile/%VERSION%/%OS%/%LOCALE%/android-translation
Placeholder article: https://support.mozilla.org/en-US/kb/android-translation

Comment 5

[Lucas Siebert]

Preliminary draft: https://docs.google.com/document/d/1Y0KazBMChMOu5_yLeBRbPBbBCf1BJP7JY5f3m3N8iMg/edit
(This isn't the final version. It still requires Android-specific instructions and screenshots, which I'll add closer to our go-live date.)

Comment 6

[Emily Wachowiak [:emilyw]]

One thing we will need to address in this article is that not all mobile devices will support translation. Unfortunately, we don't have a list of what devices these are -- generally they will be older, though. Firefox will assess whether or not the device can support translation, and if it detects that it is not supported or support is unknown, we will not show the feature at all.

So something like "Q: Why can't I access translations on my Android device? A: Not all Android devices support translation at this time."

Comment 7

[Emily Wachowiak [:emilyw]]

The release date has now moved to 126.

Comment 8

[Lucas Siebert]

(In reply to Emily Wachowiak [:emilyw] from comment #7)

The release date has now moved to 126.

Appreciate the heads-up, Emily. I've moved this task to our V126 Content Release Tracker. https://app.asana.com/0/0/1206707783424226/f

Comment 9

[SUMO Mandy]

Was this moved to V128?

Comment 10

[Olivia Hall [:olivia]]

Thanks for asking! We are doing a staged release and a release is happening in v126. Please see this Jira ticket for full details on the release waves. (The fix version is v128 because that is the final wave. We are working to reorganize these tickets to make everything more clear.)

We plan to have the core feature and page settings released via Nimbus in v126. Please let me know if you need additional information on the feature or anything else.

Comment 11

[SUMO Mandy]

(In reply to Olivia Hall [:olivia] from comment #10)

Thanks for asking! We are doing a staged release and a release is happening in v126. Please see this Jira ticket for full details on the release waves. (The fix version is v128 because that is the final wave. We are working to reorganize these tickets to make everything more clear.)

We plan to have the core feature and page settings released via Nimbus in v126. Please let me know if you need additional information on the feature or anything else.

Thanks Olivia! When should CX plan to publish this requested content? Still on track for V126?

Comment 12

[Olivia Hall [:olivia]]

Yes, thanks! Everything is on track for v126 for the core feature!

Comment 13

[Lucas Siebert]

Preliminary draft: https://docs.google.com/document/d/1xOF8uXukddYVNF6hTS8PFlOD8vgDQKB6px_ij4_q5tQ/edit#heading=h.cw31krh61jcf

Comment 14

[Emily Wachowiak [:emilyw]]

Lucas can you please grant me access to review the draft doc? Thanks

Comment 15

[Emily Wachowiak [:emilyw]]

Lucas can you please grant me access to review the draft doc? Thanks (reposting with a tag for Lucas)

Comment 16

[Lucas Siebert]

Please review the final draft at your earliest convenience. If no adjustments are needed, I plan to make it live tomorrow morning. Here’s the link: https://docs.google.com/document/d/1xOF8uXukddYVNF6hTS8PFlOD8vgDQKB6px_ij4_q5tQ/edit. Thank you!

Comment 17

[Emily Wachowiak [:emilyw]]

I just added my review comments and flagged in slack for the PM Marie-Lilas and the dev Olivia to also review. I also tagged Dasha from UX but she is traveling today, so may not get to review in time.

Comment 18

[Lucas Siebert]

The article has been published and is now available in the translation queue for contributors to begin their work.
https://support.mozilla.org/en-US/kb/android-translation

Comment 19

[Mira Lobontiu (Android QA)]

Verified as fixed on the latest Fenix Nightly 128.0a1 build from 5/15 with Google Pixel 6 (Android 14).