Closed Bug 683038 Opened 13 years ago Closed 13 years ago

[Rapid Release Branding] Firefox Aurora Branded Facebook Download Page

Categories

(Marketing :: Design, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gjimenez, Assigned: tyronflanagan)

References

Details

Attachments

(1 file)

Hi tara, 

follow up from bug 666796. 
Firefox Aurora branded download tab.
we can probably use the same design and just update the background?
let me know what you think.
Hey Grace.  Sure, that could work.  I was hoping we had found a better solution for the many green buttons by now... 
Also wanted to note that if you're trying to better distinguish "beta" vs. Aurora branding, etc... having them all on the Aurora space background is probably not going to help.  And the "beta" sash is not something we really want to be using for desktop. So, just wanted to note that. 

Anyway, what is your timing on this?  

Assigning to Ty.
Assignee: tshahian → tyronflanagan
Also, Grace:  do you have any metrics on how this page is doing?  Would be great to see if folks are actually clicking on these buttons and any learnings we've gotten through perf. tracking.  Basically seeing if the source for downloads are coming through this page (we can apply tags, and so forth)  LoFo would know better.
(In reply to Tara from comment #1)
> Hey Grace.  Sure, that could work.  I was hoping we had found a better
> solution for the many green buttons by now... 
> Also wanted to note that if you're trying to better distinguish "beta" vs.
> Aurora branding, etc... having them all on the Aurora space background is
> probably not going to help.  And the "beta" sash is not something we really
> want to be using for desktop. So, just wanted to note that. 
> 
> Anyway, what is your timing on this?  
> 
> Assigning to Ty.

- we are revamping some of the rapid release pages and using the logo with beta sash. 

slater, can you please confirm if the beta sash is okay to use? just like we did for the infographic?

- what's a realistic deadline? it would be great to have it by the end of this week, but if this is too tight the following week would be great!

Thanks!
(In reply to Tara from comment #2)
> Also, Grace:  do you have any metrics on how this page is doing?  Would be
> great to see if folks are actually clicking on these buttons and any
> learnings we've gotten through perf. tracking.  Basically seeing if the
> source for downloads are coming through this page (we can apply tags, and so
> forth)  LoFo would know better.

- will add LoFo and Williamr to the thread and work with them in getting better tracking for this.

Thanks!
Thanks Grace.  I talked to both John and Sean and we decided that it didn't make much sense to invest in the beta sash for desktop since it was created for mobile, and it's not the same icon that's downloaded (so it causes confusion).  I think it's fine to use it if we have both logos set next to each other, but otherwise It's not a logo that we'll be using as desktop/beta.  John, want to confirm please?

Grace, end of this week is pretty tight.  I can't promise as this bug should have been filed with more advance notice.
(In reply to Tara from comment #5)
> Thanks Grace.  I talked to both John and Sean and we decided that it didn't
> make much sense to invest in the beta sash for desktop since it was created
> for mobile, and it's not the same icon that's downloaded (so it causes
> confusion).  I think it's fine to use it if we have both logos set next to
> each other, but otherwise It's not a logo that we'll be using as
> desktop/beta.  John, want to confirm please?
> 
> Grace, end of this week is pretty tight.  I can't promise as this bug should
> have been filed with more advance notice.

- no problem. fine with a more realistic deadline.
- i think it would be great if we can be consistent with beta logo (with sash or no sash). it's even more confusing that we sometimes use it and sometimes we dont. 

thanks!
Re: the sash, the big issue is that the product icon is the standard Firefox logo, so I don't really feel comfortable promoting beta with something that looks different...I think that's very confusing for users. Were we to decide to update the beta product logo then that would be a very different matter (but that decision involves a lot more people than just me).

So, the current rule on the beta sash is that we use it in cases where the beta logo is positioned right next to the standard product (ex. Android marketplace), but generally speaking it's the exception rather than the rule.

Hope that helps.
(In reply to John Slater from comment #7)
> Re: the sash, the big issue is that the product icon is the standard Firefox
> logo, so I don't really feel comfortable promoting beta with something that
> looks different...I think that's very confusing for users. Were we to decide
> to update the beta product logo then that would be a very different matter
> (but that decision involves a lot more people than just me)
> 
> So, the current rule on the beta sash is that we use it in cases where the
> beta logo is positioned right next to the standard product (ex. Android
> marketplace), but generally speaking it's the exception rather than the rule.
> 
> Hope that helps.

agree that it's confusing when the product doenst have a different logo.
i believe we are using logo with beta sash on the new channel landing page (as it is next to the final release). but generally, i just thnk it's confusing as well that we are using it interchangeably (sometimes using sash and sometime not). 

fine with whatever you recommend.
Agreed that it's confusing either way.  What's the reason for not having the Beta icon for desktop also be downloaded with the sash so everything feels consistent?  I know that's not the discussion for this bug, but... just curious.
Me like.
This looks awesome.  Only thought--should there be a link back to the moz.org/firefox releases home page? Like a get more info link?
Blocks: 698918
closing. continuing in bug: 698918
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: