Purpose of this meeting: Big picture progress and plans of the apps program components and identification of issues that need alignment.

For dial-in info, see this page.

Agenda

1. Apps Ecosystem for FFxOS
2. Status Updates

Status Updates

Product Development (Engineering, QA, Security, UX)

Payments

News on payment plans, implementation, and legal/financial across B2G, Android, and Desktop

Identity

Updates on the identity integration with Marketplace and apps

Marketplace

Core Marketplace product and feature updates, release readiness

Firefox OS

B2G product updates concerning apps, release schedule updates

WebRT (Desktop & Android)

WebRT updates and readiness for upcoming milestones

• Android WebRT had great test day, triaging newly filed bugs

Apps in the Cloud

Latest on app sync

• Harald continues to work on browserID support for Android, pre-requisite for AITC on Android.

User & Developer Engagement

Business Development

Progress towards regional app goals and feedback from partners

Marketing

Go to market planning and merchandising updates

Developer Experience

Plans and progress in developer ecosystem, tutorials, and app lifecycle tools

• Alpha version of Marketplace Developer Hub (dev site link) is due to be released tomorrow (Thursday)
  • in this release: selection of core docs, tutorials and tools for apps development
  • next: improvements for IA/UX (clearer distinction between devhub and MDN), and visual design.
• "UI SDK": In the process of defining what pieces we should deliver to devs for building apps UIs, and what gaps we still have.

App Review & Content

Current status of apps in the Marketplace and policy updates

App review on FFOS

• Tested 47 games on FFOS (all free games and all apps targeting pt-BR) on Nexus S build
• Judged on whether the site is:
  • clearly desktop/mobile (mobile required) -- 36% failed
  • performance -- 28% were slow to load or ran slowly
  • functionality (plain old bugs, errors in app logic) -- 10% had failing bugs
  • content (chrome ads, download from native store, mature content) -- only 1 app during this test run, real number probably higher
    • As I understand from fligtar, the Brazilian government has some crazy requirements regarding game content review. This was NOT taken into consideration during this testing.
  • mobile design optimization (passes review, but could it be better?) -- 46% need improvement
  • Security and privacy issues were NOT taken into consideration during this testing (although I assume they've gone through the code validator)

Test data available upon request.

WIP - Baseline criteria to be considered "optimized for mobile"

• Doesn't require horizontal scroll (unless by design)
• Tap targets at least _____ px
• Font size at least ______ px
• Takes full advantage of available screen space (ie. app isn't TOO small)
• Smaller image assets? (bandwidth)
• Doesn't require physical keyboard

Some questions:

• Flash support on FFOS?
• What are the min and max supported resolutions to be considered phone, tablet? (for fennec and FFOS)
• Other minimum requirements?
• Usability thing I ran into: I'd regularly tap a link to go from the "app" to a "web page." There's no way to navigate back to the app?

Services

Support

Support plan updates

Infrastructure

SLA reports and progress towards operational readiness

Action Items