Version 28 (modified by lnl, 4 years ago) (diff)

reformat page and text, delete old info, add updated (objective, contacts, projects).

UX Team

Welcome to the UX team page! ٩(◕‿◕)۶

Sign up for the mailing list here: UX mailing list (archives). We also meet regularly (times may vary) on this irc channel.


The mission of the UX team is to make Tor applications usable and useful to all the people that need them.

We aim to accomplish this through the following strategies:

  1. Visual Design: Make Tor applications look like the serious, high-quality pieces of software that they are by keeping the design current and expressive. We support application teams as they transition to and maintain a high standard of UX quality.
  1. Quantitative analysis: Where appropriate, we add anonymized metrics-gathering capacity to Tor applications to gain insight into how they are being used.
  1. Qualitative research: Through surveys, interviews, and other techniques, we systematically identify users' mental models, use cases, and any preferences. Eventually, we hope to build a reliable body of knowledge about what users' experience using the software is.
  1. Iteration: Whenever we conclude that a change would be beneficial, we incrementally add, fix, and remove design elements, features, or functionalities based on ongoing quantitative or qualitative insights.
  1. The Extra Mile: We support other teams that improve the user experience better. Consult on issues like internationalization of the interface, catering to at-risk users, or other ongoing improvements.

Our vision is to become an enthusiastic, multidisciplinary team of designers, UI engineers, and user researchers, data analysts, localization and internationalization specialists that constantly support application teams in their efforts to make their work as useable, useful, relevant, and delightful for users as possible. Let us know if you want to join us!


This team includes anyone working on the projects described below. We're not listing names here to keep the team open to everyone. You're considered to be on the team if you're participating in discussions and development, and you're not part of the team if you are not participating or stop participating. If you want to join us, contact the UX team lead at linda [at] torproject [dot] org.




  • Tor Browser UXsprint 2015: In January 2015 we asked 5 user to download, install, configuration, and perform basic usage tasks (such as web searching and getting a new identity). Their screen was broadcasted live to a room of developers, who created tickets based on their observations.


We plan to make this section more sophisticated, but currently, it's just a list of the subset of the tickets we remembered to document.

  • #16665 People are confused when their first hop (their guard) never changes.
  • #11773 Revisions to Tor Launcher based on preliminary results from doc/TorLauncherUX2016.

And any tickets marked #ux and #tbb-usability.


Documentation by Application

We plan to use the pages to document the process. Currently, most of these lead to empty pages.

Main Applications:

Tor Browser [ TODO ] [ current work ] [ history of changes ]
Orfox [ TODO ] [ current work ] [ history of changes ]
Orbot [ TODO ] [ current work ] [ history of changes ]

Other applications:

Tor Messenger [ TODO ] [ current work ] [ history of changes ]
TorBirdy [ TODO ] [ current work ] [ history of changes ]
GetTor [ TODO ] [ current work ] [ history of changes ]
Ricochet [ TODO ] [ current work ] [ history of changes ]
OONI [ TODO ] [ current work ] [ history of changes ]



Tor-Specific Resources & Guidelines

General UX Design & Usability-Research Resources

Want to know how to run a sound user test? What should your pipeline look like from problem identification to pushing new features?

One place to start is this list, which was developed as a self-start guide for attendees of the Internet Freedom Festival. Another is this guide on how to run a valid user study: Towards robust experimental design for user studies in security and privacy.