Mobile/ProductPlanning/Notes-2012-10-02: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "__NOTOC__ == Details == * irc.mozilla.org #mobile for backchannel * Mobile vidyo room * meetings generally held on Tuesdays @ 9:00am Pacific - exceptions apply every 6 weeks * [h...")
 
 
(6 intermediate revisions by the same user not shown)
Line 13: Line 13:
* Agree on product-specific Firefox on Android goals for Q4
* Agree on product-specific Firefox on Android goals for Q4


;Beta Channel - [https://wiki.mozilla.org/Mobile/Fx16 Fx 16: Casting a Wider Net]
;Other Topics for Discussion
* ARMv6: go / no-go decision
* iOS investigation update
 
== Minutes ==
;ARMv6 go / no-go
* DECISION: ARMV6 will NOT go into Fx 16 GA, but will ride out another beta cycle on Fx 17
* Only 19 unique data points have been gathered - [https://docs.google.com/spreadsheet/ccc?key=0AukS66vOYHUQdFYzQWhFZjFlczJiVW9DZEF5clpHd2c#gid=0 consolidated spreadsheet of feedback]
* These few data points are not overwhelmingly positive
* We do not want to be in the same position when we approach Fx 17 GA: we need to make use of this extra beta cycle
* Within the next 1.5 weeks, Karen (with input) will create a plan on how to try and get more data on ARMv6 devices
** Take into account marketing, external testers, social media outreach, ....
* Exploration with a third-party test house should proceed, BUT we must be explicit with their methodology (test cases, bugs, hardware)
* Product Marketing was not planning on pushing this hard, therefore it will not make a big impact to Fx 16 GA plans
* Important ARMv6 markets are Philippines, Indonesia, India and Eastern Europe
** In majority, Philippines, Indonesia and India use English locales so we shouldn't be hugely hampered by not having their specific locales included
** Current list of [http://mxr.mozilla.org/mozilla-central/source/mobile/android/locales/maemo-locales supported locales in the multi-lang build]
* Irina to send out top ARMv6 phones for these regions for better user targeting
* Google Play downloads grabs the model information, which can be used to give an indication of the ARMv6 audience / interest
 
;Q4 Priorities
* Shared the plan for Q4 priorities with the team -  
* The work is grouped by its release channel: GA on Fx 16 or 17, Beta on Fx 18, Aurora on Fx 19 or Under Investigation
* These projects are ALL deemed priorities for completion in Q4 and are important in maintaining the health of the Fennec roadmap
* Feedback can be provided back to Karen, Brad, Mark, Chad, Sam or Erin
* It's prettier in slide format, but the content is as follows (current as of today's meeting):
 
GA: Fx 16, Fx 17
* ARMv6
* WebApps
* Media Decoding


;Aurora Channel - [https://wiki.mozilla.org/Mobile/Fx17 Fx 17: Making Things Easy]
Beta: Fx 18
* Hot items only
* Android Snippets
* Private Browsing & Safe Browsing
* Google Campaign IDs
* Updater
* New Font
* Select Search Improvements (search suggestions opt-in; one-line search widget)


;Nightly Channel - [https://wiki.mozilla.org/Mobile/Fx18 Fx 18: Beautiful Browsing]
Aurora: Fx 19
* Hot items only
* Android-Supported Locales
* WebRTC (demo -> not for Aurora)
* Reflow on Zoom
* Metrics & Benchmarking
* Personalisation & Customisation


;Other Topics for Discussion
For Investigation
* Backlog: resourcing for investigations
* First-Run UX and Next Gen Sync (BID)
** iOS
* iOS Support
** X286
* X86 Support
** ...
* WebRTC
 
;Hot Items
* Fx 17 - media decoding
** Fx 17 will include H264 support for ICS and JB, but very unlikely we will include GB support
** GB will come in Fx 18
** GB users will get a mime-type error after clicking on the content
** Product Marketing has already been planning for this phased roll-out
** Irina re-confirmed that honeycomb and froyo numbers are very low and decreasing, therefore we will not expend cycles in implementing support for these OS versions
* Font licensing update
** New font not yet licensed, but Ian is working through some different options
** Code landed that allows us to switch fonts

Latest revision as of 22:20, 8 October 2012

Details

Agenda

Roadmap launchpad: https://wiki.mozilla.org/Mobile/Roadmap12-13

Q4 Goals
  • Agree on product-specific Firefox on Android goals for Q4
Other Topics for Discussion
  • iOS investigation update

Minutes

ARMv6 go / no-go
  • DECISION: ARMV6 will NOT go into Fx 16 GA, but will ride out another beta cycle on Fx 17
  • Only 19 unique data points have been gathered - consolidated spreadsheet of feedback
  • These few data points are not overwhelmingly positive
  • We do not want to be in the same position when we approach Fx 17 GA: we need to make use of this extra beta cycle
  • Within the next 1.5 weeks, Karen (with input) will create a plan on how to try and get more data on ARMv6 devices
    • Take into account marketing, external testers, social media outreach, ....
  • Exploration with a third-party test house should proceed, BUT we must be explicit with their methodology (test cases, bugs, hardware)
  • Product Marketing was not planning on pushing this hard, therefore it will not make a big impact to Fx 16 GA plans
  • Important ARMv6 markets are Philippines, Indonesia, India and Eastern Europe
  • Irina to send out top ARMv6 phones for these regions for better user targeting
  • Google Play downloads grabs the model information, which can be used to give an indication of the ARMv6 audience / interest
Q4 Priorities
  • Shared the plan for Q4 priorities with the team -
  • The work is grouped by its release channel: GA on Fx 16 or 17, Beta on Fx 18, Aurora on Fx 19 or Under Investigation
  • These projects are ALL deemed priorities for completion in Q4 and are important in maintaining the health of the Fennec roadmap
  • Feedback can be provided back to Karen, Brad, Mark, Chad, Sam or Erin
  • It's prettier in slide format, but the content is as follows (current as of today's meeting):

GA: Fx 16, Fx 17

  • ARMv6
  • WebApps
  • Media Decoding

Beta: Fx 18

  • Android Snippets
  • Private Browsing & Safe Browsing
  • Google Campaign IDs
  • Updater
  • New Font
  • Select Search Improvements (search suggestions opt-in; one-line search widget)

Aurora: Fx 19

  • Android-Supported Locales
  • WebRTC (demo -> not for Aurora)
  • Reflow on Zoom
  • Metrics & Benchmarking
  • Personalisation & Customisation

For Investigation

  • First-Run UX and Next Gen Sync (BID)
  • iOS Support
  • X86 Support
  • WebRTC
Hot Items
  • Fx 17 - media decoding
    • Fx 17 will include H264 support for ICS and JB, but very unlikely we will include GB support
    • GB will come in Fx 18
    • GB users will get a mime-type error after clicking on the content
    • Product Marketing has already been planning for this phased roll-out
    • Irina re-confirmed that honeycomb and froyo numbers are very low and decreasing, therefore we will not expend cycles in implementing support for these OS versions
  • Font licensing update
    • New font not yet licensed, but Ian is working through some different options
    • Code landed that allows us to switch fonts