STR: 1. Visit mozilla.org with Firefox on an Android device. 2. The first CTA says Download Firefox. Tapping that will reveal a button that takes you to Google Play which gives you the option to uninstall or open. Tapping open will take you back to mozilla.org 3. A bit farther down the page there is a "Put your Firefox on your Android" CTA. Tapping this reveals a "Learn about Firefox for Android" button which leads to /android. This is OK but the original CTA is weird because you already have Firefox on your Android. 4. Further down again there is a Firefox "Get it Free on Google Play" button does the same as the one at the top. I used Firefox for Android v38 to test. UA reported as: Mozilla/5.0 (Android; Mobile; rv:38.0) Gecko/38.0 Firefox/38.0 We should remove these CTAs for Firefox for Android users.

I would question the benefit of adding this complexity to our pages. Adding more UA sniffing and conditional content to each page comes at a price in terms of maintenance. For all these conditions, we would need fallback content that is also translated into many locales. I'm not sure if I see the benefit when we weigh it all up.

I had previously thought the conditional download button (the classic green one) could handle identifying folks on Firefox for Android and giving them an appropriate message (like we do with Firefox for desktop)... I'll look on my tablet this evening.

All we do on android is detect the platform, not browser fwiw. Doing browser specific detection is another ballpark.

(In reply to Alex Gibson [:agibson] from comment #3) > All we do on android is detect the platform, not browser fwiw. Doing browser > specific detection is another ballpark. Thanks, Alex. I, of course, forgot to pull out my tablet last night to look.

Verdi - let's chat on IRC today, but it looks to me like the amount of traffic coming to us on Firefox for Android is very small and honestly, those folks should know better than to try to download again, right, since they are already on the browser? And can re-install via the Play store?

A few thoughts and some info behind what is currently on the page: On the mozilla.org homepage, the top and bottom CTAs you see are permanent in the template. However, the 2nd one you are seeing is one of the promo areas that can be swapped out from time to time depending on a campaign. To alter behavior on the top and bottom CTAs we should consider any change to be something inherent to wherever download buttons are displayed across mozilla.org (we could create a special case for mozilla.org, but it's nice to keep the logic consistent if we can). For the promo space, we would need to consider conditional promos and have a fall-back promo available for when somebody views it on their Android device (e.g., Sync?). (this is a requirement to consider if we ever implement a CMS for the homepage) Seems like overkill to show somebody already on Firefox for Android 3 CTAs to get something they already have. If it is worth the scope of work to do so, perhaps Sync could be promoted in its place in one of the top CTAs (download button or promo, whichever is easiest) and conditionally remove the CTA at the bottom of the page. Unfortunately, we can't tell if a user is signed into sync or not on Android. That being said, Android users like to see the info on the play store since it has reviews and other info that is regularly kept up to date. If this is open for discussion, what do you think about the following for Fx for Android users visiting mozilla.org? - Top CTA: Promote Sync in place of the download button (user may already be signed in) - Promo area: Keep as-is - Bottom CTA: remove

(In reply to Holly Habstritt Gaal [:Habber] from comment #6) > On the mozilla.org homepage, the top and bottom CTAs you see are permanent > in the template. However, the 2nd one you are seeing is one of the promo > areas that can be swapped out from time to time depending on a campaign. To > alter behavior on the top and bottom CTAs we should consider any change to > be something inherent to wherever download buttons are displayed across > mozilla.org (we could create a special case for mozilla.org, but it's nice > to keep the logic consistent if we can). For the promo space, we would need > to consider conditional promos and have a fall-back promo available for when > somebody views it on their Android device (e.g., Sync?). (this is a > requirement to consider if we ever implement a CMS for the homepage) The conditional promo blocks are rendered on the server, based on things like page locale and whether or not they are translated. Doing conditional blocks based on the users browser is slightly different. Here, we'd likely need to add in support for showing conditional content client-side. This is totally possible, but requires more work technically. We would also likely need to have them all pre-translated, since it would just be showing & hiding content after the page has loaded.

(In reply to Jennifer Bertsch [:jbertsch] from comment #5) > Verdi - let's chat on IRC today, but it looks to me like the amount of > traffic coming to us on Firefox for Android is very small and honestly, > those folks should know better than to try to download again, right, since > they are already on the browser? And can re-install via the Play store? Sure I guess this isn't an emergency but it would be good to fix. Lots of people on mobile - many exclusively. Seems to me we're going to want to be able to talk to mobile Firefox users differently than other mobile users at some point.

The homepage this bug referred to is no longer active for the vast majority of locales. The new home page features a generic Firefox section that doesn't call out any particular platform. Closing this as wontfix.