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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#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-a2  |  Actual Points:
Parent ID:  #28051                       |         Points:
 Reviewer:                               |        Sponsor:
-----------------------------------------+--------------------------

Comment (by sysrqb):

 Replying to [comment:5 antonela]:
 > hello! I made a first approach to this task:

 Thanks!
 >
 > I know that the current .apk is just a glued version, but is cool to
 have it as a reference to think about how to improve it.

 I have a new version available now :)

 http://sbe5fi5cka5l3fqe.onion/~sysrqb/fennec-60.3.0.en-US.android-
 arm_28051_1.apk
 https://people.torproject.org/~sysrqb/fennec-60.3.0.en-US.android-
 arm_28051_1.apk

 Orbot now works (or it should work, let me know if it doesn't). I removed
 the onboarding screens due to some coding issues, but we'll have new
 onboarding screens in any case. After Tor starts, the user must tap the
 back button to return to the browser. If the user's device is not running
 the newest version of Android, then they should have a notification that
 says Tor Browser in the drop-down list, and they can return to Orbot using
 that. We have a problem on the newest version of Android, so the
 notification isn't created and there isn't a way for the user to re-open
 Orbot except for killing the app and restarting it.

 >
 > The current First Time User flow looks like
 [snip]
 >
 > I drafted a first version of an improved flow. On the big picture, it
 includes a bridge configuration step and removed the VPN settings. Also, I
 merged the `privacy` and `tor network` steps from the current onboarding
 into this bigger flow.

 Yes, that looks good! I don't think we should say anything about the VPN
 mode (and we'll probably remove that in the future).

 [snip]
 >
 > I have questions for the Tor Network Settings in TBA. I see four options
 for config bridges at orbot now:
 >
 > - Connect directly to Tor (recommended)
 > - Connect through community servers
 > - Connect throught cloud servers
 > - Request New Bridges.... (If all else fails)
 >       Bridge Mode
 >               Website
 >               Cancel
 >               Email
 >
 > What is the plan for them? Are we going to carry all of them? Will MOAT
 work in TBA?

 Yes, I don't know a reason why we wouldn't want Moat available in TBA. In
 fact, I think Moat provides an even better experience on mobile than on
 desktop. But, considering Orbot doesn't currently have support for moat, I
 think we should add it as a follow-up ticket for this, and we can
 implement it soon (but later).

 > Do we want to have a similar Tor Launcher UX?

 I think we should use the better UX :) (whatever that is)

 I think using the Tor Launcher UX is the simplest answer and it provides a
 consistent experience across desktop and mobile, so that is a good option.
 On the other hand, (saying the obvious) mobile provides a different UX
 than desktop, so creating a new experience that is mobile-specific may be
 better. I'd be happy with choosing the easy/simple option now, and we can
 iterate on it over the next few months.

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

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs