Category Archives: Announcements

LINE is ready for Firefox OS!

Line-app-logo-150x150At SUMO, we realize that the need for choice in messaging services has been among the most popular feedback from our users. Although the development of third-party applications such as these is out of our control, and dependent only on the interest of each developer, Mozilla has been working closely with partners to ensure that our user’s voices are heard.

With this in mind, we are happy to announce that Line, the popular instant messaging service with over 300 million registered users worldwide, is the newest addition to the world of Firefox OS!

This application is fully compatible with all the other available platforms, making it much easier and fun to stay in touch with friends and family. The development of this app supports the idea of Firefox OS as the future of mobile, providing openness, innovation, and opportunity on the Web.

You may download Line by simply searching for “Line” on the Marketplace, or by tapping on the following link from your Firefox OS device:

There are many other choices in the Marketplace that allow users to communicate with each other. Loqui and ConnectA2 are available and allow some compatibility with Whatsapp, while Facebook and MessageMe allow for some additional communication options.

We are looking forward for many more amazing apps to sprout and populate our ever-growing Marketplace in 2014.

Stay tuned!

[Your Feedback Needed] A simplified and focused L10n dashboard

The localization dashboard is going to see major changes soon to make sure that it is as simple and focused on the tasks at hand as possible. We need your feedback to make sure we are making the right decisions. If you are using the L10n dashboard and want to take part in the discussion, please had over to the following bug, have a look at the attached mockup, and leave your comment:

The following is a quick summary of what changes we are making and why.

One of the biggest strength of the platform that SUMO is built on is the fact that localization has been one of the key design components. We created several localizer personas when we designed Kitsune and had them in mind when we made decisions early on. One of those decisions was to create an L10n dashboard that would present all the data that localizers might need to get their job done.

Since the early SUMO was rather small and focused on a single product, the L10n dashboard worked pretty well. Since then however, we have increased the scope of SUMO and added several more products and more functionality. The L10n dashboard grew organically during those times to cover more products and functionality.

Now seems like a good time to take a look at the tasks that localizers are faced with today and bring the the L10n dashboard into shape again. Rosana and I started that discussion with one thought: The L10n dashboard should answer one question and should do that as good as possible: “What should I be working on next”.

The current L10n dashboard present a lot of data, but unfortunately not all of it is relevant or actionable. While that data should still be accessible, it doesn’t make sense to present it as prominently as we are doing today. Having the one question in mind we cut back a lot of unnecessary information and came up with a streamlined, simple interface that bundles information and presents only things that localizers need at any moment. When we printed the current L10n dashboard out, it took covered 4 full pages, the current proposal can fit onto a single page.

Here you can see a mockup of our proposed L10n dashboard:
localization dashboard

To summarize the changes we made:

  • The product picker that is currently a drop down becomes a visual product picker. The product icons should be rather small though, to make sure people can see as much of the L10n dashboard above the fold as possible.
  •  The overview section is slimmed down by removing the “administration” articles and the explanatory text. We oversize the progress bar for the top 20 articles, so that updated articles lead to visible changes. The logic of orange -> green stays the same. We then remove the explanatory text and add it to the overview section items as tooltips. The now free space is used for bigger progress bars.
  • The actual content section is separated into Localization and Review
  • The Localization tab has a list of articles that need attention, where need attention is defined as “needs translation, needs update, and needs immediate update”. The list is ordered by most views in the last 30 days. Thus we are doing away with all other lists on the L10n dashboard.
  • Each article in the “needs attention” list shows below it the templates that are included in the article that need attention. Same rules for “need attention” as before.
  • The review tab has a list of top 20 articles needing review with a link to all articles needing review. The templates are listed the same way as on the localization tab, only templates that need review or “need attention” are listed.

If you want to take part in the discussion, please had over to this bug and leave your comment there:

We need your feedback to make sure we are making the right decisions with these big changes.


Your feedback for the new SUMO support forum needed


We need your help in designing the presentation of the support forum statuses. If you have been following the contributor or the platform meeting, this is probably old news for you, but for everyone else: Big improvements to the support forums are coming.

