First-run startup time is much longer than regular app startup given that Firefox is creating your profile (and other things?). Right now, on our splashscreen, we still show the "Loading" string.
Instead, for the duration of the activities that don't happen every time, we should say, instead, "Setting up Firefox" (or Fennec).
This should make it clear that what users are experiencing isn't what they will experience in the future.
Maybe we could show a message "preparing first run" or similar when users start the mobile browser for the first time after installation. I wonder though what happens after you deactivate and re-activate sync or delete your user data - I expect slower startup after these actions
2,0-, but we'll take a patch for this
Created attachment 532497 [details] [diff] [review]
Comment on attachment 532497 [details] [diff] [review]
i do not understand the difference between:
Maybe instead, we should have a more dynamic splash screen on firstrun/installation, that shows a progress bar (maybe bad for performance), or a set of strings that we cycle through when we install:
preparing for installation
(In reply to comment #4)
> Comment on attachment 532497 [details] [diff] [review] [review]
> i do not understand the difference between:
you can look at the dtd to get the strings
> Maybe instead, we should have a more dynamic splash screen on
> firstrun/installation, that shows a progress bar (maybe bad for
> performance), or a set of strings that we cycle through when we install:
yup, bad for performance
> preparing for installation
> installing libraries
> creating profile
> optimization installation
that's not what madhava specified
I don't want to add more jargon-filled detail. The point here isn't to explain exactly what's going on to the user; instead, we're simply trying to make the point that the wait they're experiencing is not something that will happen every time.
We can try other things to give more of a sense of activity (as Doug is suggesting), but I think the "Setting up Firefox" string is helpful on its own.
Verified fixed on Firefox 6 Beta 2: Mozilla /5.0 (Android;Linux armv7l;rv:6.0) Gecko/20110713 Firefox/6.0 Fennec/6.0
Device: LG Optimus 2X (Android 2.2)