[Firefox Aurora Branding] Implement: Firefox Aurora Page Optimized for Mobile

RESOLVED FIXED in 4.10

Status

P1
normal
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: gjimenez, Assigned: sgarrity)

Tracking

unspecified
4.10
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: r=98435,98517 b=trunk)

(Reporter)

Description

7 years ago
Implement Firefox Aurora for Mobile Optimized Page Design from Bug: 695604
Target Live Date: Tuesday, Nov. 8
(Reporter)

Updated

7 years ago
Summary: Implement: Firefox Aurora Page Optimized for Mobile → [Firefox Aurora Branding] Implement: Firefox Aurora Page Optimized for Mobile
(Reporter)

Updated

7 years ago
Priority: -- → P2

Updated

7 years ago
Assignee: lforrest → steven

Updated

7 years ago
Target Milestone: 4.5 → 4.6

Comment 1

7 years ago
Hey Steven - heads up here, assets should be ready by end of this week. We're targeting the 4.7 milestone to launch this. Thanks!
Target Milestone: 4.6 → 4.7

Comment 2

7 years ago
Steven, would you mind giving a status update on this? Thank you!
Target Milestone: 4.7 → 4.8
(Reporter)

Comment 3

7 years ago
hi chrissie, 

the design is almost ready and just waiting for minor tweaking from Ty. 
Ty was out sick last week, so we had to move implementation to another week.
Here is the design bug for this page: 695604

We're hoping to finalize the design by this week and hopefully get it implemented for 4.8.

please let me know if you have any additional questions.

thanks!

Comment 4

7 years ago
(In reply to Grace Jimenez :grace from comment #3)
> hi chrissie, 
> 
> the design is almost ready and just waiting for minor tweaking from Ty. 
> Ty was out sick last week, so we had to move implementation to another week.
> Here is the design bug for this page: 695604
> 
> We're hoping to finalize the design by this week and hopefully get it
> implemented for 4.8.
> 
> please let me know if you have any additional questions.
> 
> thanks!

Grace, thank you, I'm tuned into watch Bug 695604. It will be tight to get it into 4.8, because we're putting all efforts into launching the rebranded /new /fx and first run pages. 

I will prioritize this bug to go directly to silverorange after those are complete.

Comment 5

7 years ago
Alriiiight! Steven, assets here: http://mozilla.tyflanagan.com/artwork/Nightly_Aurora/FFx_Aurora_Mobile_Android.psd.zip

Can you prioritize for after the /new, /fx, and first run pages are coded?
(Reporter)

Comment 6

7 years ago
hi chrissie, 

no problem.
we can also include in 4.9, if the timing is too tight. 
given we are still waiting for the mobile page (desktop view).

Thanks for the follow up!

Comment 7

7 years ago
(In reply to Grace Jimenez :grace from comment #6)
> hi chrissie, 
> 
> no problem.
> we can also include in 4.9, if the timing is too tight. 
> given we are still waiting for the mobile page (desktop view).
> 
> Thanks for the follow up!

#fb!
(Reporter)

Comment 8

7 years ago
hi steven, 

im not sure if you saw this one. 
I assume this would probably be too late for 4.8 push tomorrow?

let me know if you are able to include this for tomorrow's push.

Chrissie, what's our URL format for optimized mobile pages?
mozilla.org/firefox/m/firefoxaurora?
m.mozilla.org/firefoxaurora?

please advise.


thanks.

Updated

7 years ago
Target Milestone: 4.8 → 4.9
(Reporter)

Comment 9

7 years ago
directions also provided in: 696546

there are 2 design versions that needs to be implemented and tested.
laura forrest can provide more info on testing details. 

here are the final psds.

v1. http://mozilla.tyflanagan.com/artwork/Nightly_Aurora/FFx_Aurora_Mobile_Android.psd.zip


v2: http://mozilla.tyflanagan.com/artwork/Nightly_Aurora/FFx_Aurora_Mobile_Android_v2.psd.zip


thanks!
(Reporter)

Updated

7 years ago
Target Milestone: 4.9 → 4.10
(Assignee)

Comment 10

7 years ago
http://www-dev.allizom.org/en-US/m/firefox/aurora/

It looks a little funny in a desktop browser, but looks good on mobile devices (tested on a few Android devices and iOS).

I don't have a URL for the "What's New in this Version" link though - where should that point?

If this can get QA'ed in time, it could go out with the 4.9 release tomorrow.
Keywords: qawanted
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: r=98435, b=trunk
(Assignee)

Comment 11

7 years ago
I didn't realize that this bug had two designs. Should we implement both at different URLs? Will we be able to use SiteSpect for testing?
(Assignee)

Comment 12

7 years ago
Created a new link that will redirect to the latest Aurora release notes and added it here.

Grace, can you clarify how the two designs should be handled? Should we just build out two similar pages?
Whiteboard: r=98435, b=trunk → r=98435,98517 b=trunk

Updated

7 years ago
Priority: P2 → P1
(Reporter)

Comment 13

7 years ago
Im not really sure how we implement two designs for testing. 
laura forrest would be able to provide more info on this.

Laura, how do we usually do the implementation if we are testing two designs? 

thanks!

Comment 14

7 years ago
(In reply to Grace Jimenez :grace from comment #13)
> Im not really sure how we implement two designs for testing. 
> laura forrest would be able to provide more info on this.
> 
> Laura, how do we usually do the implementation if we are testing two
> designs? 
> 
> thanks!

Hey Grace, I'll chime in here - we won't be able to do any testing with our tool, Sitespect until January 1, 2012. My recommendation would be to split this into two bugs, making this bug for the page you want live in Q4 and the new bug for the second page to go live in early January Q1 and set it as a blocker to bug 700746 (this is the Sitespect bug to get the testing tool up and running again).

Let me know if I can help any further.
(Reporter)

Comment 15

7 years ago
sure. thanks laura! i can go ahead and do that.

steven, let's go with v1 design for now (current desktop design). 

thanks!
(Reporter)

Comment 16

7 years ago
(In reply to Grace Jimenez :grace from comment #15)
> sure. thanks laura! i can go ahead and do that.
> 
> steven, let's go with v1 design for now (current desktop design). 
> 
> thanks(In reply to mcbmoz from comment #14)
> (In reply to Grace Jimenez :grace from comment #13)
> > Im not really sure how we implement two designs for testing. 
> > laura forrest would be able to provide more info on this.
> > 
> > Laura, how do we usually do the implementation if we are testing two
> > designs? 
> > 
> > thanks!
> 
> Hey Grace, I'll chime in here - we won't be able to do any testing with our
> tool, Sitespect until January 1, 2012. My recommendation would be to split
> this into two bugs, making this bug for the page you want live in Q4 and the
> new bug for the second page to go live in early January Q1 and set it as a
> blocker to bug 700746 (this is the Sitespect bug to get the testing tool up
> and running again).
> 
> Let me know if I can help any further.

thanks Chrissie!
(Reporter)

Comment 17

7 years ago
opened bug 708722 for v2 testing implementation.
qa-verified-trunk http://www-dev.allizom.org/en-US/m/firefox/aurora/
Keywords: qawanted
(Assignee)

Comment 19

7 years ago
Since there's a new bug opened for the second version, we're all set here.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
pushed to production r98756
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.