MiniApps WG

Agenda

1. Logistics
2. Status of specs
3. New proposals

Logistics & Administrivia

• Welcome!
• Please, remember the W3C's Code of Conduct.
• IRC: #miniapp (you can use irc.w3.org)
  • `q+` to add a question
• Scribe?

Status of the specs

• MiniApp Lifecycle
• MiniApp Addressing
• MiniApp Widgets Requirements
• MiniApp Packaging
• MiniApp Manifest
• MiniApp Components

MiniApp Lifecycle

Specific events and an interface for the MiniApp object and its pages

MiniApp lifecycle:

launched, shown, hidden, error…

Page lifecycle:

loaded, ready, shown, hidden, unloaded

Status: WD

• Spec: https://www.w3.org/TR/miniapp-lifecycle/
• Repo: https://github.com/w3c/miniapp-lifecycle

Status of the specs

• MiniApp Lifecycle
• MiniApp Addressing
• MiniApp Widgets Requirements
• MiniApp Packaging
• MiniApp Manifest
• MiniApp Components

MiniApp Addressing

URIs for MiniApps

platform://miniapp/foo;version=1.0.1/pages/index?k=v#bar

https://platform.org/miniapp/foo;version=1.0.1/pages/index?k=v#bar

Status: Group Draft Note

• Spec: https://www.w3.org/TR/miniapp-addressing/
• Repo: https://github.com/w3c/miniapp-addressing

Status of the specs

• MiniApp Lifecycle
• MiniApp Addressing
• MiniApp Widgets Requirements
• MiniApp Packaging
• MiniApp Manifest
• MiniApp Components

MiniApp Widgets Requirements

Scenarios and requirements for MiniApp Widgets (particular MiniApp pages)

Placed in a specific area of a device

Status: Group Note

• Spec: https://www.w3.org/TR/miniapp-widget-req/
• Repo: https://github.com/w3c/miniapp-widget-req

Status of the specs

• MiniApp Lifecycle
• MiniApp Addressing
• MiniApp Widgets Requirements
• MiniApp Packaging
• MiniApp Manifest
• MiniApp Components

MiniApp Packaging

Describes the logical and physical structure of a MiniApp

• Pages, components, styles,…
• Packaging format, file-system, directories…
• Digital signatures (for developer, publishers, others…)

Status: WD

• Spec: https://www.w3.org/TR/miniapp-packaging/
• Repo: https://github.com/w3c/miniapp-packaging

Packaging: Open Issues

Security and efficiency concerns (TAG's Review):

1. Preservation of the origin model
   • UA SHOULD use SSL/TSL for distribution
   • UA SHOULD keep track of the origin (save it in manifest?, UA decides?)
2. Secure context (integrity of the package)
   • Package SHOULD be hashed (integrity);
   • and SHOULD be signed (e.g, developer + distributor)
3. Efficiency of ZIP container

Ongoing discussion.

Status of the specs

• MiniApp Lifecycle
• MiniApp Addressing
• MiniApp Widgets Requirements
• MiniApp Packaging
• MiniApp Manifest
• MiniApp Components

MiniApp Manifest

JSON document to describe a MiniApp

• Based on Web App Manifest (extends)
• 15 attributes with information for user agents (super-app, OS) and publishers (icons, descriptions, versions…)
• Runtime configuration (themes, colors, orientation…)

Status: WD

• Spec: https://www.w3.org/TR/miniapp-manifest/
• Repo: https://github.com/w3c/miniapp-manifest

Manifest Next: Internationalization

Localization of manifest members

Currently, MiniApps apply text localization techniques during the compilation stage

We must distribute texts in different languages and localize color schemes, icons, and images (good for marketplaces).

Next: alignment with Web App Manifest (working draft)

Manifest Next: Content Security Policy (CSP)

Increase security and integrity of MiniApps

• The system caches the MiniApp, and user agents do not always have access to HTTP headers.
• We need to guarantee security and avoid content and scripts from non-trusted origins.

Proposal: alignment with Isolated Web Apps (e.g., `permissions_policy`, `content-security-policy`, `integrity-block`?)

Status of the specs

• MiniApp Lifecycle
• MiniApp Addressing
• MiniApp Widgets Requirements
• MiniApp Packaging
• MiniApp Manifest
• MiniApp Components

MiniApp Components

Gap analysis of solutions in MiniApp implementations

• How to declare, reuse, access components
• Templating, content interpolation, styling, scripting...
• Built-in components (i.e., <image>, <ad>, <map>)

Status: Draft Community Group Report

• Spec: https://w3c.github.io/miniapp-components/
• Repo: https://github.com/w3c/miniapp-components/

MiniApp for IoT

Use cases of MiniApp for IoT devices

• ????

Status: Draft Community Group Report

• Spec: https://w3c.github.io/miniapp-iot/
• Repo: https://github.com/w3c/miniapp-iot/

Next steps

1. MiniApp Elements & MiniApp API (Proposals)
2. MiniApp Object Model (Proposal)

MiniApp HTML Profile (Proposal)

Objective: define a subset of common HTML elements required by MiniApp user agents (e.g., media, EPUB).

• Minimum set of standard HTML elements present
• Incubation in the CG.
• Based on the existing gap analysis (+ including other MiniApp implementations).

Comments?

Next steps

1. MiniApp Elements and API (Proposals)
2. MiniApp Object Model (Proposal)

MiniApp Object Model (Proposal)

Objective: define the document object model for MiniApps.

• Baidu? Tencent?

Comments?