Firefox Accounts Ecosystem

Integrated over a dozen teams' services with the account system.

Soon after we created the Firefox Account system, we began connecting new and existing Firefox services.

My Role

Senior Product Designer

Teammates

Design Engineer, PMs, EMs, PMMs, dozens of teammates

Challenges

  • Herding cats
  • All form factors
  • Lack of standards
  • Multiple time zones
  • Locally synced encrypted data

Methods

  • User Flow Diagrams
  • Wireframes
  • Prototypes
  • User Testing
  • Data Science
Many of the devices and services that connected to the account system
Many of the devices and services that connected to the account system

The problem and how it was solved

Firefox is most known as a web browser, and Chrome's rise was due largely in part to their perceived compatibilities with Google properties.

In order to lean into its reputation for user privacy, Mozilla began building out an ecosystem of services that integrated natively with Firefox.

Firefox Accounts Ecosystem
Firefox Accounts Ecosystem
Early designs for increasing adoption of services in the Firefox browser
Early designs for increasing adoption of services in the Firefox browser

Allowing for flexibility

Supporting simple web properties was easy, but some relying parties like browsers or VR headsets were more complicated.

Firefox Accounts Ecosystem
Detailed analytics and A/B frameworks allowed us to always be optimizing
Detailed analytics and A/B frameworks allowed us to always be optimizing

Research Findings

The most powerful learning was that there is no intrinsic value in having a Firefox Account.

Impact

Grew the userbase from zero to 20M MAU and enabled the future of Firefox connected applications.

← Back to all work