wiki:org/teams/UxTeam

Version 13 (modified by lnl, 22 months ago) (diff)

--

UX Team

Overview

Welcome to the UX team. The UX team is a multidisciplinary group of people who cares about UX for privacy and security tools. There current other 4 teams part of Tor: Metrics Team measures and analyses things in the public Tor network, Network Team writes the software to keep the Tor network running, the Applications Team produces usable applications for end users, and the Community Team focuses on the non-technical aspects of growing a healthy Tor community.

Objective

To help end users by building intuitive and aesthetically appealing interfaces without sacrificing security or technical functionality.

People

User Experience is always a multidisciplinary effort, it involves designers, user researchers, data analysts, localization and internationalization specialists, UI engineers, and more! Is the collective contribution of all these skills that helps understand the user and build the best experience for them. We're not listing names here to keep the team open to everyone. You're on the team if you're participating in discussions and development, and you're not part of the team anymore if you aren't. =

Resources

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

(TODO) In this section, there will be resources that teach you the basics of user experience, user interface design, and user research techniques.

Logistics

Projects

org/meetings/2015UXsprint: January 2015 meeting, live usability testing of download, install, configuration, and basic usage such as web searching and New Identity. Summarized in a HotPETs 2015 paper. See also:

doc/TorLauncherUX2016: Usability testing and design of Tor Launcher under simulated censorship.

Communication

Reaching Us

The best way to contact us is by email.

Purpose Contact Information Archives
General Communication UX mailing list (archives)
Suggestions for Improving Products N/A N/A
Advice on Improving Your Product N/A N/A
Research Discussion N/A N/A

Collaboration

  • with other developer teams: We plan to regularly communicate with the other teams in order to ensure that what we are doing is useful, deployable, and does not sacrifice important functionality. We have not yet set up an official channel of communication or a regular time for communication, but we realize the importance of this.
  • with other researchers: We welcome any researchers who would like to collaborate with us! We have a need in many of our products. If you want to collaborate with us on a particular aspect of the user experience, assess a particular product, or want to know how to get involved, contact us to talk.
  • across multiple products: The vision for the UX team is to have a centralized team that designs for the user experience in a consistent manner across all the different products that Tor offers. Ideally, we would love to have a person who is responsible for continuous research, testing, and maintenance of each Tor product, but have team-wide communications across all these members so that there can be consistent design, text, images, and feedback for users across products.

Documentation by Product

We are attempting to organize our work by product for the sake of organization. Currently, there isn't anything at the links provided below, but the wikis exist and are begging to be filled out. If you hear any suggestions for improving the user experience in a Tor product, please fill in the TODO wiki. If you are doing any current work on a particular product, detail the work you are doing in the corresponding product's current work page.

We plan to structure the team in a way that there is a point of contact for improving the UX of each product; when that happens, their contact information will be listed below. Until then, contact us for everything and anything at the UX mailing list.

Application Products

Product Documentation Main Contact
Tor Browser [ TODO ] [ current work ] [ history of changes ] N/A
Tor Messenger [ TODO ] [ current work ] [ history of changes ] N/A
Tor Mail [ TODO ] [ current work ] [ history of changes ] N/A
Get Tor [ TODO ] [ current work ] [ history of changes ] N/A
Ricochet [ TODO ] [ current work ] [ history of changes ] N/A
Orfox [ TODO ] [ current work ] [ history of changes ] N/A
Orbot [ TODO ] [ current work ] [ history of changes ] N/A
OONI [ TODO ] [ current work ] [ history of changes ] N/A

Other

Usability doesn't just need to be for the end user. Streamlining the workflow for internal tools and development tools can greatly speed up the learning process for developers, ease the burden of developing, and prevent bugs before they happen.

Archives

History of changes

(Notes from 2015-02-09 IRC meeting.) simple: problem, hypothesis (what we tried), solution. I am thinking of grouping these by phases of the user path, so the animations can be part of 'awareness' group.

Tor Browser Bundle 3.5 introduces Tor Launcher.

Tickets

  • #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.