MiniApps WG

Agenda

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

Logistics & Administrivia

• Welcome!
• Please, remind the W3C Code of Ethics and Professional Conduct and the Antitrust and Competition Guidance
• IRC: #miniapp
  • `q+` to add a question
• Scribe?

Status of the specs

• MiniApp Packaging
• MiniApp Manifest

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…) - Optional

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 Packaging
• MiniApp Manifest

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`?)

Next steps

1. MiniApp Elements & MiniApp API (Proposals)
2. MiniApp Performance (Discussion)

MiniApp HTML Elements and MiniApp API Baseline (Proposals)

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

1. Baseline for standard HTML elements
2. Baseline for Web APIs elements

Incubation in the CG.

Comments?

Next steps

1. MiniApp Elements and API (Proposals)
2. MiniApp Performance (Discussion)

MiniApp Performance (Discussion)

Some comments, requirements:

• Cross-platform development is a strong demand:
  1. modifying and optimizing DOM and HTML;
  2. a new engine and runtime mechanism? prioritizing performance and experience with a dual-engine approach.
• There are many different MiniApp DSLs

Bytedance's Presentation

Comments?