UX for bookmarks and history import

VERIFIED FIXED in Firefox 11



Firefox for Android
6 years ago
5 years ago


(Reporter: blassey, Assigned: gcp)



Firefox 12
Dependency tree / graph

Firefox Tracking Flags

(firefox11 fixed, firefox12 fixed, fennec11+)



(4 attachments)

Comment hidden (empty)


6 years ago
Assignee: nobody → madhava
Priority: -- → P2
Is this about a UI for importing bookmarks and history from the native browser?

Or is this about getting bookmarks/history in from an existing version of XUL Fennec? So for the user who is "updating" to Fx11, they have all their stuff?
Oh, bug 710330 blocking this one gives me a clue.
Simplest idea of all -- we could do a splashscreen that says "Setting Up Firefox" (as we used to) to give people an idea that this is a one time thing.

CCing in Matej and Martell to see if there's anything from brand that we'd want to use to amuse or communicate to people about while we're at it.

Comment 4

6 years ago
As much as I love injecting personality into the product where possible, I think this might a time where we just want to be short, sweet and really clear. +1 to "Setting Up Firefox" (unless we want to add something like "...for maximum awesomeness," but that's not going to be very l10n friendly).
So lazy. By which I mean thank you for your considered opinion. :)

OK - simple and straightforward it is.


6 years ago
tracking-fennec: --- → 11+
Created attachment 588925 [details]
splash screen

just nice and simple. I'll post some logo assets soon. 

(the background is the same that is used in the tab menu, and the spinner is just the normal spinner)
Created attachment 589522 [details]
Specs for splash screen
Here's a link to the logo assets http://dl.dropbox.com/u/2182500/Mozilla/splash-screen-logos.zip

This should be ready for implementation now

Comment 9

6 years ago
This smells like it's adding a string?

Comment 10

6 years ago
It's not, we can reuse R.string.splash_firstrun.

Comment 11

6 years ago
Created attachment 590673 [details] [diff] [review]
Patch 1. Code for the Setting up screen uX

Implementation of the described UX. I will actually use this for bug 713283, as far as I understand the UX experience there should be identical to this one.

It will delay displaying itself by 100ms to avoid flicker if the operations complete very quickly.

I noticed 
which we probably don't actually use in Native Fennec? We can probably remove them then?
Assignee: madhava → gpascutto
Attachment #590673 - Flags: review?(mark.finkle)
Comment on attachment 590673 [details] [diff] [review]
Patch 1. Code for the Setting up screen uX

Looks good, and yes we can remove the "splash" assets from native fennec.
Attachment #590673 - Flags: review?(mark.finkle) → review+

Comment 13

6 years ago
Created attachment 590683 [details] [diff] [review]
Patch 2. Remove unused splash screen assets
Attachment #590683 - Flags: review+


6 years ago
Blocks: 713283
Some of the initializations are done in onCreate(). I feel those can be specified in XML file instead. It is costly to assign in java usually.

Comment 15

6 years ago

Pushed with some more stuff moved to XML.


6 years ago
Attachment #590673 - Flags: approval-mozilla-aurora?

Comment 16

6 years ago
Comment on attachment 590683 [details] [diff] [review]
Patch 2. Remove unused splash screen assets

[Approval Request Comment]
Required for improve profile migration.
Attachment #590683 - Flags: approval-mozilla-aurora?
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 12

Comment 18

6 years ago


6 years ago
status-firefox11: --- → fixed
status-firefox12: --- → fixed
Comment on attachment 590673 [details] [diff] [review]
Patch 1. Code for the Setting up screen uX

this already landed because of a miscommunication over irc, giving it approval post-landing
Attachment #590673 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment on attachment 590683 [details] [diff] [review]
Patch 2. Remove unused splash screen assets

this already landed because of a miscommunication over irc, giving it approval post-landing
Attachment #590683 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+

Comment 21

6 years ago
If possible, I'd like to ask we reconsider this UX. While we'll do what we can to keep migration times <1 minute, that's still fairly long. Secondly, for users with large numbers of bookmarks (more than a few hundred), or slow phones (specially if we get ARMv6 in), we can't really predict how long they are going to see this screen, but it might be considerably longer.

The experience would probably be improved if we can show, instead of "Setting up Firefox...":

1) Importing bookmarks: x out of y
2) Importing history: x out of y
3) Importing favicons: x out of y
[4) Importing passwords: x out of y]  <- we don't do this yet

a) Informs the user what is actually happening.
b) Will show progress, removing the impression the browser is stuck here forever.
c) Helps understand that this is really a one-time event on first start.
d) Alerts the user that it restarts if they close Fennec (either directly or by exiting and starting many other apps).

I know l10n will be thrilled by the idea of new strings, but I figure I'd rather bring this up now (and maybe not need it in the end if we can get the migration fast enough), rather than leave it be and panic at the last minute when we see some users with tons of bookmarks are getting a terrible experience.

Maybe we can do:
line1: Setting up Fennec...
line2: Bookmarks (x/y)

The new string impact of that should be small or nonexistent (might not have a string for favicons yet).

Comment 22

6 years ago
I agree with gcp here - we've taken enough beating from XUL version users on the startup logo screen, we even heard statements like "I hate this Firefox logo". When we do something similar on the first startup, which is the first impression we make on the user, then this is quite bad. If we tell the user explicitely what they need to wait for, this impression will hopefully be totally different.
Let's open a new bug for UX improvements here. I think we need to find a compromise between:

- reducing the overall time required
- making the time we can't cut less visible (i.e. on demand; hidden while something else is happening; other)
- where we can't hide it, distracting the user more (i.e. progress, or having some other conversation with them)
- making it clear that this is a one time thing

Just providing more detail isn't necessarily going to make for a better experience.

I opened Bug 729532 - Improve first-run profile import experience
UI updates when importing bookmarks and history were already landed since some versions ago. Closing bug as verified fixed.
You need to log in before you can comment on or make changes to this bug.