1862738 - Android: Language standardization for Credential Management features

Status: RESOLVED FIXED

(Firefox for Android :: General, task)

Description

[Isabella Ssozi [:isabella]]

User Problem:

Across credential management features, we are, in places, inconsistent in the terminology we use (e.g. sometimes we say “login”, and other times we say “password”). In other cases, we use terms that are imprecise—for example, credit cards to mean any card-based payment method. This is a disruptive user experience.

Goal:

We’d like to (a) use consistent terminology across features and (b) choose terms that speak to the capabilities of the features as they are built today, while leaving some flexibility for near-term changes.
Acceptance Criteria

Replace applicable strings with recommended nouns, verbs and modifiers under “Terminology recommendations” in https://docs.google.com/document/d/1HS7N-Eg1rFn-ATDOGo5vj4IYbp5LtB-RUMB0HFQq-nM/edit#heading=h.qr88jwe5d96a

Comment 1

[Isabella Ssozi [:isabella]]

Attachment: Inventory of strings

Comment 2

[Isabella Ssozi [:isabella]]

Hi team, checking in on the timing for this. Is this on track for Fx 122?

Comment 3

[Jonathan Almeida [:jonalmeida]]

Hey Emily, is this something you could provide feedback for Isabella?

Comment 4

[klower]

Hi Jonathan,
I'm the content designer working on this project. Last week, I posted this message in the Jira ticket:

For whoever picks up this ticket, wanted to make sure that this Google sheet I put together is referenced / followed for the string changes. A few notes about the sheet:

• Filter on Column A to see Android strings (this sheet captures string changes for Desktop, Android and iOS)
• Current copy is captured in Column G
• Copy to update to is Column H
• For some strings, it is noted “No changes” in column H. I kept those rows/strings in the sheet, just to have a more holistic view of the interaction and the surrounding strings.
  If you have any questions as you’re working the ticket, please let me know. Thank you!

So, I believe the next step here is to have an Android engineering resource assigned, to make the string changes in the code.

Comment 5

[Jonathan Almeida [:jonalmeida]]

Thanks klower, the doc says it's still work in progress, but if not, I'll leave this for jmahon to assign to add into the team's sprint.

Comment 6

[Joe M [:jmahon]]

Thanks for the tip, Jonathan. We don't have capacity to pick this up immediately, but it's been added to our product roadmap - given current constraints, though, we'll probably pick it up in the new year.

Comment 7

[Isabella Ssozi [:isabella]]

Hi team, for whenever this gets picked up - just wanted to flag that the "Credit Cards" option in the choose-what-to-sync UI also has to change to "Payment Methods".

Comment 8

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1862738 - Credential management string changes (#5207)

Comment 9

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1862738 - Put credential management strings before translation (#5225)

Comment 10

[BMO Github Automation]

Authored by https://github.com/sarah541
https://github.com/mozilla-mobile/firefox-android/commit/e3c4888bc6ff0eb69a97aa5b418cc317570789b3
[main] Bug 1862738 - Put credential management strings before translation

Comment 11

[Joe M [:jmahon]]

The strings landed, but because the localization team is still working on them, they're not yet actually incorporated as user-facing strings.

Re-opening this to account for the remaining work that is needed to get the newly localized strings to show up in the app.

Comment 12

[Joe M [:jmahon]]

Marking this as fix-optional for 123; if we can get everything done and uplifted before too late, we can still make 123, but we're not yet certain if the timing will work out for that.

Comment 13

[[:skhan]]

The changes got landed yesterday and should be a part of v125. Closing as fixed.