A few month ago we set out to evaluate the support forum. The insights were partially surprising and partially confirmed our suspicions. The good news is: We are helping a huge number of people with their Firefox questions. However, the report also showed that we have two big issues:

  1. In too many cases people don’t come back, so we don’t know whether we are really helping them
  2. In too many cases we leave people hanging when they come back, either because we forget to get back to them, we’re out of our depth, or the question is not completely about using Firefox.

This quarter we set out to address these issues one by one:

  • We are looking into ways to let people easily reply in the forums when they receive a message from us, ideally they won’t need to even log in. This should increase the number of forum threads where we do get feedback on the solution we provided.
  • We have enlisted the help of the SUMO helpdesk to take care of issues we can’t solve alone. We can now escalate questions and have them spend time with us and the users to find the solution.
  • The heldpesk will also cover questions that are not completely about using Firefox.
  • We have introduced a new model for questions, specifically “states”. A question either “needs attention”, is “responded” to or is “done”. This way we can very easily tell which threads we haven’t responded yet, needing our attention the most.

Now, the challenge is to find a way to present all of this information in a way that is useful for as many contributors as possible. That includes current and future contributors. We have created a first mock-up, that you can see here: The discussion around that has already started and you can follow along here:

We urgently need feedback on this, because it will be a large scale change, that will affect every contributor using the support forums today. In particular we are interested in answering the following questions:

  • What in particular are you looking for when using the support forums? Open questions, questions with lot’s of replies? Questions where you have replied?
  • Are their certain combinations of filters that make sense to you and that should be the default?

Please leave your replies in the forum. We will use this thread to develop this mock-up further.


Escalating Forum Posts

Hello I’m Patrick with SUMO’s Helpdesk. I’ve gotten to meet a few of you at the Summit in Toronto, but for those who I haven’t met yet I wanted to explain the role that Helpdesk can play within SUMO and how we can help contributors fill in the gaps on the forums. Things like getting us to 100% question replied to in 24 hours and increasing our solution rate.

For Q4 we’re working on using the existing forum tagging system to start leveraging the skills of our long time contributors, as well as getting the Helpdesk involved when you don’t know know the answer.

The tag that I’m most excited about is Escalated, which you can use when you just can’t figure out the solution to customer’s problem. There will be new filters which you can use to only look at the Escalated case if you want to work on the hard stuff. In addition escalating a post will send a ping to the Helpdesk with the forum URL, so we can get involved if needed. Posts can be also be automatically tagged as Escalated after it has gone 12 hours with No Replies.

A few people have asked what kind of posts should be escalated? If you’re unsure of how to reply mark it escalated. Since everyone is able to see escalated tagged post, anyone can answer them.

This tag along with new Filtering options, will allow all of us all to see what posts need our attention and get the customer a more timely response.

We’re hoping to have all of this rolled out before the end of December. There is a bug tracking the work for this feature here Bug 932348 – Escalated threads should create zendesk ticket, so please let us know what you think and if you’re interested in focusing on these escalated cases I’d love to hear from you.

Gravatar for Avatar

For a long time we have had small avatars on SUMO, but with the shiny new profile pages they look out of place. So we are going to support bigger avatars soon. But there is a twist: We won’t just increase the size of the avatars, we are switching to Gravatar instead. Gravatar is used by large number of online services including This means that you don’t have to manage your avatar on SUMO separately unless you really want to. You can just upload an image once on Gravatar and have it show up on all kinds of webservices you are using.

Now, what does this change mean for you?

  1. If you are a new user and have a Gravatar account already, we’ll automatically use that when you create a new account on SUMO
  2. If you are a new user and don’t have a Gravatar account yet, you’ll get the default avatar as always and you can change your Avatar by going to the Gravatar page (linked from your profile on SUMO)
  3. If you are an existing user with a Gravatar account, we’ll replace the avatar you have here with the one in your Gravatar account.
  4. If you are an existing user without a Gravatar account nothing is changing for you. But if you want to change your Avatar later on, you’ll be linked to Gravatar.

