Standardization tasks

Aligned with the High-level-roadmap for System Application and related work, we have identified a list of standardization tasks that we need to get started with. We hope to get to a point where we have clear visibility and accountability for contributions from each team/site, assuming responsibility for sub-tasks of Cameo.

The page shares its basic structure and boilerplate with Development tasks for consistency.

Runtime and Security Model for Web Applications

On a high-level, we would like to see the Runtime and Security Model for Web Applications spec to better consider and address non-mobile use cases for desktop, IVI, TV. We believe the current spec is too focused on mobile use cases.

Tasks

• Multiple window support

Managing multiple windows is an important use case in non-mobile contexts. Hongbo Min started discussion, related to issue #98 and issue #100. We should revisit these issues and try get the spec better address non-mobile use cases.

• Window management

Related to the multiple window support, we need an improved model for window management. Event pages used by Chrome Packaged Apps is one such model to learn from. Related to issue #100.

• Event registration for system messages

Event registration is currently unspecified, see issue #73. Also related is the event registration in the event page model of Chrome Packaged Apps.

• Privileged applications extensions (Anssi)

APIs that are not web-facing should be split into their own specification. Anssi proposed on the public-sysapps to split ApplicationManagement interface and other parts of the Runtime spec relevant to privileged applications only into their own spec. Related to issue #4 and issue #92.

• Clarify design principles, scope, use cases, and the structure of the spec (Anssi)

We need to clarify design principles, scope, use cases, and make sure they align with our high-level goals. Anssi started discussion on public-sysapps. Related to issue #43, issue #95, and issue #97.

• Application lifecycle

TBD