Mobile/webdevplan

Phase 1

Goal: Implement a short-term solution for getting the most amount of mobile users to Firefox.com/m/beta and downloading Firefox 4 Beta.

Requirement #1: Those visiting the following pages from an Android or Maemo device should be redirected to Firefox.com/m/beta ( beta download page)

• Mozilla.com
  
• Firefox.com
  
• Mozilla.com/Firefox
  
• Mozilla.org/Firefox
  

Bug:
Webdev contact:
Timing:

Requirement #2: On Firefox.com/m, in front of “See More Features,” add the link “Get Firefox 4 Beta for Android and Maemo” and redirect user to Firefox.com/m/beta (while beta downloads are the primary objective)

Bug:
Webdev contact:
Timing:

Requirement #3: Add link with text “Full Site” at the bottom, in front of “FAQ” link of Firefox.com/m and Firefox.com/m/beta if the true intent was to go to Mozilla.com or Firefox.com.
Bug:
Webdev contact:
Timing:

Requirement #4: On Firefox.com/m/beta, builds are separated by Android/Meamo buttons to ensure the best funnel while device detection gets improved.

Phase 2

Goal: Improve device detection on Firefox.com/m and Firefox.com/m/beta to increase the number of successful downloads.

Requirement#1: Each page should only have one download button and should detect the following:

Android or Maemo
Compatible with devices requirements (Android 2.0 and above, ARM v7)
Should be updated as new, compatible devices hit the market
See supported devices: https://www-trunk.stage.mozilla.com/en-US/mobile/platforms/

Requirement #2: Appropriate error messages should appear depending on the scenario.
Initial examples:

“Your device is not supported by Firefox. Please see this link (or this list) to view Firefox supported devices.”
“Attention: Your device is supported by Firefox, but not tested. After downloading, please let us know should you discover any issues.” (Consider adding this to About:Welcome page)

Requirement #3: Web pages linked from Firefox mobile should be optimized for mobile viewing and reading. Those pages include:

About:Firefox pages
FAQ
Rel Notes
Features
Privacy Policy
Get Involved page
Quarterly mobile survey
Input (Beta Tester Tools)

Is req. #3 higher priority than #1 and #2? IMO, it has more immediate benefit.

Timing: (7 weeks): 12/18/10
How did we get the date 12/18? It seems like we don’t know much about the scope, and so can’t yet pick a deadline we can stick to.

Phase 3
Goal: Users enjoy a readable, touch-friendly and user-friendly version of Mozilla.com on their mobile phones on major pages where they’re either trying to download Firefox, add-ons, or get help. Those sites/pages include:

Mobile SUMO
Mobile AMO
Firefox.com/mobile
Mozilla.com (page)
Firefox.com (page)

Requirement #1:
Requirement #2:
Requirement #3:

Timing: (11+ weeks): 2/12/11