Changes between Version 34 and Version 35 of doc/TorLauncherUX2016


Ignore:
Timestamp:
Feb 9, 2017, 9:37:42 PM (2 years ago)
Author:
lnl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/TorLauncherUX2016

    v34 v35  
    77Users take more than 10 minutes to connect to Tor if the public relays are censored and 50% of the users cannot connect to Tor if the interface’s hardcoded bridges are censored. The suggested design changes saves users a lot of time--over 20 minutes if they are in censored environments that censor hardcoded bridges.
    88
    9 Designing changes was especially challenging because of atypical, Tor-specific design considerations. You might think that it would be easiest for the user if the process of setting up the connection to Tor was completely automated, and you're right. But it doesn't account for the fact automating the process can put some users at risk or that the relays that work in almost all countries are magnitudes more expensive and limited in capacity (to name a few reasons).  Anyone interested in doing UX work for Tor would especially benefit from reading about these considerations.
     9Designing changes was especially challenging because of atypical, Tor-specific design considerations. You might think that it would be easiest for the user if the process of setting up the connection to Tor was completely automated, and you're right. But it doesn't account for the fact automating the process can put some users at risk or that the relays that work most reliably are magnitudes more expensive and limited in capacity (to name a few reasons).  Anyone interested in doing UX work for Tor would especially benefit from reading about these considerations.
    1010
    1111People: