[tor-bugs] #28329 [Applications/Tor Browser]: Design TBA+Orbot configuration UI/UX

Tor Bug Tracker & Wiki blackhole at torproject.org
Thu Jan 10 14:22:41 UTC 2019


#28329: Design TBA+Orbot configuration UI/UX
-------------------------------------------------+-------------------------
 Reporter:  sysrqb                               |          Owner:  tbb-
                                                 |  team
     Type:  enhancement                          |         Status:  new
 Priority:  Very High                            |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-mobile, ux-team, TBA-a3,         |  Actual Points:
  TorBrowserTeam201812                           |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor8
-------------------------------------------------+-------------------------

Comment (by gk):

 Replying to [comment:16 antonela]:

 [snip]

 > For the unsuccessful scenario, we can take different paths:
 >      a - Have a retry button
 >      b - Suggest users to move to the Network Setting screen to config a
 Bridge
 >      c - Move the user to the Network Setting screen with a message
 about what failed and some encouragement on how to fix it.

 c) seems to me the best option from those three. a) I doubt users
 understand why we just give them a "Retry" button in case things failed.
 And why should things get fixed just by tapping that button after the
 first try already failed?  b) we could do that but we would move the user
 to the network settings anyway if they decided to tap the link, so we can
 do c) right from the beginning...

 > Do we have data about why bootstrapping fail in mobiles? Which are the
 most common failing cases?

 As far as I know we don't have that data.

 >
 > `3.0`
 > If users arrive here after a failed connection, the copy at the top will
 change to encourage users to take action to fix it. I made the first
 approach on this screen. My idea is to divide this section into two:
 Bridges and Advanced Settings. With this split, users are lead to tap the
 first option instead of start exploring options that they don't know what
 are.
 >
 > ---------
 >
 > **Network Settings**
 >
 > Since we want to have a balanced experience compared with desktop, I
 include the same options we have on the desktop. We'll not have moat for
 this version, so I skipped it.
 >
 > The user flow is the same for each option. Users can switch on/off each
 setting, and then we move them to a second screen where the configuration
 is made.
 >
 > When the user returns to the main network settings screen, they can see
 a status of the changes they made, at the description. If users want to
 change it, they can tap the entire row.
 >
 > The copy is up to review. Material Design has excellent suggestions
 about how to approach this copy https://material.io/design/platform-
 guidance/android-settings.html

 There is no firewall ports configuration for Tor Launcher on start-up.
 While this is confusing to some users I think this is currently the right
 choice for mobile users, too. (I think we'll eventually drop that option
 altogether on desktop). See: #24452 for some discussion.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28329#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list