In Q4, we will prepare for the launch of both Web Push and Service Workers in Firefox 44 by building one or two serious progressive apps and the infrastructure they require. We'll focus our engineers on one or two projects at a time, so we build team cohesion and benefit from collaboration. We'll carefully scope these projects so we can really hit them out of the park. Our tight focus, coupled with conference talks and blog posts, will make these apps useful references, helping build developer awareness for the launch of serviceworkers and push in Firefox 44. As we build real product code with automated tests, we explore the limits of our platform, find its bugs, and gather the knowledge we need to plan for the beginning of 2016.
=== Oghliner ===
* Ship v1 of Oghliner, a library/tool to offline web apps using Service Workers and deploy them to GitHub Pages. We will base this on top of several existing open source projects, including sw-precache from the Chrome team (https://github.com/GoogleChrome/sw-precache). [Note: this is likely to be the case, although there's some slight possibility that we'll replace sw-precache with our own implementation. I think that's unlikely in v1, however.]** Oghliner v1 - https://github.com/mozilla/oghliner
* === Platatus === Ship MVP of at least one serious offline [not progressive?] web app. We need to explore the space of possible use cases – to find bugs in the implementation, to expand our own understanding, to help developers [I would reverse the order of these reasons]. Much of the work of building even simple demo apps is app-related and not related to the underlying technologies. The leading candidate is Platatus, an app that offers a detailed, data-driven view of Mozilla's progress on delivering the technologies behind Progressive Web apps.** Platatus MVP - https://github.com/mozilla/platatus - minimal viable prototype of reference app that describes standardization/implementation status of web platform features
== Bug tracking ==
