Tor Browser Android Onboarding Plan
We want a plan for onboarding in Android. Mozilla did a big refactor in 113 and 114 to theirs. I've captured what it looks like in the attached screen shots. It's flow is:
- single page asking about notifications
- onboarding "cards" page with settings for
- dark/light theme
- url bar placement (top/bottom)
- sync / signin
- Privacy / "Total cookie protection"
- link to privacy policy
large screen shots
Apparently Desktop onboarding in torbrowser just asks about Security Level right now
Designs
- tor-browser-build #40927
- tpo/ux/design #155
Activity
added 13.0 stable 13.5 stable Android labels
marked this issue as related to #41878 (closed)
marked this issue as related to #41972 (closed)
mentioned in issue #41972 (closed)
added Meta label
removed 13.0 stable label
@donuts I screen shotted and descrtibed what moz115 is doing now, what I'm disabeling in our 13.0 android
further dev notes:
The onboarding is multipart
The cards main area is generated by onboardingFragment
But the first full page popup question about notifications is from: action_global_home_notification_permission_dialog / homeNotificationPermissionDialogFragment
Edited by Dan Ballard
i have not seen our custom onboarding popup. can you point me to the ticket where it was added so i know what to look for and can try and track down what happened to that code?
It may have happened on trac, I'm not sure. It's the content @pierov is alluding to above. It appears on the home page after bootstrapping and is notoriously hard to screenshot because it clears after you open settings to allow screenshots.
-
found it
large screen shots
and yeah no that's not triggering in 13.0 and I have pretty good ideas why, they blew up ours and their onboarding flow and our code clinging to the old flow is broken all over, it's why I'm doing the big bootstrap refactor.
created #41992 (closed) to track
Edited by Dan Ballard
-
My current thinking for 13.5 would be reenable onboarding, pull out the nimbus parts, pull out the parts we dont want "light/dark mode" and add our security level. The onboarding as you can see from the pics above is pretty modular on some card system they are using.
The actual question here is, should onboarding be before or after bootstrap? it has been suggested that is confusing, and certainly with the existing end button text "start browsing now" it is, but logically, I don't see any reason it should go after bootstrap, it doesn't depend on tor, and if we later put any first pick config options in it (one day bridges) it should def come first? just with better text guidance? or at least that's my thinking. Acknowledging that currently since we embed it on the default homepage it comes after bootstrap, but that seems more a result of a hack? or was it preferred?
The reason for which it's confusing before the bootstrap is that it makes the URL bar available.
So, we should at least hide the URL bar if we want to onboard before the bootstrap.
I was extremely confused by being able to write a URL, and than having a proxy failure. I thought the bootstrap was still broken.
My test device is old, and still on a 16:9 aspect ratio, so the start browsing button is down and requires me to scroll to notice it (I expect not to be the only impatient user
On desktop we solved by hijacking to
about:torconnect, but on mobile we should really hide the URL bar imho.Apart from that I don't have a strong opinion about having it before or after (after is what we've always done: maybe the reason is that once you've bootstrapped, you can do whatever you want, you're not forced to go through the onboard and then have another compulsory step).
-
Sounds great! I'm in favor of this plan if we can hide the URL bar as @pierov suggests, and also patch the button to something a little more accurate – e.g. "Get started"?
Maybe there's a similar generic string in translation memory we can use.
-
Tagging @jag here too as they're currently working on Android, and the prospect of UX changes is maybe happening.
-
reviewing #42004 (closed) actually raises a good point. onboarding can have links to detail pages like privacy policy. we might remove the moz one or not or add our own? but it's a clear point in the column of bootstrap first, onboard second. and which ever way we do it, we should inspect this behaviour it doesn't act as a proxy leak or just fail when it gets added back in
-
Would it be helpful for @jag to visualize what we've discussed? We'll need to update our Figma library with the changes anyway.
mentioned in issue #41878 (closed)
mentioned in merge request firefox-android!10 (merged)
-
For who ever does the work, we're deleting the existing unhooked up code for the moment in the linked to commit
and it was originally added in
So use those as reference for what's needed when readding
added Roadmap::Future label and removed Backlog label
marked this issue as related to #41992 (closed)
marked this issue as related to tor-browser-build#40927 (closed)
marked this issue as related to tor-browser-build#40965 (closed)
removed the relation with tor-browser-build#40965 (closed)
marked this issue as related to #41335 (moved)
assigned to @jag
removed Roadmap::Future label
added Backlog label
mentioned in issue #41847
added UX Team label
unassigned @jag
-
I think we should repurpose Fx's onboarding, with the following changes:
Remove:
- Theme (potentially? It's confusing that it doesn't visibly change in this context)
- Sync
- Privacy protection
- Privacy policy
Keep:
- Notifications
- Toolbar
- Start browsing button
Add:
- Security level (from Tor Browser)
Update:
- Notifications illustration
- Notifications copy
- "Welcome..." copy (at top of second screen)
- "Ready..." copy (at bottom of second screen)
Tagging @nicob for a new illustration, although I think I know which one we're going to use here :)
assigned to @dan
mentioned in issue #41992 (closed)
-
Ok I've been playing around with firefox-android onboarding. They added a new systems, called Juno, in 2022, that appears to be for new users?
Juno / Global Onboarding screen shots
How ever as best I can tell from comments and reading moz bugzilla issues, they are keeping the card based "home onboarding" for "existing and upgrading" users? I cannot find any evidence that it's to be removed before ESR 128. So I'll proceed with using that for now.
-
I'm personally not a huge fan of the new full page Juno/Global onboarding because it appears to be very rigid and lock us into just two button questions which is sub optimal for things like Security Level. It has been pointed out if we are later forced to this system we could have one of the buttons be like "go to security level settings".
Lets hope moz keeps the "home onboarding" card interface around for a while longer
-
So it would appear the cards system has been removed and replaced with the above screen shotted fullscreen onboarding system, it just exists in multiple places in the code, the juno one is a nimbus powered version, but the other version has been restyled to be the same, just more fixed in code. I'll quickly try and mock out an experience we want with the above edits to the selection of topics, and adding one new one that just takes us to security level as has been suggested to get some feedback since I know ux is a bit over subscribed
-
As per irc: moz's constantly changing onboarding and the desire to sync with desktop means ux will take one pass at a unified onboarding and for firefox we'll prolly abandon what ever moz is doing and roll our own. for the security level question at this point that'll be a big win as their onboarding format is too narow (two buttons, one is skip)
removed 13.5 stable label
removed Doing label
