{"id":7145,"date":"2022-09-07T13:45:39","date_gmt":"2022-09-07T13:45:39","guid":{"rendered":"https:\/\/phrase.com\/?post_type=case-study&p=7145"},"modified":"2025-08-13T15:33:23","modified_gmt":"2025-08-13T13:33:23","slug":"livestorm","status":"publish","type":"case-study","link":"https:\/\/phrase.com\/customers\/livestorm\/","title":{"rendered":"Accelerating and Simplifying Localization During Rapid Growth"},"content":{"rendered":"\n
\n
\n
\n
\"Livestorm<\/figure>\n<\/div>\n\n\n\n
\n

Born from a lunch With a rapidly growing customer base and a constantly evolving product, Livestorm\u2019s<\/a> localization process was struggling to keep up with the increasing number of text strings and locales., Deliveroo\u2019s Journey to 170,000 partners and counting. <\/strong><\/p>\n\n\n\n

Aiming to accelerate, streamline, and centralize localization, Livestorm implemented Phrase Strings. The intuitive platform is helping Livestorm save time and minimize translation errors \u2013 and crucially, the Phrase solution will scale seamlessly as Livestorm continues to grow.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

CHALLENGE<\/p>\n\n\n\n

More languages, more text strings, more complexity<\/h3>\n\n\n\n


When Livestorm launched in 2016, the majority of its customers were based in France and the USA\u2014but it wasn\u2019t long before it gained traction on a global scale. Today, Livestorm has customers in more than 40 countries, and catering to such a linguistically diverse user base is no easy task.

Thibaut Davoult, Growth Engineer at Livestorm, explains: \u201cThe Livestorm app is available in 16 languages, and we\u2019re adding more on a regular basis. At the same time, we\u2019re always working on new features, which means more text strings that need translating. As the number of locales and the volume of text grew, localization became increasingly complex.\u201d

Livestorm incentivizes its users and customers to help with translations, but it relied on spreadsheets to manually collect language keys from contributors. Without a dedicated tool, gathering the translations was a time-consuming task, and version control was particularly painful. Internally, the team developed a meticulous checklist to avoid mistakes while implementing a new language.

Yet, as the scale of localization grew\u2014with more languages, text strings, and employees involved\u2014the checklist became more cumbersome than effective. \u201cLocalization speed was becoming a problem,\u201d continues Thibaut. \u201cAnd developers were shouldering too much of the work load. We needed a way to accelerate and centralize the process, and we needed a solution that would be scalable as Livestorm continued to grow.\u201d<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

SOLUTION<\/p>\n\n\n\n

Phrase Strings\u2014easy to use, easy to implement<\/h3>\n\n\n\n


After carefully evaluating several localization solutions, Livestorm decided to implement Phrase Strings. Robin Lambert, Co-Founder and Product Designer at Livestorm, leads the localization team, and was responsible for choosing the new solution. Robin comments: \u201cBy far the most important selection criterion for us was ease of migration from our old system.

The last thing we wanted to do was manually reproduce all our spreadsheet data. Phrase Strings\u2019 powerful importing tools and excellent onboarding team made it an easy decision.\u201d Livestorm was also impressed by Phrase Strings\u2019 user-friendliness, and its extensive format support. Robin\u2019s team works with both i18next and Rails i18n, so format flexibility was essential. Phrase Strings consolidates all of Livestorm\u2019s localization tasks into a single, easy-to-use dashboard.

Translators can work directly through the dashboard, which completely eliminates the need for spreadsheets. Similarly, Phrase Strings enables a centralized, well-defined localization process, so Livestorm no longer has to worry about manually following a complex checklist. Robin adds: \u201cWith the help of Phrase Strings\u2019 Customer Success onboarding team, implementing the solution took less than two weeks. That is quite a feat considering how complicated our legacy process was when we made the switch.\u201d<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
<\/div>\n\n\n\n

STATS & FACTS<\/p>\n\n\n\n

Livestorm by the numbers<\/h2>\n\n\n\n
\n
\n
\n

40<\/p>\n\n\n\n

countries<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

17<\/p>\n\n\n\n

languages<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

50%<\/p>\n\n\n\n

less time spent on localization <\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

1.6M<\/p>\n\n\n\n

words processed<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

BENEFITS<\/p>\n\n\n\n

Simple and scalable<\/h3>\n\n\n\n


Livestorm is now perfectly positioned to deliver its web conferencing service in more languages and with more features than ever, without being held back by localization constraints. \u201cThe localization process is so much more streamlined, which makes it much easier to release new versions and add new locales,\u201d confirms Thibaut. \u201cWe\u2019d say we\u2019ve shortened the developer working time when adding new languages by 50%.\u201d

Phrase Strings is delivering time-savings through a host of features. When maintaining spreadsheets, there was always a risk of accidentally deleting valid keys; but with Phrase Strings, that is a complete non-issue. Likewise, Phrase Strings\u2019 search engine and progress tracking tools make it easy to find particular keys or see what needs translating. Last but not least, with Phrase Strings automating many of the processes that Livestorm developers used to perform manually, adding new languages is now significantly more straightforward.

Most importantly, Phrase Strings is fully scalable, so Livestorm will be able to keep enjoying all of the benefits even as the company size and scope of localization continue to grow. Thibaut concludes: \u201cPhrase Strings has already made it possible for us to double the number of people involved in localization internally, and that number should scale nicely as the team grows. It\u2019s great knowing that we can expand the localization team without increasing the complexity of the process.\u201d<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n

FEATURES USED<\/p>\n\n\n\n

Key Phrase Strings features that help Livestorm localize at scale<\/h3>\n\n\n\n
\n
\n
\n
\"\"<\/figure>\n\n\n\n

API<\/h4>\n\n\n\n

The API allows you to import locale files, download locale files, tag keys, or interact in other ways with the localization data stored in your Phrase Strings account.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\"\"<\/figure>\n\n\n\n

User roles and access control<\/h4>\n\n\n\n

Organize your localization team by assigning dedicated roles and access rights to each team member according to projects and locales.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\"\"<\/figure>\n\n\n\n

Multiple projects<\/h4>\n\n\n\n

As software projects grow and become more complex it helps to split them into modules to keep things manageable. The same holds true for the localization of software projects.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\t
\n\t\t
\n\t\t\t

The localization management process is so much more streamlined at Livestorm<\/a>, which makes it much easier to release new versions and add new locales.<\/p>\n\t\t<\/div>\n\t\t

\n\t\t\t\n\t\t\t
\n\t\t\t\t\"Logo\n\t\t\t\t

\n\t\t\t\t\tThibaut Davoult\t\t\t\t<\/p>\n\n\t\t\t\t

\n\t\t\t\t\tGrowth Engineer\t\t\t\t<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t<\/div>\n\t<\/div><\/div><\/div><\/div>\n\n\n\n

\n

Ready to get started?<\/h2>\n\n\n\n

Reach a wider audience and build deeper connections today.<\/p>\n\n\n\n

\n
Request a demo<\/a><\/div>\n\n\n\n
See pricing<\/a><\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Learn how Livestorm overcame its globalization challenges with our complete solution for high-quality, scalable, and fast localization.<\/p>\n","protected":false},"featured_media":37382,"parent":0,"template":"case-study-refresh","case-study-tag":[116],"class_list":["post-7145","case-study","type-case-study","status-publish","has-post-thumbnail","hentry"],"acf":{"image":{"ID":3325,"id":3325,"title":"livestorm_logo_bw_testimonial","filename":"livestorm_logo_bw_testimonial.svg","filesize":4184,"url":"https:\/\/phrase.com\/wp-content\/uploads\/2022\/08\/livestorm_logo_bw_testimonial.svg","link":"https:\/\/phrase.com\/?attachment_id=3325","alt":"Livestorm logo | Phrase","author":"6","description":"","caption":"","name":"livestorm_logo_bw_testimonial","status":"inherit","uploaded_to":1107,"date":"2022-08-16 19:11:38","modified":"2022-08-24 07:00:00","menu_order":0,"mime_type":"image\/svg+xml","type":"image","subtype":"svg+xml","icon":"https:\/\/phrase.com\/wp-includes\/images\/media\/default.png","width":240,"height":41,"sizes":{"thumbnail":"https:\/\/phrase.com\/wp-content\/uploads\/2022\/08\/livestorm_logo_bw_testimonial.svg","thumbnail-width":240,"thumbnail-height":41,"medium":"https:\/\/phrase.com\/wp-content\/uploads\/2022\/08\/livestorm_logo_bw_testimonial.svg","medium-width":240,"medium-height":41,"medium_large":"https:\/\/phrase.com\/wp-content\/uploads\/2022\/08\/livestorm_logo_bw_testimonial.svg","medium_large-width":240,"medium_large-height":41,"large":"https:\/\/phrase.com\/wp-content\/uploads\/2022\/08\/livestorm_logo_bw_testimonial.svg","large-width":240,"large-height":41,"1536x1536":"https:\/\/phrase.com\/wp-content\/uploads\/2022\/08\/livestorm_logo_bw_testimonial.svg","1536x1536-width":240,"1536x1536-height":41,"2048x2048":"https:\/\/phrase.com\/wp-content\/uploads\/2022\/08\/livestorm_logo_bw_testimonial.svg","2048x2048-width":240,"2048x2048-height":41},"svg":"\n\n\n\"Livestorm"},"copy":"","link":{"title":"Livestorm","url":"https:\/\/phrase.com\/customers\/livestorm\/","target":""},"case_study_logo":false,"landing_page":[],"search_content_type":"","header_video_type":"none"},"taxonomies":[{"term_id":116,"name":"Technology","slug":"technology","term_group":0,"term_taxonomy_id":116,"taxonomy":"case-study-tag","description":"","parent":109,"count":25,"filter":"raw"}],"_links":{"self":[{"href":"https:\/\/phrase.com\/wp-json\/wp\/v2\/case-study\/7145","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/phrase.com\/wp-json\/wp\/v2\/case-study"}],"about":[{"href":"https:\/\/phrase.com\/wp-json\/wp\/v2\/types\/case-study"}],"version-history":[{"count":4,"href":"https:\/\/phrase.com\/wp-json\/wp\/v2\/case-study\/7145\/revisions"}],"predecessor-version":[{"id":114268,"href":"https:\/\/phrase.com\/wp-json\/wp\/v2\/case-study\/7145\/revisions\/114268"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/phrase.com\/wp-json\/wp\/v2\/media\/37382"}],"wp:attachment":[{"href":"https:\/\/phrase.com\/wp-json\/wp\/v2\/media?parent=7145"}],"wp:term":[{"taxonomy":"case-study-tag","embeddable":true,"href":"https:\/\/phrase.com\/wp-json\/wp\/v2\/case-study-tag?post=7145"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}