Mobile/webdevplan

Project Goals

• Ensure that Mozilla serves up a user friendly page to download Firefox from their mobile device.
• Ensure that Downloading Firefox provides user with the correct build (or correct help message) depending on user's mobile device.
• Ensure that all pages linked to from Firefox mobile are user friendly on a mobile device.
  

Team

Webdev contact: malexis@mozilla.com, lforrest@mozilla.com
Webdev implementation: websites team
UX: jgrlicky@mozilla.com (mockup reviews with jslater@mozilla.com)
plan specs: clooney@mozilla.com

Phase 1 - Beta 3 Blockers (Code Freeze: Nov. 23, Launch: Dec. 7)

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

Mockups

Requirement #1: Android/Maemo devices hitting landing page should be redirected to mobile landing page

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

Bug: bug 608415
Webdev contact: Alex Buchanan
Timing:

• Code freeze Friday 11/19.
• QA 11/22-24.
• Depending on QA, launch on 11/30.
• Launching 11/23 might be possible, depending on QA.
  

Requirement #2: Beta download buttons on mobile landing page.

Bug:bug 611192
Webdev contact:Jason Grlicky
Timing: with requirement 1

Requirement #3: Provide link back to the "full site"

Bug:bug 611191
Webdev contact:Jason Grlicky
Timing: with requirement 1

Requirement #4: Pages listed in about:firefox should be optimized for mobile viewing:

• Privacy Policy
• Rel Notes
• Credits
• FAQ
  
• Support
  
• Know Your Rights
  

Bug:
Webdev contact:
Timing:

Phase 2

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

Design mockups for this phase are available Here.

Requirement#1:  Firefox.com/m and Firefox.com/m/beta should have one download button with device detection providing the right build to the mobile user.

• 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/

Bug:
Webdev contact:
Timing:

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)
  

Bug:
Webdev contact:
Timing:

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

• FAQ
  
• Features
• Get Involved page
• Quarterly mobile survey
• Input (Beta Tester Tools)

Bug:
Webdev contact:
Timing:

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. 

Design mockups for this phase are available Here.

In order of priority:
1. Mobile AMO
2. Mobile SUMO landing page + top 5 most visited pages.
3. Firefox.com/mobile, Mozilla.com - redesigned and redirected to Firefox.com/m
4. www.GetPersonas.com

5. About:Firefox pages (see below for full list)
6. Firefox.com/mobile/sync - reformatted for mobile friendliness to help the setup process

7. Firefox.com/mobile/featues - reformatted for mobile/touch friendliness
8. http://www.mozilla.org/

Pages listed in about:firefox should be optimized for mobile viewing:

Privacy Policy
Rel Notes
Credits
FAQ
Support
Know Your Rights