[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #27484 [Applications/Tor Browser]: Onboarding: unintuitive not-navigation buttons, starting with "Circuit Display" / "See My Path"
#27484: Onboarding: unintuitive not-navigation buttons, starting with "Circuit
Display" / "See My Path"
-------------------------------------------------+-------------------------
Reporter: dmr | Owner: tbb-
| team
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-8.0-issues, tbb-onboarding, ux- | Actual Points:
team |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by mcs):
Replying to [comment:8 antonela]:
> Yes, since there is no call to action on the first screen, the user
intuitively goes to the left menu or close it. BUT! Not finding a call to
action can confuse users. The problem is usually defined as "I arrive here
and I don't know what to do/click". Perhaps, Firefox folks did it
intentionally so people don't need to take action but read.
That may very well be the case. I think the problem that dmr is pointing
out is that the first few onboarding screens teach people that the right
side button is for navigation, but then we change the behavior and we have
not taught them how to navigate between onboarding steps.
> We included the right-next buttons because in that way the navigation
seemed more fluid for new users. The first three panels host very
important knowledge for new users. We really want to have users reading
it. Very different than the other three steps, which hosts advanced
technical information.
>
> We could solve it by
> a. removing [next] buttons at the right side so we force users to
navigate with the left menu.
> b. being explicit about what we are going to open is a new tab.
My vote would be for a. (remove the [next] buttons). Another possibility
would be to add explicit `Next` buttons (so some panels would have two
buttons and some would just have `Next`).
> for 2.
> I know that could be ideal to trigger/open a circuit display when the
user clicks the button, but since we are in `about:tor`, we don't have a
circuit and fake it is not smart.
>
> Since it is not possible, something that came to my mind is what would
go wrong if we open the doorhanger when the user visits their first site,
and we prompt the useful circuit display onboarding.
> So, instead of launching it for duckduckgo, it launches for any first
site that gets open.
>
> The user flow will look like (for first time or just updated users):
> - user lands in `about:tor`
> - user opens a new tab / writes a URL at the URL bar
> - the circuit loads, the page loads, the doorhanger prompts and the
circuit onboarding step 1 appears.
>
> mcs it is possible? could we prompt the circuit onboarding on the first
visited site? what would be wrong if we do it?
This would be difficult to implement because Kathy and I would rather not
invoke the onboarding code for arbitrary sites (the implementation is tied
to Firefox's URL-based permissions model). From a UX point of view, it
might also be too intrusive and/or confusing to interrupt people's work in
this way.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27484#comment:9>
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