1345952 - [Focus Android] Set up the app in stores_l10n

Status: RESOLVED FIXED

(Mozilla Localizations :: Other, enhancement)

Description

[Delphine Lebédel [:delphine - OOO]]

(Wasn't too sure where to file this as there is no Focus for Android Product section on bugzilla, as far as I can tell. Please feel free to move)

Since Focus for Android is a brand new project, we're going to have to set it up on stores_l10n. In order to do this, we will need to know what kind of content is going to be present.

At this point, we know we will have a description (one liner) to localize and screenshots for the app to localize and test too.

During the Focus meeting it was mentioned there were going to be no keywords - are we sure about this?

Since this is a v1, there will be no What's New to localize this time around. We will need those for future versions. 

@flod: please add anything I may have forgotten here that you need in order to set this up

thanks all!

Comment 1

[Francesco Lodolo [:flod]]

I think this covers pretty much everything. I would honestly be surprised to not have keywords, we have them for all iOS and Android projects.

Also, I noticed that we have a "Short Description" and a "Description" on Android, they have different length constraints.

We'll need clear deadline, as in when screenshot text is needed, when screenshots will be available for QA, etc.

Team should also figure out if they can automated publishing this information (releng is currently doing it for Firefox).

Comment 2

[Francesco Lodolo [:flod]]

Store length limits
https://github.com/mozilla-l10n/stores_l10n/blob/5db4de5069b1463f693181cbe39843cddbb34127/app/inc/constants.php#L16-L22

Comment 3

[Delphine Lebédel [:delphine - OOO]]

Deadline for getting most of this content in is March 17th (Fabio, please correct me if I'm wrong!).

Mike did mention that for screenshots we usually get these closer to release date - which is said to be on April 6th. But in any case and as you mention Flod, we still do need to know quickly what those dates will be for screenshots. 

We also need to make sure we have enough time to go back and forth with the designer and localizers so they can sign-off on their final work. I've mentioned 2 weeks during the meeting - if that timeline is unrealistic let's make sure we define the new one now.

All the corresponding bugs should be filed for these pieces (so, translation of content and screenshots) as we move forwards, with deadlines and content each time in the bug.

Fabio: we'll wait for your feedback on comment 1, as well as mine here, before moving on with this :) thanks!

Comment 4

[Fabio Rios [:frios]]

Attachment: these are the current ios screenshot - android to follow.PNG

Hey all, 

In terms of strings, I want to re-use what we have from iOS on both screenshots and app store detail, so the existing copy will work. Since this was previously translated for iOS, I just need to validate that we have it in all the necessary locales. Delphine do you have the list? I can check with Product team tomorrow.

New strings:
As you've already mentioned, we need a "short description" (80 characters). I will add this to the bug tomorrow.

I'd like to add one screenshot to explain the small app size. I will provide the string tomorrow as well.

Need by date: Does March 27th work for the new strings?

Comment 5

[Delphine Lebédel [:delphine - OOO]]

(In reply to Fabio Rios [:frios] from comment #4)
> Created attachment 8848330 [details]
> these are the current ios screenshot - android to follow.PNG
> 
> Hey all, 
> 
> In terms of strings, I want to re-use what we have from iOS on both
> screenshots and app store detail, so the existing copy will work. Since this
> was previously translated for iOS, I just need to validate that we have it
> in all the necessary locales. Delphine do you have the list? I can check
> with Product team tomorrow.

Thanks for this update Fabio. Here is the dashboard for the Focus iOS store release (excluding screenshots): https://l10n.mozilla-community.org/stores_l10n/#focus_ios_release

So to recap, the most recent list of locales completed for Focus iOS store content were: German, en-US, Spanish from Spain (es-ES), French, Indonesian, Italian, Japanese, Korean, Norwegian, Dutch, Portuguese Brazil (pt-BR), Portuguese Portugal (pt-PT), Russian (ru), Swedish (sv-SE), Turkish, Simplified Chinese, Traditional Chinese.

This means we should already have content for all of the above.

But in any case on our side we need to enable these strings in our translation tools specifically for Focus Android. Note that since it's an opt-in project there may be additional locales who want to opt-in. Also, Play Store supports way more locales than App Store - so we may get much more content here than previously on iOS.

The final locale coverage list I can get out to you on deadline day Fabio - our dashboards will reflect completion for this anyways, once they are set up (will post here once it's up). 

Fabio: just let us know what the priority locales are so we make sure they are covered, and we will let you know which other ones are ready and can be added as well at the deadline.

Flod: are you missing anything here at this point to set things up?

> 
> New strings:
> As you've already mentioned, we need a "short description" (80 characters).
> I will add this to the bug tomorrow.
> 
Ok thanks, we'll be keeping an eye out today then for this. Flod needs this too to set up things on our side.

> I'd like to add one screenshot to explain the small app size. I will provide
> the string tomorrow as well.
> 
Good - when you have this Fabio, can you please file a bug blocking this one (same product/component in bugzilla should be fine)?

In the bug we'll need to know the languages we need for screenshot translation (since these are only usually a subset from our main list). We'll also need to know when when the screenshots will be available for review and when the testing cycle on them ends.

To give you an idea, typically this is the screenshot l10N QA cycle: localizers get the string (and have an en-US screenshot as reference) > localizers translate > the designer provides now localized screenshots > localizer reviews them and realizes there are errors > designer needs to update screenshots > localizers reviews work again > either good to sign-off, or needs repeat. All this happens on bugzilla. I'll attach all the corresponding localization bugs to the main one you open for the screenshots, Fabio.

> Need by date: Does March 27th work for the new strings?
We need to act quickly. If we get all the information needed above (+ clarity on the keywords), then I think this maybe could work. But we'd need to get all this in today - and before EOD because that's the same as Monday for us in the end ;)
Does the initial deadline of April 6th, that we have agreed upon earlier, not work anymore? That would probably be more realistic if we don't get content before EOD. 
Thanks!

Comment 6

[Francesco Lodolo [:flod]]

(In reply to Delphine Lebédel [:delphine - use Need Info] from comment #5)
> Flod: are you missing anything here at this point to set things up?

No, this sums up the situation correctly.

> In the bug we'll need to know the languages we need for screenshot
> translation (since these are only usually a subset from our main list).
> We'll also need to know when when the screenshots will be available for
> review and when the testing cycle on them ends.

For iOS we did screenshots for: de, es-ES, fr, id, it, ja, pt-BR, ru, zh-CN.

My plan was to set up Focus for Android like the iOS version, and copy content over. If we end up with a different list of locales, things might get a bit more complicated.

I'm also curious to understand if someone looked in automating store updates, because doing it manually is going to be long and painful.

Comment 7

[Delphine Lebédel [:delphine - OOO]]

(In reply to Delphine Lebédel [:delphine - use Need Info] from comment #5)
> Does the initial deadline of April 6th, that we have agreed upon earlier,
> not work anymore? That would probably be more realistic if we don't get
> content before EOD. 
> Thanks!

I realize we said +2 weeks after string freeze, which brings us to March 31 - not April 6 :) Sorry for the confusion!

Comment 8

[Fabio Rios [:frios]]

(In reply to Delphine Lebédel [:delphine - use Need Info] from comment #7)
> (In reply to Delphine Lebédel [:delphine - use Need Info] from comment #5)
> > Does the initial deadline of April 6th, that we have agreed upon earlier,
> > not work anymore? That would probably be more realistic if we don't get
> > content before EOD. 
> > Thanks!
> 
> I realize we said +2 weeks after string freeze, which brings us to March 31
> - not April 6 :) Sorry for the confusion!

Delphine, Flod, we've got the short description string below. Note that our limit is 80 characters, so I've included shorter versions for locales that need extra space. March 31st for these is fine. Thank you!


Get The Privacy Browser. Fast & always private from Firefox, a browser you trust

OR

Get The Privacy Browser. Fast & always private, from a brand you trust

OR

Get The Privacy Browser. Fast & always private, from Firefox

Comment 9

[Francesco Lodolo [:flod]]

(In reply to Francesco Lodolo [:flod] from comment #1)
> I think this covers pretty much everything. I would honestly be surprised to
> not have keywords, we have them for all iOS and Android projects.

Not sure where I checked before writing this, but we don't have keywords on Android projects, only iOS. Sorry for the confusion
https://l10n.mozilla-community.org/stores_l10n/locale/en-US/fx_android/release/

Comment 10

[Francesco Lodolo [:flod]]

Found another issue while setting things up: the main application title for Android has a maximum length of 30 characters.

On iOS it's currently "Firefox Focus: The privacy browser" (34 characters). English is too long, and there's no way we can translate that.

Comment 11

[Fabio Rios [:frios]]

(In reply to Francesco Lodolo [:flod] from comment #10)
> Found another issue while setting things up: the main application title for
> Android has a maximum length of 30 characters.
> 
> On iOS it's currently "Firefox Focus: The privacy browser" (34 characters).
> English is too long, and there's no way we can translate that.

Flod, good catch on the character limits of the title. 

When possible we want to use:

Firefox Focus: Private Browser (30 characters)

If space is needed:

Firefox Focus: Private & Fast (29 characters)

Firefox Focus: Private. Fast (28 characters)

Comment 12

[Francesco Lodolo [:flod]]

I think we might need to accept the idea that:
* Some locales will only be able to use one of the adjectives. Is "Private" better than "Fast" in case? 
* Others might even need to use only "Firefox Focus".

Just to confirm, we're still waiting for text to be used in one more screenshot?

Comment 13

[Francesco Lodolo [:flod]]

(In reply to Francesco Lodolo [:flod] from comment #12)
> Just to confirm, we're still waiting for text to be used in one more
> screenshot?

Forget this, just saw bug 1349052. Still need a clarification on the other question before exposing the string.

Comment 14

[Fabio Rios [:frios]]

(In reply to Francesco Lodolo [:flod] from comment #12)
> I think we might need to accept the idea that:
> * Some locales will only be able to use one of the adjectives. Is "Private"
> better than "Fast" in case? 
> * Others might even need to use only "Firefox Focus".
> 
> Just to confirm, we're still waiting for text to be used in one more
> screenshot?

"Private" is higher priority than "speed". 

It's OK if we need to limit to "Firefox Focus" in some locales. No punctuation needed if this is the case.

In those instances when we can only have one adjective, I'm happy to leave it up to the team to modify the message so that it makes sense. We just need to make sure we start with the Firefox Focus name and add a note about being private. 

For example: 

"Firefox Focus: It's Private"

Comment 15

[Francesco Lodolo [:flod]]

System is set-up
https://l10n.mozilla-community.org/stores_l10n/#focus_android_release

If there's a green cell near the locale it means it's completely translated. You can use the HTML link to copy text for each locale, for automation there's the JSON link.