We asked ourselves a number of questions - what capabilities exist today to support our ambitions? What are the pain points within our current architecture? How will these pain points be amplified when the number of supported languages has more than doubled? What new problems do we foresee both technically and organizationally? What capabilities do we need to sustainably support all of these languages, both short and long term? To support the business case, it was essential to understand what was required on the tech side to pull off the effort.įirst, we needed to assess our technical landscape. We could also expand our total addressable market and make our product more accessible to an even more diverse user base. By increasing the number of supported languages from 26 to more than 60, we believed we could expand our reach and impact those users whose native languages were not supported at that time. When we first started thinking about Scaling Translations, Spotify was available in 26 languages. Industry peers have indicated that translations have been one of their strongest drivers of growth over the years. We believe that localization is key for engaging with our users across the world. We called the project Scaling Translations. This article describes how we delivered on such an immense localization effort at Spotify. Last year, we added support for 36 new languages to our products in one go, for a total of 62 languages.
0 Comments
Leave a Reply. |