Bringing a localized experience to our social channels

As the number of people wanting to be our friends and stay connected with Firefox increases, a growing number of those users speak languages other than English. This gives us a big opportunity to interact with them in their own language.

Just as Firefox is localized in over 80 languages, imagine if our Facebook page or Twitter presence was available in 80 languages as well. And what if users could have conversations with other users and Mozilla contributors on those social networks as well? That would be quite a rich experience, and I think it’s an experience we should strive to offer for our 5 million+ users on those networks.

Studies have shown that localized content on these channels offers an experience for users that is several times more engaging. The exciting bit is that we’ve already localized some of our content on our social channels, and it’s proven to be quite successful in engaging our users. We currently localize announcements for Firefox updates and new campaigns, and we also localize our custom tabs on Facebook when possible.

We can improve on this by creating an easy way to offer localized versions of almost all our content on these pages. We could start with a few locales as a trial. We’d create solid experiences and have conversations with those users that is just as compelling as our English content. If successful, we could then add more locales.

What is your favorite way that Firefox content is localized (besides in the product itself)? What organizations or brands have you seen localized content for that have impressed you? Add your thoughts in the comments.

2 thoughts on “Bringing a localized experience to our social channels

  1. For my locale(s) the issue is small localisation team. I’d love to be reaching Firefox users on Facebook in languages such as Afrikaans, Swahili and Zulu. And we’re aware that reaching those audiences could grow our team.

    We have quite a lot of work to keep the product localised and that won’t decrease. But you can help us by making it easy for us to contribute localisations. Which means no new formats, please don’t ask us to log into Facebook to do the work, no strange formats in bug reports. Please. For us what works best are texts loaded into Pootle/Vebatim that we can simply translate in a localisation environment.

    This does require automation on your part. But think of it rather as time*80 that you are going to save for localisation teams. Save us time and you get more localised.

    Make it easy of us to translate and make it clear which parts are needed for which campaign or platform.

  2. Facebook have very limiting support for content (such as status messages) localization, and Twitter doesn’t have content localization support at all. Also, when publishing status messages in languages which the Facebook page owners doesn’t know, this make it impossible to them to actually listen to the replies made by the followers.

    Unless things are going to get changed soon, I’d recommend to create separated pages for non English localizations, and promote them on for these locales.

    Some locales already have presence in social networks. For example we have in Israel our very own Facebook page which more than thousand followers.

Leave a Reply

Your email address will not be published. Required fields are marked *