Firefox Sync Reboot

Creating an account system for future Firefox connected services.

The original Sync authentication method (JPAKE) was not gaining traction with users.

My Role

Senior Product Designer

Teammates

Engineers, Program Manager, Product Managers, Security Engineers, Data Scientists

Challenges

  • Large userbase
  • Fragile
  • Many teams
  • Encrypted data

Methods

  • Ideation
  • Browser Feature
  • Design Systems
  • User Flow Diagrams
  • Wireframes
  • Prototypes
  • Data Analytics

The problem and how it was solved

Firefox was the first browser to introduce syncing but had the problem in that few people could figure out how to configure it correctly.

The original Sync authentication method (JPAKE) never converted users
The original Sync authentication method (JPAKE) never converted users

Along with my design engineer, I was tasked with designing a conventional account system that integrated into Firefox on every platform.

Firefox Sync Reboot

What came next?

With a successful launch under our belt, we invested further into the feature.

Firefox Sync Reboot
Firefox Sync Reboot
Some designs intended to increase adoption
Some designs intended to increase adoption

All of these initiatives were coupled with remote user testing.

Firefox Sync Reboot
2FA and recovery codes were added
2FA and recovery codes were added
The onboarding flow for Sync
The onboarding flow for Sync

Impact

Within 10% of the time, the new Sync had attracted 10x the number of users eventually reaching 20M MAU.

← Back to all work