[Fx4Launch] Redesign Firefox Sync welcome page to drive mobile sync setup

VERIFIED FIXED in 1.4

Status

www.mozilla.org
General
P1
normal
VERIFIED FIXED
8 years ago
6 years ago

People

(Reporter: Caitlin Looney, Assigned: sgarrity)

Tracking

unspecified

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
This is the current welcome/first run page for Firefox Sync:
http://www.mozilla.com/en-US/firefox/sync/firstrun.html

After speaking with the Sync, Mobile and Desktop team, we've identified low
hanging fruit to cross promote mobile and drive sync setups on other platforms.
(We currently have 625k sync adus on desktop and 3k on mobile.)

We'd like to aim for this page to go live on or before Firefox 4 for mobile
final release (mid-March). 

Here's the link to the copy:
https://docs.google.com/document/d/188_iXGCfOc4-F80O19kbH6ZBwe7lc22Zn_cOsRkwxOE/edit?hl=en&authkey=CLuo3asH

We really want this page to be visually hard-hitting and apparent that you can
set up Firefox Sync on your mobile/across multiple devices.
(Reporter)

Updated

8 years ago
Priority: -- → P2
Target Milestone: --- → 1.3

Updated

8 years ago
Summary: Redesign Firefox Sync welcome page to drive mobile sync setup → [Fx4Launch] Redesign Firefox Sync welcome page to drive mobile sync setup

Updated

8 years ago
Assignee: nobody → jslater

Comment 1

8 years ago
John - Perhaps we design this page during the 1.3 release time-frame, then implementation during 1.4.

Updated

8 years ago
Target Milestone: 1.3 → 1.4
(Reporter)

Comment 2

8 years ago
When is 1.4?

Comment 3

8 years ago
(In reply to comment #2)
> When is 1.4?
Launches Tuesday, March 8.

Comment 4

8 years ago
John - Has creative work started on this page? If the final mobile release ends up being approx 3/22 then it would be great to have these assets finished by 3/15, giving dev 1 week to implement.
Summary: [Fx4Launch] Redesign Firefox Sync welcome page to drive mobile sync setup → [Fx4MobileLaunch] Redesign Firefox Sync welcome page to drive mobile sync setup
(Reporter)

Comment 5

8 years ago
It has. I think we've signed off on the design. Launching sooner (1.4 or March 8) would be best as there is a Sync usability study kicking off that day.

Comment 6

8 years ago
Design is happening over in bug 628773. It's basically finished...will close that one out as soon as Sean posts the files.

Laura, do we have a dev resource for this yet?
Depends on: 628773

Comment 8

8 years ago
Great - Steven - can you guys help out here? 3/8 seems to be the desired launch date but since this isn't tied to the Fx4 Desktop release it should be prioritized accordingly.
Assignee: jslater → steven
OS: Mac OS X → All
Hardware: x86 → All
(Reporter)

Comment 9

8 years ago
Thanks. Looks great.

Comment 10

8 years ago
Making this a P1 to see if we can get it into 1.4 (as it ties into Sync, which is a key Fx4 desktop feature). Steven, if work on this looks like it will jeopardize other bugs please let me know asap and we'll consider pushing it to 1.5.
Severity: major → normal
Priority: P2 → P1
Summary: [Fx4MobileLaunch] Redesign Firefox Sync welcome page to drive mobile sync setup → [Fx4Launch] Redesign Firefox Sync welcome page to drive mobile sync setup
(Assignee)

Comment 11

8 years ago
This redesign is in place in the Fx4 branch (r84849).
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Keywords: qawanted
Resolution: --- → FIXED
Created attachment 519186 [details]
screenshot

reopening  as this is broken in IE6
(In reply to comment #12)
> Created attachment 519186 [details]
> screenshot
> 
> reopening  as this is broken in IE6

ignore comment as this is in in product page 

qa-verified-stage http://www-fx4.stage.mozilla.com/en-US/firefox/sync/firstrun.html
Keywords: qawanted
verified fixed http://www.mozilla.com/en-US/firefox/sync/firstrun.html
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.