Marketplace/TV

From New wiki
Jump to navigation Jump to search
The Marketplace has been placed into maintenance mode. It is no longer under active development. You can read complete details here.

Overview

Firefox OS will be used as a platform for TV. This means that there are two distinct efforts required:

  1. Creation of a TV-specific UI
  2. Augmentation of the back-end/API to support TV content


Background materials

Legacy

Current


Content for TV

Content for TV is confined to hosted apps and websites.

NEEDED: content guidelines.


Proposed Phases

  1. Initial launch – only 5-10 big name sites, ~10 webapps (hosted). Content Services will need to verify the regions the content works in (is accessible to). Data will be imported by Mozilla, not submitted by the public. Like with webapps, we'll use a language for the listing (if we have it), default to English if we don't.
  2. Subsequent launch – requires submission tool. The other websites content (MOWs) also does not have a submission tool.


Engineering information


QA info

To install the simulator, follow the instructions on https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/TVs_connected_devices#Developing_TV_apps.

Note: When running the simulator, the three notes following are important. Both the b2g-bin path and the profile path will be specific to your installation. The if you start at a 1600x900 resolution setting, it may be too big and you'll merely see a black screen in the simulator; try reducing the resolution setting until you see the UI (I defaulted to a 50% ratio, which worked enough for me to know that everything was installed correctly).


Back-end Sprint plan

  • Sprint 1: 2015/11/10 - 2015/11/16 (roughly)
  • define/document API specs and disseminate: 1223643 this should allow for the creation of a mock API for front-end development to use, with minimal changes required for true integration.
  • Sprint 2: 2015/11/18 - 2015/11/26 (roughly)


Back-end bugs

Tracking bug: 1205499

<bugzilla> { "blocks": ["1205499"], "status": ["UNCONFIRMED", "ASSIGNED", "NEW", "REOPENED", "RESOLVED", "VERIFIED"], "include_fields": "id, summary, priority, status, resolution" } </bugzilla>

Front-end bugs

Tracking bug 1204762

<bugzilla> { "blocks": ["1204762"], "status": ["UNCONFIRMED", "ASSIGNED", "NEW", "REOPENED", "RESOLVED", "VERIFIED"], "include_fields": "id, summary, priority, status, resolution" }

</bugzilla>