Skip to content


Applications Team

About us

Welcome to the Applications Team wiki page. The Applications Team is a group of Tor people who are working on different user facing products like Tor Browser.


The people who are part of this team is anyone working on the projects described above. We're not listing names here to keep the team open to everyone. This team also has the participation of user support and localization team members and members of other teams that give support to the Application team efforts.

You're on the team if you're participating in discussions and development, and you're not part of the team anymore if you decide you want to move on (which we hope won't happen).


Just go to #tor-browser-dev, and somebody from the team might either be around or appear later and get back to you. You can use the tbb-team alias for getting the attention of someone on the team (many of us have added this specific keyword so it highlights us).

We use ​IRC for our meetings, we meet on the ​OFTC network. We use a meeting pad to take notes each meeting.

Team meeting UTC CET
Primary team meeting Monday 15:00 Monday 16:00


In Q1 and Q2 the App's team will focus on improving the overall user experience of Tor Browser with ESR updates and connect assist for Android. In the secon

  • Tor Browser Desktop UX 
  • Connect Assist & Connection Settings for Android 
  • Onion error reporting
  • Tor Browser maintenance (bugs fixing, periodic rebases, etc
  • NoScript maintenance and/or new features
  • ESR Update
 starting on time
  • Improve Browser from feedback from users
  • "Tor VPN" implementation
  • Improve QA process for To Browser
  • Tor Browser refactoring
  • Sustainable release process
  • Automated testing system in place (esp for non-linux platforms)

Previous priorities.

Roadmap for Q1 and Q2 - January to June 2024

Sponsor 131 

  • Letterboxing/Betterboxing
  • Installers for Windows/Linux
  • Third party apps external links  
  • OpenH264 Build Reproducibility 

Sponsor 96

  • Tor Browser Desktop UX

Roadmap for Q3 and Q4 - July to December 2024

Sponsor 101 - VPN

  • Transitioning the product to the Application's team

Sponsor 131

  • Priorities to be aligned

Active Sponsor Projects

Triaging Tickets

We are triaging tickets once a week (Bella and Richard) .

The criteria to include tickets in a specific milestone are:

  • bugs that must be fixed (include security, regression or crash bugs)
  • tickets that have been road-mapped before because they are part of a sponsored project
  • tickets that are very fast to fix (around 1 hour)

The process we are using for triaging tickets is:

  1. filter out all tickets not in the milestone sorted by creation date
  2. for each new ticket:
  • add related labels (for example add an UX label to tickets that needs UX/UI help and the same for other teams)
  • if it fits the criteria written above then add it to the right milestone

Becoming a volunteer

The best way to get involved is to visit our weekly IRC meeting (see above). Tell us your background and interests and we will find a project for your to get started.