If you don’t want your standard Gravatar image to be shown on SUMO, you can change your email address on SUMO. You don’t have to actually use a different email account. Just append “+SUMO” to it. So if my mail address is it would become This way you still get your email to, but Gravatar won’t show the image here that you have set for

This is now live on our staging server: Please give it a try and let me know what you think. You can also comment directly in the bug for this:

¡Firefox OS ya está aquí!

Today we are celebrating the launch of Firefox OS in Spain, and to thank our Spanish speaking contributors, we decided to post the update in Spanish. We will resume with the English content after it.


Hoy es un gran día para la web: estamos orgullosos y emocionados de anunciar el lanzamiento global de Firefox OS.

Mozillians de todo el mundo hemos unido fuerzas para lanzar Firefox OS: una nueva plataforma móvil que abarca los valores de Mozilla y permite seguir empujando nuestra misión por una web libre.

El nuevos sistema operativo de Mozilla se merece y necesita del soporte de la comunidad, en especial de Mozilla Hispano, que ha ayudado a popularizar Firefox en el mundo hispanoparlante. SUMO y Mozilla Hispano hemos estado trabajando duro para crear todos los elementos que ayudarán a los nuevos usuarios de Firefox OS:

- Una nueva interfaz móvil para SUMO que simplifica la gran experiencia de en tu móvil.
- Más de 50 nuevos artículos que recogen las instrucciones más comunes de Firefox OS.

La  comunidad de localizadores ha realizado un gran trabajo para asegurarse qué este contenido esta disponible en Español y demás lenguas en las que Firefox OS será lanzado.

Estamos convencidos que gracias a todos los que han contribuido a SUMO y Mozilla Hispano, estamos preparados para esta nueva generacion de usuarios móviles de Mozilla. Pero esto es sólo el principio, ¡ya que es ahora cuando empieza la diversión!

FirefoxOS.2En esta nueva aventura tendremos muchos nuevos usuarios que accederan a la web, por primera vez, a través de sus teléfonos móviles. De manera similar, una larga lista de usuarios de Firefox buscarán como obtener el máximo rendimiento de sus nuevos terminales. Tal y como hemos hecho hasta ahora con Firefox y Firefox para Android, es nuestra responsabilidad ayudarles. Tenemos grandes herramientas como los foros de Mozilla Hispano y la Armada Alucinante. Es el momento de agarrar tu capa de superheroe y ayudarnos a hacer de la web móvil un lugar mejor.

¡Únete a nosotros en esta aventura!

Firefox Sentiment Reports

Hello all from the User Advocacy team! We have a special new tool to discuss today that will help us gauge the impact of each Firefox release on our amazing user base. We call this the User Sentiment Report (USR). While we’ve been working on this internally for the past couple of releases, fine tuning and tweaking the report, we are finally ready to make this report publicly available for both Desktop and Android Firefox 21!

What is a Sentiment Report?

The User Advocacy team spends a great deal of our time reading and tracking the feedback from our hundreds of millions of users via several channels (SUMO, Input, etc.). We use this feedback to find pain points, problems, and pleasures that users have with our products and then report on them to make sure our products get better and better with each release. One challenge that we have is getting the big picture of all feedback for a release, and gauging the general feeling of our users, if a release had a lot of problems for users, or if it was a very smooth one. So, the Sentiment Report was created. This report allows us to see specific releases, the general feeling of users for that release (based on the number of SUMO reports, negative pieces of input, etc.) and easily compare it to previous releases (allowing us to determine what a “Normal” release is). This report is generated at the end of every release cycle using feedback gathered since release day. The insights from this report have not been possible ever before, so we are excited to have expanded this report to Firefox for Android.

Firefox for Android Sentiment Report

While the Firefox for Desktop Sentiment Report has been ongoing for a couple of releases as we fine tuned it, we haven’t had a Firefox for Android report until this cycle. Using what we have learned from Desktop, here is the first ever Mozilla User Sentiment Report for Android!

