Closed Bug 654818 Opened 13 years ago Closed 13 years ago

[Rapid Release] Update firefox.com/m page to add beta download button

Categories

(www.mozilla.org :: General, defect, P1)

Product:
www.mozilla.org
Component:
General
Version:
Firefox 5
Platform:
All
Android
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: gjimenez, Assigned: sgarrity)

Details

Hi Jason, 

Just to follow up from our conversation, we need to update the firefox.com/m page to add the beta download button. the page will be live when the beta becomes available on the 17th.

maybe we can put the beta download button on top of the play firefox spark box? 

Copy: (copying matej for recommendations)
Interested in testing new features before they make it to the final release? Download Beta for mobile. [link to android market] 

let me know if you need any additional info. thanks!
I think we should be as concise as we can here, so I'd say one of the following:

Want to help shape the future of Firefox?
Download Beta for mobile

Want to help test the latest features? 
Download Beta for mobile

Want to help determine what makes it to final release?
Download Beta for mobile
(In reply to comment #1)
> I think we should be as concise as we can here, so I'd say one of the
> following:
> 
> Want to help shape the future of Firefox?
> Download Beta for mobile
> 
> Want to help test the latest features? 
> Download Beta for mobile
> 
> Want to help determine what makes it to final release?
> Download Beta for mobile

thanks matej. 

jason, 

let's go with: 
Want to help determine what makes it to final release?
Download Beta for mobile

thanks!
I'm assuming an additional requirement of this task is to drop the Maemo download button, like Caitlin mentioned earlier?
(In reply to comment #3)
> I'm assuming an additional requirement of this task is to drop the Maemo
> download button, like Caitlin mentioned earlier?

jason, we are dropping maemo on /mobile/download and would like to keep it in this page.

no need to drop maemo from this page.

thanks!
Ah, I see - I misunderstood. Is there any reason why we are exposing the Maemo download on the mobile site, but not on desktop? It seems like we'd want to be pretty consistent in general there.
Here is a mockup of the landing page with the Beta download button and the copy specified above:

http://people.mozilla.com/~jgrlicky/drop/mozcom/mobile_mockups/rapid_release/mobile_mozcom_P4_v1a.png

I think we might be able to achieve better results with even more concise copy, and changing "for Mobile" to "for Android" to let the user know that the beta releases will not work on other platforms.

http://people.mozilla.com/~jgrlicky/drop/mozcom/mobile_mockups/rapid_release/mobile_mozcom_P4_v1b.png

I'll defer to your judgement, of course - just putting it out there. Thoughts?
That looks good to me. I'd just say "Want to test the latest features?" instead of "latest
Firefox."
(In reply to comment #7)
> That looks good to me. I'd just say "Want to test the latest features?" instead
> of "latest
> Firefox."

Good call - updated the mockup:

http://people.mozilla.com/~jgrlicky/drop/mozcom/mobile_mockups/rapid_release/mobile_mozcom_P4_v1b2.png
(In reply to comment #5)
> Is there any reason why we are exposing the Maemo
> download on the mobile site, but not on desktop? It seems like we'd want to be
> pretty consistent in general there.

After checking out the comments on https://bugzilla.mozilla.org/show_bug.cgi?id=652811, I now see Caitlin's plan ;). I withdraw my concern!
I like this mockup, but wondering we want to have the orange download button above the fold and placed as narrower bar under the list of Supported Devices link and above the features. Jason, I defer to you, but curious how many folks pan down and will see this. I wonder we can test this page.
(In reply to comment #10)
> I like this mockup, but wondering we want to have the orange download button
> above the fold and placed as narrower bar under the list of Supported Devices
> link and above the features. Jason, I defer to you, but curious how many folks
> pan down and will see this. I wonder we can test this page.

hi caitlin. jason and I have talked about putting the button on top of the list. but the reasoning we to put it at the bottom is to keep the focus on the final release (and not distract/confuse mainstream users who might not want the beta) as this page is mainly to promote release and it's features. the beta download is more of a promo just like the spark at the bottom of the page. will follow up with you tomorrow and maybe we can look at the page again. thanks!
That's ok. I trust you and Jason considered it and have decided it's in the best place for the user. That said, we may want to try two different versions (and have a control group) at some point to learn more.
hi jason, 

after discussing this further with Caitlin, let's move the download beta button at the bottom of the "listed support devices" but can we make the height of the button smaller, to make it even more distinctive from the release button (in addition to it being orange ;) 

thanks jason!
Hey guys - I have to say that from a UX perspective, there's really no reason to put the beta download button in a competing position with the final release button.

If we don't want to miss out on potential downloads, we should present the user with as few choices as possible. This is why the desktop download button on mozilla.com is the only CTA on the page - beta is 100% separate. Having the mobile site deviate from this paradigm would be putting mobile at a disadvantage.

The beta button would also spatially separate the main download button from the list of product features, introducing new users to the idea of a "Beta" product before they even know what the features of Mobile Firefox are.

I know that putting the beta button in that position would increase beta downloads; if I'm wrong in assuming that we never want beta downloads to compete with final release downloads, then the change would be OK. I am, of course, also open to A/B testing an alternate version of this page with the beta button up top, but I can't recommend that we make that the main approach.
(In reply to comment #14)
> Hey guys - I have to say that from a UX perspective, there's really no
> reason to put the beta download button in a competing position with the
> final release button.
> 
> If we don't want to miss out on potential downloads, we should present the
> user with as few choices as possible. This is why the desktop download
> button on mozilla.com is the only CTA on the page - beta is 100% separate.
> Having the mobile site deviate from this paradigm would be putting mobile at
> a disadvantage.
> 
> The beta button would also spatially separate the main download button from
> the list of product features, introducing new users to the idea of a "Beta"
> product before they even know what the features of Mobile Firefox are.
> 
> I know that putting the beta button in that position would increase beta
> downloads; if I'm wrong in assuming that we never want beta downloads to
> compete with final release downloads, then the change would be OK. I am, of
> course, also open to A/B testing an alternate version of this page with the
> beta button up top, but I can't recommend that we make that the main
> approach.

hi jason, 
 
i agree with your points completely. the reasoning why we wanted it below the listed supported devices is because we don't want to miss the eyeballs going in the page. if the button is at the bottom of the page, we're not sure how many people will really see the call out on beta.

do you have any other recommendations on how we can promote beta that would fit the screen without competing with the final download button? maybe text to promote beta button that link to the bottom of the page where the download button is?

the goal is increase awareness of the beta without competing with the final release download but will defer to your recommendations what would best for the user.

it would be good to see a/b testing as well if possible. 

thanks!
(In reply to comment #15)
> (In reply to comment #14)
> > Hey guys - I have to say that from a UX perspective, there's really no
> > reason to put the beta download button in a competing position with the
> > final release button.
> > 
> > If we don't want to miss out on potential downloads, we should present the
> > user with as few choices as possible. This is why the desktop download
> > button on mozilla.com is the only CTA on the page - beta is 100% separate.
> > Having the mobile site deviate from this paradigm would be putting mobile at
> > a disadvantage.
> > 
> > The beta button would also spatially separate the main download button from
> > the list of product features, introducing new users to the idea of a "Beta"
> > product before they even know what the features of Mobile Firefox are.
> > 
> > I know that putting the beta button in that position would increase beta
> > downloads; if I'm wrong in assuming that we never want beta downloads to
> > compete with final release downloads, then the change would be OK. I am, of
> > course, also open to A/B testing an alternate version of this page with the
> > beta button up top, but I can't recommend that we make that the main
> > approach.
> 
> hi jason, 
>  
> i agree with your points completely. the reasoning why we wanted it below
> the listed supported devices is because we don't want to miss the eyeballs
> going in the page. if the button is at the bottom of the page, we're not
> sure how many people will really see the call out on beta.
> 
> do you have any other recommendations on how we can promote beta that would
> fit the screen without competing with the final download button? maybe text
> to promote beta button that link to the bottom of the page where the
> download button is?
> 
> the goal is increase awareness of the beta without competing with the final
> release download but will defer to your recommendations what would best for
> the user.
> 
> it would be good to see a/b testing as well if possible. 
> 
> thanks!

hi jason, 

let me know if you have any additional recommendation or have any additional questions. thanks!
Target Milestone: --- → 2.5
How's about we come up with two variants and let's test our assumptions:
1. competing model as proposed, with beta button below main
2. separate model with beta button at the bottom

What we want to answer:
1. does the beta button compete with the main button?  how does it affect GA release conversion?
2. does gain in beta download traffic warrant having the beta button on a mainstream page at all?
(In reply to comment #17)
> How's about we come up with two variants and let's
> test our assumptions:
> 1. competing model as proposed, with beta button below main
> 2. separate model with beta button at the bottom

Here's a quick mockup of a potential option 1:

http://people.mozilla.com/~jgrlicky/drop/mozcom/mobile_mockups/rapid_release/mobile_mozcom_P4_v2.png

Grace - I like your idea of a text description that links, instead of a button. Hopefully that will compete less - here, the beta link could even link to the channel page to give the user more info about what they're getting into before they download.

For option 2, we could use the mockup from comment #8:

http://people.mozilla.com/~jgrlicky/drop/mozcom/mobile_mockups/rapid_release/mobile_mozcom_P4_v1b2.png

What do you guys think?

Tangentially, as far as future strategy goes, it might be worthwhile to ask if a beta download button should even go on this page. Desktop Firefox has a healthy beta audience, and yet they don't market the beta on their landing page. This makes me ask: how and where do they tell people about it, and could we replicate that for mobile? For instance, we could incorporate a "Future Releases" item into the pull-down menu, get the word out in newsletters (since these people are already our fans!), and use a mobile equivalent of Snippets. We could even look at which methods have been most effective for them and see if we can pursue those first.

It also makes me wonder if instead of marketing the mobile beta to a general audience, if it would be more effective to market it to existing Desktop Beta users, since they're already the adventurous type ;)? Lots of possibilities here. Thoughts?
Component: www.mozilla.com → www.mozilla-japan.org
Target Milestone: 2.5 → ---
Assignee: jgrlicky → steven
Priority: -- → P1
Target Milestone: --- → 2.5
(In reply to comment #18)
> (In reply to comment #17)
> > How's about we come up with two variants and let's
> > test our assumptions:
> > 1. competing model as proposed, with beta button below main
> > 2. separate model with beta button at the bottom
> 
> Here's a quick mockup of a potential option 1:
> 
> http://people.mozilla.com/~jgrlicky/drop/mozcom/mobile_mockups/rapid_release/
> mobile_mozcom_P4_v2.png
> 
> Grace - I like your idea of a text description that links, instead of a
> button. Hopefully that will compete less - here, the beta link could even
> link to the channel page to give the user more info about what they're
> getting into before they download.
> 
> For option 2, we could use the mockup from comment #8:
> 
> http://people.mozilla.com/~jgrlicky/drop/mozcom/mobile_mockups/rapid_release/
> mobile_mozcom_P4_v1b2.png
> 
> What do you guys think?
> 
> Tangentially, as far as future strategy goes, it might be worthwhile to ask
> if a beta download button should even go on this page. Desktop Firefox has a
> healthy beta audience, and yet they don't market the beta on their landing
> page. This makes me ask: how and where do they tell people about it, and
> could we replicate that for mobile? For instance, we could incorporate a
> "Future Releases" item into the pull-down menu, get the word out in
> newsletters (since these people are already our fans!), and use a mobile
> equivalent of Snippets. We could even look at which methods have been most
> effective for them and see if we can pursue those first.
> 
> It also makes me wonder if instead of marketing the mobile beta to a general
> audience, if it would be more effective to market it to existing Desktop
> Beta users, since they're already the adventurous type ;)? Lots of
> possibilities here. Thoughts?

hi jason and steven,

let's go with option 1 for the 17th. 

jason, to answer your question, it's one of our goal to grow the beta channel for mobile and increase mobile beta presence/awareness including promoting in desktop beta sites and other channels (beta blog, beta newsletter etc.) but that also includes increasing awareness to our current/new mobile users. so it would be good to have data whether it is effective to put beta promo in mobile final release page or not. 

will follow up with lauraf regarding a/b testing plans. 

thanks!
(In reply to comment #19)
> (In reply to comment #18)
> > (In reply to comment #17)
> > > How's about we come up with two variants and let's
> > > test our assumptions:
> > > 1. competing model as proposed, with beta button below main
> > > 2. separate model with beta button at the bottom
> > 
> > Here's a quick mockup of a potential option 1:
> > 
> > http://people.mozilla.com/~jgrlicky/drop/mozcom/mobile_mockups/rapid_release/
> > mobile_mozcom_P4_v2.png
> > 
> > Grace - I like your idea of a text description that links, instead of a
> > button. Hopefully that will compete less - here, the beta link could even
> > link to the channel page to give the user more info about what they're
> > getting into before they download.
> > 
> > For option 2, we could use the mockup from comment #8:
> > 
> > http://people.mozilla.com/~jgrlicky/drop/mozcom/mobile_mockups/rapid_release/
> > mobile_mozcom_P4_v1b2.png
> > 
> > What do you guys think?
> > 
> > Tangentially, as far as future strategy goes, it might be worthwhile to ask
> > if a beta download button should even go on this page. Desktop Firefox has a
> > healthy beta audience, and yet they don't market the beta on their landing
> > page. This makes me ask: how and where do they tell people about it, and
> > could we replicate that for mobile? For instance, we could incorporate a
> > "Future Releases" item into the pull-down menu, get the word out in
> > newsletters (since these people are already our fans!), and use a mobile
> > equivalent of Snippets. We could even look at which methods have been most
> > effective for them and see if we can pursue those first.
> > 
> > It also makes me wonder if instead of marketing the mobile beta to a general
> > audience, if it would be more effective to market it to existing Desktop
> > Beta users, since they're already the adventurous type ;)? Lots of
> > possibilities here. Thoughts?
> 
> hi jason and steven,
> 
> let's go with option 1 for the 17th. 
> 
> jason, to answer your question, it's one of our goal to grow the beta
> channel for mobile and increase mobile beta presence/awareness including
> promoting in desktop beta sites and other channels (beta blog, beta
> newsletter etc.) but that also includes increasing awareness to our
> current/new mobile users. so it would be good to have data whether it is
> effective to put beta promo in mobile final release page or not. 
> 
> will follow up with lauraf regarding a/b testing plans. 
> 
> thanks!

hi steven, 

not sure if you've implemented this page already, 
is it still possible to make a small copy change?
with the beta button, can we update the text to say, 
"want to test the latest features"
"Download beta for android" vs check out.

thanks!
hi steven, just checking in to make sure we are all set for tomorrow? please let me know if you need any additional info. thanks!
(In reply to comment #21)
> hi steven, just checking in to make sure we are all set for tomorrow? please
> let me know if you need any additional info. thanks!

This was missed over the weekend because it was filed under www.mozilla-japan.org rather than www.mozilla.com. Hopefully still do-able today. Will start on it now and update soon.
Assignee: steven → nobody
Component: www.mozilla-japan.org → www.mozilla.com
(In reply to comment #22)
> (In reply to comment #21)
> > hi steven, just checking in to make sure we are all set for tomorrow? please
> > let me know if you need any additional info. thanks!
> 
> This was missed over the weekend because it was filed under
> www.mozilla-japan.org rather than www.mozilla.com. Hopefully still do-able
> today. Will start on it now and update soon.

hi steven. thats weird. sorry about that. keep me posted with the status. 
just a heads up - android market for beta link is tbd. will provide ASAP.
thanks!
Assignee: nobody → steven
Done in trunk in r88856. Please review in trunk and I'll merge to stage: http://www-trunk.stage.mozilla.com/en-US/m/
Merged to stage in r88877.
Status: NEW → RESOLVED
Closed: 13 years ago
Keywords: qawanted
Resolution: --- → FIXED
Thanks steven!
new live date: Thursday, 5/19

thanks!
Target Milestone: 2.5 → ---
Beta For Android URL
appID: org.mozilla.firefox_beta
https://market.android.com/details?id=org.mozilla.firefox_beta
Updated link from comment #28 in trunk in r89002.

Merged to stage in r89003.

That leaves to merges to stage that will have to go to production: r88877 and r89003.
hi steven,

i gave the update in the email but forgot to update this bug. 
if it's still possible can we make the download link to https://www-trunk.stage.mozilla.com/en-US/m/download-android.html?beta

if it's too late. this is not a blocker. and can update the link later. 

thanks.
Updated the link to use the download-android.html?beta page and made that page use the full market web link for the fall back link. Both in trunk in r89142.
Merged to stage in r89144.
pushed to production r89178
verified fixed https://www.mozilla.com/en-US/m/index.html
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
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.