What\u2019s new or coming up in Firefox desktop<\/h2>\nFirefox string deadline changes<\/h3>\n
Starting with 149, some changes in developer deadlines relating to Nightly and Beta have resulted in a slight shift in string translation deadlines, giving us 2 extra days to land strings. Previously deadlines in Pontoon were set to the Sunday ahead of the final Release Candidate but going forward they will be set to a Tuesday. For example the upcoming deadline for Firefox 151<\/a> is Tuesday, May 12.<\/p>\n If you’re interested to see more details on upcoming Firefox releases and milestones, https:\/\/whattrainisitnow.com<\/a> has all the latest details.<\/p>\n Behind the scenes a refresh on the visual look of Firefox has been ongoing using the internal name \u201cNova\u201d. You may have seen some blog reports recently on this, or perhaps have been seeing bugs in Bugzilla with this in the title. We will start seeing new strings related to these changes here and there as development work progresses, however we don\u2019t expect a large number of string changes stemming from this work.<\/p>\n That being said, these updates also bring some changes in how we communicate directly to our users within Firefox. One of these changes you may have already met: our new mascot Kit. If you missed the announcement give it a read here<\/a>. You may also notice a shift voice for user directed messages \u2014 with source strings becoming more Genuine, Fiery, and Playful. See this recent update<\/a> in Firefox\u2019s brand voice for more details.<\/p>\n Localization for the update to about:settings has been going on for some time (starting early this year) and the bulk of the translation work is behind us at this point. You may see some new strings (particularly around Privacy & Security) but many of the strings are in a viewable\/testable state in Nightly 152. You can check your translations and test out the redesign by typing Things have been particularly busy on mobile over the past couple of months. For example, Firefox for Android saw a significant spike in April, with the number of new strings increasing to over 200 compared to fewer than 50 in March \u2014 more than eight times the typical monthly volume*<\/sup>.<\/p>\n There are two main drivers behind this increase. First, Firefox for Android is introducing a built-in VPN feature, bringing it in line with the functionality already available in Firefox. Second, both iOS and Android teams are working on a new widget for the upcoming 2026 World Cup, allowing users to follow their team directly from the browser.<\/p>\n *<\/sup> Did you know that you can track the number of new strings in a project from the Insights page in Pontoon? Check for example Firefox for Android<\/a>. In the Translation activity<\/i> chart, click on New source strings<\/i> in the legend to display this data. Given the difference in scale, it can also help to hide other metrics to make the chart easier to read.<\/p>\n New documentation system<\/b>. Pontoon now features a brand-new, unified documentation system<\/a>. This new hub brings together previously scattered resources into a single, streamlined experience, consolidating developer, localizer, and admin documentation from three separate sites into one cohesive platform. By centralizing content, the new system makes it easier to find, navigate, and maintain documentation, ensuring contributors of all roles have quick access to up-to-date and consistent guidance.<\/p>\n Search<\/b>. You can now set default search options<\/a> directly in your profile<\/a>. This allows you to tailor your search without having to adjust filters each time.<\/p>\n The same settings are also applied when using the recently introduced<\/a> global search page<\/a>, which brings a major step forward in unifying localization across Mozilla by allowing users to search for strings across all projects and locales in one place. Inspired by Transvision and designed as its successor, the feature integrates deeply with Pontoon, making it easy to filter results, compare translations across languages, and jump directly into the translation workflow.<\/p>\n In addition, the prompt now includes more contextual data:<\/p>\n This additional context helps the model generate more relevant suggestions. It also represents a first step toward making LLM suggestions more useful, ahead of potential experiments with displaying them by default alongside suggestions from traditional machine translation.<\/p>\n New contributors<\/b>. We\u2019re also excited to welcome a group of new contributors who have started making an impact on Pontoon over the past few months. MundiaNderi<\/a>, nishitmistry<\/a>, dannycolin<\/a>, first-afk<\/a>, wassafshahzad<\/a>, huseynovvusal<\/a>, and Peacanduck<\/a> have all contributed valuable improvements across different parts of the project, helping us move faster and improve the overall experience.<\/p>\n A special shoutout goes to Serah (MundiaNderi), who not only made significant contributions but also shared insights into her work in a recent blog post<\/a> about enhancing comment management in Pontoon\u2014an excellent example of the kind of collaboration and knowledge sharing we love to see in the community.<\/p>\n As part of the recent documentation update for Pontoon, we\u2019ve reorganized the content around pretranslation to make it clearer and easier to navigate. There is now a dedicated page<\/a> outlining the criteria required to enable pretranslation for a locale, along with guidance on how to monitor its effectiveness over time (for example, by tracking metrics like acceptance rate or time to review). If you\u2019re a locale manager and want to try pretranslation for your locale, you can request it directly from Pontoon<\/a>.<\/p>\n Over the past 12 months, we also ran a limited experiment using paid translation agencies for two locales. The goal was to restore the localization level of Firefox for Android in cases where the community was inactive \u2014 situations that have since improved, with both communities now active again. Image by Elio Qoshi<\/p><\/div>\n We continue the localizer spotlight series this year.<\/p>\n If you enjoy the series, please help us identify the localizers you\u2019d like to see featured filling out this nomination form<\/a>. If you have stories to share, tell us in your own words.<\/p>\n Know someone in your l10n community who\u2019s been doing a great job and should appear here? Contact us<\/a> and we\u2019ll make sure they get a shout-out!<\/p>\n If you want to get involved, or have any question about l10n, reach out to:<\/p>\n Did you enjoy reading this report? Let us know<\/a> how we can improve it.<\/p>\n","protected":false},"excerpt":{"rendered":" Please note some of the information provided in this report may be subject to change as we are sometimes sharing information about projects that are still in early stages and … Read more<\/a><\/p>\n","protected":false},"author":663,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[467028,137],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/posts\/1883"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/users\/663"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/comments?post=1883"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/posts\/1883\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/media?parent=1883"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/categories?post=1883"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/l10n\/wp-json\/wp\/v2\/tags?post=1883"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}UI Refresh<\/h3>\n
Settings redesign<\/h3>\n
about:config<\/code> into your URL bar, proceeding past the warning message, and searching for browser.settings-redesign.enabled<\/code> and setting the value to true<\/code>.<\/p>\nWhat\u2019s new or coming up in mobile<\/h2>\n
![\"Screenshot](\"https:\/\/blog.mozilla.org\/l10n\/files\/2026\/04\/firefox_android_worldcup-600x915.png\")
<\/a>Given the short turnaround time for this feature, you will notice that many strings are intentionally kept consistent across platforms \u2014 and started landing on Desktop as well. We\u2019re also pre-landing as many strings as possible, ahead of implementation, to give localizers more time to complete translations.<\/p>\nWhat\u2019s new or coming up in Pontoon<\/h2>\n
![\"Screenshot](\"https:\/\/blog.mozilla.org\/l10n\/files\/2026\/02\/translation_search-600x436.png\")
<\/a>AI integration<\/b>. We\u2019ve also refined the prompt used by the LLM-powered translation feature<\/a>. The goal is not to change how the feature works, but to make its output more consistent and better aligned with the context available in Pontoon. For example, the updated prompt improves how punctuation is handled, reducing variability in suggestions.<\/p>\n\n
![\"Screenshot](\"https:\/\/blog.mozilla.org\/l10n\/files\/2026\/04\/Screenshot-2026-04-01-at-11.20.35-600x340.png\")
<\/a><\/p>\nNewly published localizer facing documentation<\/h2>\n
\nBecause volunteer communities remain the foundation of Mozilla\u2019s localization model, we wanted to be transparent about when and why this approach was used, and what it means in practice. This includes clarifying how external support fits within a community-driven ecosystem, where localizers retain ownership and responsibility for quality and direction. You can find more details in this page<\/a>.<\/p>\nFriends of the Lion<\/h2>\n
![\"\"](\"https:\/\/blog.mozilla.org\/l10n\/files\/2017\/07\/2-Lions-01-252x232.png\")
\n
Useful Links<\/h2>\n
\n
Questions? Want to get involved?<\/h2>\n
\n