There are a few things I’d like to highlight about the report. First is the trending topics. On we receive thousands of pieces of feedback for each release of Firefox. It is impossible to go through and read all this feedback manually. So with the help of the metrics team, we created an auto-tagger which, using a training set made by hand, will automatically tag all feedback that comes through input into roughly 20 different buckets (Crashes, websites issues, Flash issues, etc.). This allows us to watch for spikes and drops in various types of feedback and chase down anomalies when they happen. In the sentiment report, you can see the current top ten categories compared with the last 5 releases (Blue points are downward trends, Red are upwards). The numbers you see are negative input per 10 million ADI (Active Daily Installs).

Cost of Support (COS). This is an important metric. In it, we track clicks to the Help button in Firefox for Android per thousand ADI’s. The reason we watch this number is if we see a spike in Help button clicks along with a corresponding decrease in ADI’s, it is likely that there is a significant problem in that version of Firefox that is causing us to lose users. You can compare the week by week cost of Support and the overall COS for each version. Lower is obviously better (Low clicks to the help button with high ADI’s).

Most Painful Issues for Top Devices. Another awesome thing the auto-tagger lets us do is track what devices are having more issues in what categories, and lets us track these per release. So for example, we can see that the Nexus 7 was having major issues with Crashing in previous releases, but that this has consistently been trending downwards, meaning the crash work we have been doing has been paying off. Conversely we can see that the Asus TF300T had a small spike in complaints around slowness in Firefox 21, so we should begin to look into that for future releases. We can track these numbers for any device we have data on, but obviously we don’t have room to show them all in the report.

Firefox for Desktop Sentiment Report

Of course we have this report for Desktop too. Released at the same time as the Android Sentiment report, you can view the Desktop User Sentiment Report! This report tracks many of the same things that the Android report does, but with some notable exceptions.

Trending Topics. We don’t have an auto-tagger for Desktop (yet), so this category consists for topics that were automatically generated from feedback we received on this release, and then were manually curated to give the most relevant information possible.

Survey Data. We have a tool on Firefox for Desktop called Startup Snippets. Users that use the default about:home page in Firefox can see these little snippets of text under the search bar. At certain times during a release cycle we will deploy a link to a survey via these snippets to a certain sample of our users, asking for their feedback around the latest version of Firefox. We can then use this survey data to generate a star rating for Firefox (1-5 stars, with 5 being the highest).

The rest of the report is fairly self explanatory, Cost of support being the number of users who click the help button in Firefox per thousand ADI, negative input (and positive input), and the number of new support threads each week. Using all these graphs we can watch how a release fares over every week of the cycle and compare it with previous releases.

The Future

By no means are these reports in their final form. Every cycle of Firefox brings in new improvements to the User Sentiment Reports. We hope to add many new features in the future, such as tracking of Google Play data for Android, an auto-tagger for Desktop, etc. If you have feedback or ideas for these reports please feel free to contact Tyler Downer or Matt Grimes.

Of Course…

None of this would have been possible without a ton of hard work from many different people. Special thanks go to Hamilton Ulmer, Ali Almossawi, Annie Elliott, Ibai Garcia, and countless other people for their feedback and ideas.

SUMO in 2013 – Summary

This is the final part of the SUMO in 2013 blog post series — let’s wrap up:

If you read all previous posts, you probably noticed a few overarching themes throughout the series: Mobilization, Advocacy, and Scale.


With mobilization, I mean it in a non-traditional sense of the word: the web is becoming increasingly mobile, and this shift changes our efforts to support our users. We need to become mobile — we need to mobilize!

I’m extremely excited about our plans to create a mobile support experience that no one has built before. Mozilla Support is already insanely cool to use from your mobile phone, but just imagine how awesome it will be once we hook it into your phone’s notification system and utilize some of the new web APIs we’ve worked on as part of making the web itself the app platform for Firefox OS (and, long-term, for apps across all major mobile platforms). With the direction the web itself is taking through efforts like Firefox OS, the opportunities to create awesome experiences are only limited by your imagination.

