Usability testing of Figma prototype on multi-path circuits
Context
Multi-path circuits (aka. Conflux) is a feature that enhances reliability and performance by splitting traffic across multiple circuits at the same time and prioritizing circuits with lower latency.
Right now:
- On desktop, Tor Browser only displays single-path circuits.
- On Android, Tor Browser has no circuit display at all.
Design
- Desktop
- Android
- Study on circuits
Timeline
At best, this feature will be implemented in Tor Browser 16.0, not before June-July 2026. We're aiming at handing over finished designs by the end of 2025.
- September
- October
- November
- Week of November 3:
-
Analyze
-
- Week of November 10:
-
Analyze
-
- Week of November 17:
-
⚠️ Tails Sprint -
Report
-
- Week of November 24:
-
Report
-
- Week of November 3:
- December
Research goals and questions
-
Test the basic version (no bridge + no onion service) of the new circuit display for single-path and multi-path circuits on both desktop and Android, before we hand it over for development.
-
Discoverability
- Do users know where to find the circuit display?
- Even more important for Android users since there is no circuit display right now on Android.
- Use of the circuit icon instead of the shield icon with UTP.
- Do users know where to find the circuit display?
-
Usability
- Is it intuitive for users to switch between the view of each path?
-
Understanding
- Do users understand that websites using multi-path circuits are using the different paths at the same time?
- Do users understand that the same exit relay is used in multi-path circuits?
- Do users wonder about the implications of Tor Browser using a single-path vs. a multi-path circuit?
- Do users wonder about the benefits or disadvantages of both?
- Do users wonder about when Tor Browser chooses one or the other?
- Do users wonder about how to change between one and the other?
- Do users understand the relay terminology? (#148)
- Otherwise, how might we improve it?
- What questions do people have when opening the "Learn more" link? (not written yet)
-
-
Test the new circuit display within Firefox's new Unified Trusted Panel (UTC).
- Do the other elements of the UTP interfere with the circuit display?
Out of scope
-
Test variants of the new circuit display
- Onion sites
- Multi-path won't work yet with onion sites.
- Bridges
- Onion sites
-
Accessibility
- Is the new circuit display accessible for screen reader users?
Participant recruitment
Duration
Limit ourselves to 1 hour: not a lot of different things to test + remote + questions more than tasks.
Number of participants
We won't test both desktop and Android with the same participant (between-subjects study), because the interfaces are too similar.
- 1 pilot test
- @felicia wants to attend the pilot test, at least, and maybe some more tests as observer
- 4 participants for Android
- Ideally people who use Tor Browser on Android already
- 4 participants for desktop
- Ideally people who use Tor Browser on desktop already
Screening criteria
- Occasional and frequent users
- Location
- SIDA countries
- Time zone
- Language
- Prototype in English only
- Incentives: #182
Prototype
We'll use interactive Figma prototypes.
Interactions available right now:
- Open Tor Browser on Wikipedia page.
- Click on circuit icon.
- Get UTP with circuit display for single-path circuit.
- Click on "New circuit for this site".
- Get UTP with circuit display for multi-path circuit.
Methodology
Figma prototype
Ask participant to:
- Turn off "Advanced settings > Show hints on click"
- Turn on "Hide UI"
BBB
Moderator:
- "Make presenter"
Participant:
- Share screen
Deliverables
- Polished report using template from design#260 (closed).
Checklist
-
Design research -
Recruit -
Decide on session duration -
Decide on number of participants -
Discuss screening criteria -
Discuss incentives -
Schedule slots -
Create screening survey using template screener -
Review screening survey (@alicia) -
Test screening survey -
Send link to screening survey -
Schedule participants using screening spreadsheet -
Schedule 1 extra participant for no shows
-
-
Answer to all candidates using email templates -
Confirm only after sound check (if remote) -
Send research information sheet to participant when confirming location
-
-
Prepare prototype -
Prepare interactive mockups on Figma -
Test interactive mockups
-
-
Prepare tests -
Adapt research information sheet -
Adapt consent form -
Adapt checklist -
Explicit reset procedure -
Explicit recording procedure
-
-
Prepare recording setup -
Test the recording setup -
Check available disk space
-
-
Prepare incentives
-
-
Analyze -
Create rainbow table -
Mark new issues -
Document benefit -
Strike through solved issues -
Fill in demographics tab of rainbow table -
Link rainbow table from here: XXX
-
-
Create public report and link from here -
Prepare video clips -
Document on GitLab -
Create missing issues -
Document in existing issues as "### User research findings" -
Link all issues to this one -
Link related issues together -
Verify labels on all issues
-
-
Share highlights on tails-dev and link from here: XXX -
Prepare video clips
-
-
Wrap up -
Share results with project -
Share results with participants -
Save candidates in email database: https://nc.torproject.net/apps/onlyoffice/679614?filePath=%2FUX%20Team%2FUser%20Research%2FParticipants.xlsx -
Add to achievements.mdwn -
Reimburse incentives -
Improve checklist
-