View source for User:Elancaster/RoadmapDraft


Partner opportunities: pre-install and alternative distributions
Pre-install partners are still a ways off, although there are some short-term opportunities we can take advantage of
Vetted alternative distribution channels is a good way of gaining visibility, discoverability, and targets NEW users within our current TAM
NB: leaning towards our current, better-known market segment instead of developing due to supporting functions not yet ready to tackle these 'really new' customers
Revenue generation
Let's see if we can more actively contribute to the Mozilla financial position
Innovate to differentiate
Build on core strengths
Ensure foundations and basics are available for us to build upon
Consumer-led (and good marketing-led) differentiators
Developer ecosystem
Some of these items can fit across some of these other pillars, but probably worth calling out separately
Tablestakes
Ensuring we have good code
Addressing papercuts, direct user feedback where we can
Ensuring we're not unnecessarily behind the competition
Although could and probably should be 4, I wanted to call out tablestakes so we don't lose sight of ensuring we have good, quality code that we're always proud of shipping.

The idea here is that we don't put all our eggs into one of these baskets (or following along the pillar analogy, putting all the stones towards one column) so that we have a fairly balanced workload across all four areas.

To support the above, here is the list that I have called out (note that I am aware that this is spread across multiple teams, and they're not ALL P1s, but did want to call these bits out as what I feel are the important bits of work upon which we should focus):

Revenue Generation
Search engines (P1)
Before we change the default search engines (to revenue-generating ones), we need the UI to allow users to set their default search engine to switch back if they wish
Search engines to add (KR currently clearing with BD): Yahoo, Bing, Yandex
Search suggestions usage (KR currently clearing with BD): Yahoo, Bing, Wikipedia, Yandex?
Adding search engines to the list (without touching default) can be first step, once BD has ok-ed all contracts (in progress)
Matching default engines to the right locales is also currently inflight and will require vetting
Possible to use different default search engine for Canada and the UK (given we only have en-US)? Ideally, would like to split this apart from a default perspective so we can balance revenue-generating opps that best match the engine of best choice

Partnership Opportunities
Pre-install / distribution opportunities 
Aruba (privacy review of wrapper, release mgmt plan) - should be light on your teams (P1)
T-Store (release mgmt plan, distribution agreement vetting, should hopefully be light on your teams) (P2)
Ouya - both pre-install & alternative distribution opportunity. So far, I am going to bat on this on unless I get some market feedback that really discourages me. (P2)
Minimum TV optimizations (web content adjustable font; border 'space') (P2)
Navigation directional control (standard control, no snav requirements from the outset)  (P2)
IBM - security investigations on what we could do to support a Corpfox profile (or on-site compiled) (P2)
Dynamic snippets (P1)
Distribution files (P1)
L10N multi-locale build (P2)

Innovate to Differentiate
Shumway: video playback using generic player (P1) from top sites; using branded player (P2) 
about:home redesign 
3 swypable pages (P1)
magazine style for reader list (P2)
Reader
quick action to add to reader list (long tap, menu) (P1)
night mode (P1)
serif/sans serif font toggle (P2)
save scroll position (P2)
shortcuts to next / previous article (P3)
handling offline reading (P2)
rich preview of article (P3)
WebRTC
Support Android for WebRTC (P1)
Guidelines for mobile implementation (P2)
Identify front-end work, UI framework (P2)

Developer Ecosystem
APIs
Webactivities, Push, Contacts are P1s
Payments, Alarm are P2s
Priviledged apps (P1)

Tablestakes
Reflow on zoom on double tap (P1)
Canvas performance (P1) (could also be listed partnership support)
SkiaGL
Async canvas swapping
Others? looking for input here
Performance improvements (could also be listed partnership support)
Canvas 2D (thinking Ouya and the market it serves)
WebGL(thinking Ouya and the market it serves)
ANR bugs (P1)
New tab UI (finishing off) (P1)
Settings UI clean-up (P1)
Quickly share using last app (P2)
Any PiCL integration for sign-up (P2)
Gestures engine to add a handful of gestures (P2)
Form autocomplete (P2)
First-run UX emphasis on UX here, though, and not necessarily engineering in this quarter