The closest comparison to what is happening with the web today that I can think of is the introduction of the Sony Walkman in 1979, which revolutionized the way people listened to music. SUMO is heading in the same direction and this will bring lots of new opportunities to help fellow Firefox users no matter where you are — and the karma this will give you will feel more rewarding than listening to your favorite mixtape!


Over the years, we’ve gotten better and better at distilling user feedback from our support channels and reporting it to engineering and QA so they can prioritize their work on fixing the most annoying bugs our users complain about. Cheng played a huge role in kickstarting our efforts already back in 2008, and today we have a dedicated team responsible for this work. In 2013, we’ll institutionalize User Advocacy and partner even more closely with Product Management, UX, Engineering and QA to deliver on Mozilla’s brand promise: Firefox answers to no one but you.

We’ve already built in hooks to Input in Firefox OS so we can ensure high quality user sentiment and feedback reporting for the first handsets once we launch. Of course, our user advocacy efforts will go beyond our internal feedback tools — we’ll also be monitoring press, blogs, forums and social media throughout the product launch to make sure we aren’t missing anything. Our goal here is the same with Firefox OS as it’s been for desktop and Android Firefox: to proactively support our users by making our products better.


This is the glue that will tie it all together — at the end of 2013, our hope is that we’ll be able to look back at a year with significant community growth and where contributions went from just something you could do in front of your computer to something you could do anywhere you are as long as you have your phone with you.

SUMO staff, summer 2012.

We have awesome people in the SUMO community already — people like Alice, feer56, Scoobi, cor-el, Satdav, madperson, iamjayakumars, jscher2000, Tobbi, underpass, Swarnawa, smo, Nukeador, michro, and many many more (this is really just a sample of our incredibly passionate community!). At the end of 2013, I hope that these people will have taken even more ownership in their various areas of our support efforts — and I hope I’ll be able to list even crazier and impossible to pronounce forum nicknames for new people who joined our community this year!

As part of our quest to grow our community, we need to challenge our assumptions and traditions and be open to completely new processes and community governance models to scale our work to Mozilla’s growing product line. I’m envisioning a community where hundreds of people around the world help with everything from writing support articles that are read by tens of thousands of users, to helping users directly where our users are — the forum, social media, and in person. While I’m incredibly proud of the community we’ve been able to build so far around SUMO, I know we can do more.

Screen Shot 2013-02-15 at 15.46.20

SUMO superhero and his butler — awesome artwork by Sean Martell.

Thanks for reading thus far. If you haven’t already, please join our community and help us shape the future of the mobile web, get more involved with Mozilla, and help our users! It’s dead simple, fun, and can take as little as a few minutes to make an impact to thousands of people around the world.

Congrats, you made it to the end of the blog series about our Mozilla Support goals in 2013!

SUMO in 2013: Firefox Android

This is part 4 of SUMO in 2013, and the focus today is Firefox on Android!

Our goals for Firefox for Android support can be summarized in three words: Community, Mobilization, and Community! :)

Enable fully community-driven self-service support for Firefox for Android

The scope of SUMO has grown significantly in the last year. We went from supporting just one product (Firefox on the desktop) to multiple products, and this suddenly made the SUMO community feel small — despite being several hundred people strong!

In 2013, we will focus even harder on scale in order to keep up with all the support documentation needed for all of our products. With Firefox for Android, we want to enable a model where the ownership of the knowledge base is with the wider community. In practical terms, this means that the responsibility of keeping articles up to date and writing new ones would be shared by a wider group of people in our community.

Android is the most widely used mobile operating system today, and Firefox on this OS has made incredible improvements in the last year and is now easily the best web browser in the ecosystem. A big part of this has been our tireless work on helping our users on SUMO while listening carefully to what they’re telling us about their experience in places like our forum and in Google Play reviews.

Contributing to SUMO is a great way to get involved in this effort and help shape the future of Firefox on Android. Here are some ways you can dig in right now:

