Mobile/webdevplan: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "== 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.''' <br> <u>Requirem...")
 
No edit summary
Line 28: Line 28:
== Phase 2<br>  ==
== Phase 2<br>  ==


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


<br> <u>Requirement#1:</u>&nbsp; Firefox.com/m and Firefox.com/m/beta should have one download button with device detection providing the right build to the mobile user. <br>


<u>Requirement#1:</u> 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/


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


<br>  
<br>  


Requirement #2: Appropriate error messages should appear depending on the scenario.<br>Initial examples:  
<u>Requirement #2:</u> Appropriate error messages should appear depending on the scenario.<br>Initial examples:  


“Your device is not supported by Firefox. Please see this link (or this list) to view Firefox supported devices.”<br> “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)  
*“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)<br>


<br>  
<br>Bug:<br>Webdev contact:<br>Timing:<br> <br>
 
<u>Requirement #3:</u> 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)


Requirement #3: Web pages linked from Firefox mobile should be optimized for mobile viewing and reading. Those pages include:  
Bug:<br>Webdev contact:<br>Timing:<br>


About:Firefox pages<br> FAQ<br> Rel Notes<br> Features<br> Privacy Policy<br> Get Involved page<br> Quarterly mobile survey<br> Input (Beta Tester Tools)
== <br>Phase 3 ==


<br>Is req. #3 higher priority than #1 and #2? IMO, it has more immediate benefit.  
'''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.&nbsp;'''


Timing: (7 weeks): 12/18/10<br>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.


<br>Phase 3<br>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<br> Mobile AMO<br> Firefox.com/mobile<br> Mozilla.com (page)<br> Firefox.com (page)  
Mobile SUMO<br> Mobile AMO<br> Firefox.com/mobile<br> Mozilla.com (page)<br> Firefox.com (page)  
334

edits

Navigation menu