Closed Bug 477109 Opened 14 years ago Closed 14 years ago

better explanatory first-run page


(Firefox for Android Graveyard :: General, defect)

Not set



Tracking Status
fennec 1.0+ ---


(Reporter: madhava, Assigned: Gavin)




(2 files, 3 obsolete files)

The current first-run page works for people who are really paying attention, but could be made better for people who just want to get on with browsing.  Part of the solution could be to make it more eyecatching, but I also suspect that a more visual explanation than arrows with text to read would be useful.  I'm doing some thinking about this and will comment more soon.
Blocks: 477628
tracking-fennec: --- → 1.0b2+
tracking-fennec: 1.0b2+ → 1.0+
Are we considering the animated GIF solution? "shows control bars and then slides them out"
Assignee: nobody → madhava
As best as I can tell no one actually understands our first run page, so I think we need something with text or something.
adding blocking on alt-text bug, as don't want to fix that until first-run is changed.  That old bug doesn't really apply anymore, but needs to be considered for any replacement.
Blocks: 472377
I think an actual quick little demo, possibly as an animated image, would be the best thing here. I'll work on this with martell.
Flags: in-litmus?
I'm assuming we need to get these strings in ASAP. This isn't styled, and is missing images, but is otherwise localizable (strings in context, etc.). Strings come from the mockup Madhava/Caitlin have been working on.

This just adds firstrun.xhtml to the normal browser content package, I didn't touch the other first run stuff yet. I think we'll need this page to be privileged, so we don't need to worry about having it in a contentaccessible package, so I think we'll just want to get rid of the old pages.
Assignee: madhava →
Attachment #398783 - Flags: ui-review?(madhava)
Attachment #398783 - Flags: review?(mark.finkle)
(In reply to comment #5)
> I think we'll need this page to be privileged

... to fill in the links based on prefs, just to finish that thought.
Attachment #398783 - Flags: review?(mark.finkle) → review+
Attachment #398783 - Flags: ui-review?(madhava)
Attached patch styling (obsolete) — Splinter Review
This adds the styling, an attempt to match .

Some issues:
- links just open the addons manager instead of pointing to specific pages (maybe we want to keep this?)
- I'm using just text rather than the "Welcome" image, since that isn't localizable. Need to add in an icon perhaps, and maybe make the text prettier.
- missing "skip all this" link, but could easily add it back and make it open the awesomebar
- the text is pushed offscreen by the animation, which makes it hard to discover (madhava and caitlin were working on some of alternative styling to address this, I think)
- has only been tested on desktop so far
- I'm concerned this will be a significant Ts hit, given taras' experiences with our previous first run pages. much more stuff to load (CSS/images/dtds) than we had before.
some more polish:

- we need to add the "play again" symbol to the end of the animation (I'm getting this)
- working on revising the layout so the content after the animation will be findable by the user
Attachment #402494 - Flags: review?(mark.finkle)
Depends on: 518714
Depends on: 518719
Depends on: 518728
(In reply to comment #8)
> - I'm using just text rather than the "Welcome" image, since that isn't
> localizable. Need to add in an icon perhaps, and maybe make the text prettier.

bug 518728 - going to just use the banner image for now

Also patched other issues madhava pointed out in bug 518719 and bug 518714.
Comment on attachment 402494 [details] [diff] [review]

>-function showDownloadsManager(aWindowContext, aID, aReason) {
>-  BrowserUI.switchPane("downloads-container");
>-  // TODO: select the download with aID

This was supposed to be used by the downloadManagerUI.js component, but the damn function is spelled wrong. Should be showDownloadManager

>diff --git a/chrome/content/firstrun.xhtml b/chrome/content/firstrun.xhtml

>-<!--  <link rel="stylesheet" href="chrome://global/skin/about.css" type="text/css"/> -->
>+  <link rel="stylesheet" href="chrome://browser/skin/header.css" type="text/css"/>
>+  <link rel="stylesheet" href="chrome://browser/skin/firstRun.css" type="text/css"/>

firstrun no longer has a favicon? 

>diff --git a/themes/hildon/firstrun/favicon-fennec-30.png b/themes/hildon/firstrun/favicon-fennec-30.png
>deleted file mode 100644


The images and animation in here are enormous. Can we try to reduce them using smaller color depth or removing any color profiles?

Also, can we convert the png files to gif? Taras found that png files load very slowly on the N810.

r+, but let's see if we can do some things to reduce the image sizes and I think the favicon should be kept, don't you?
Attachment #402494 - Flags: review?(mark.finkle) → review+
Favicon should definitely be kept (using the fennec one until 1.0).

I can ask Sean about how to reduce the size of the animation - not much color used anyway.

I can't seem to save out a GIF with proper transparency.
New smaller (now in 8 color) animation here:
Attached image New Weave Graphic (obsolete) —
Attached image New Add-ons Graphic (obsolete) —
Attached patch updated stylingSplinter Review
Includes the latest images (weave, addons, firstRunAnimation), and restores the favicon.

Madhava and Sean were discussing removing the blue header background, but this doesn't do that yet. Still need a couple of image tweaks though so we can revisit that.
Attachment #402494 - Attachment is obsolete: true
Attachment #403885 - Attachment is obsolete: true
Attachment #403887 - Attachment is obsolete: true
Pushed that:

will file some followup on the remaining tweaks.
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → B5
verified FIXED on builds:

Mozilla/5.0 (Windows; U; WindowsCE 5.2; en-US; rv:1.9.2b1pre) Gecko/20091006 Fennec/1.0a3


Mozilla/5.0 (X11; U; Linux armv6l; en-US; rv:1.9.2b1pre) Gecko/20091006


Mozilla/5.0 (X11; U; Linux armv7l; en-US; rv:1.9.2b1pre) Gecko/20091006
Litmus testcase takes care of testing the strings on the firstrun page.
Flags: in-litmus? → in-litmus+
You need to log in before you can comment on or make changes to this bug.