Develop mobile support web app with built-in social support


Bus Stop No. 75 by mgarbowski. (CC)

Imagine someone standing at a bus stop waiting for the bus to arrive in the morning. While she’s standing there, she pulls up her phone and launches the SUMO app where she finds a user who has a problem with Firefox for Android. She quickly pulls down a canned response, customizes the answer a bit and hits Send. Right there, as she was waiting for the bus, she was able to help a fellow Firefox user solve their problem. A few minutes later, karma kicks in: she gets a notification in her phone that the user found her answer helpful…. and the bus suddenly arrives!

In 2013 we want to enable mobile contributions like this — and this will of course also be useful to help users of all of our other products, including Firefox OS! We’re already well on our way with our work last year on mobilizing the SUMO website, but there are some more steps to take to “appify” it too — things like hooking into the mobile notification system.

This summarizes the key goals we are working on this year around Firefox for Android. Stay tuned for the final part of this blog series.

If you’re interested in getting involved and learning more about what we’re working on to make the web better, please join our discussions in our SUMO contributor discussions forum. Oh, and don’t forget that today is SUMO day. Help us answer questions in the support forum and join us in channel #sumo!

SUMO in 2013: Firefox Desktop

You’re reading part 3 of SUMO in 2013, and this time the focus is Firefox on the desktop!

Increase retention and user loyalty

Over the years, we’ve built something pretty amazing with the desktop Firefox support on SUMO, so this year it’s all about optimizing and oiling that engine to go from great to awesome. Overall, the goal in 2013 is to decrease issue-driven churn.

SUMO developments over the years

Snapshots of over the years.

Some of this has already been covered in the first part of this blog series — the stuff that applies to all of our products — but it’s worth repeating some of it here since desktop Firefox represents the vast majority of our traffic on today. There are two main components to this that will contribute to increased retention and user loyalty that we are responsible for:

  1. Understand our users by listening to their feedback. This is what the User Advocacy team is focusing their efforts on.
  2. Delighting our users with better-than-expected support. This is what the Desktop & Cross-Product Support team focuses on, including efforts like a kick-ass education strategy. But it also includes our focus on providing kick-ass help articles and covering more topics and answers.

Achieve 100% resolution rate in English support forum

To be clear, 100% resolution rate here means that no posts in the forum should be left unresolved. In other words, any user posting a question should get an answer to their question, and if that answer doesn’t solve their problem, we won’t give up until that problem is solved. However, it doesn’t necessarily mean that all resolutions will please the user — for example, if a user posts a question like “Why is there no official version of Firefox for Playstation 3?” we will simply do our best to explain why and resolve the thread that way. While the user may disagree with our answer, we would consider that thread resolved. So we won’t exactly achieve magic here — but we’ll get pretty close. ;)

Let’s be clear about one thing: this is a very ambitious goal. It will take a huge effort from everyone involved: our insane community of volunteers, our awesome WebDev team to prepare the platform for things like being able to mark threads as “unsolvable” (similar to the INVALID resolution in Bugzilla) and streamline the interface, and of course the SUMO team itself. There will no doubt be some threads that will be left behind or forgotten in the day-to-day answering of questions in our community. Because of this, we will need to have people ready to “fill in the gaps” as they appear, and to ensure that all threads that already have an answer actually lead to a resolution. Do you think we can do it? Would you like to help us while learning more about our products and development processes? Come join us in the forum!

Provide first response to all forum questions within 24 hours

Another forum-related goal this year is to ensure that everyone gets a first response within 24 hours of posting a question in the forum. This is part of our commitment to delight users with our support, and in reality we’ll aim to do even better than 24 hours — but this is already an ambitious goal as it is!

QuestionsThe good thing is that already making great progress in our ability to provide timely responses. In fact, we’re already responding to close to 80% of all of our questions within 24 hours. But the road to 100% will be both challenging and fun at the same time!

That’s it for desktop Firefox this year. Piece of cake, right? ;) In the next part, I’ll walk you through our goals for Firefox for Android.