Modular Web Engines

• Upcoming
• Tentative
• Breakout Sessions

Beyond pure web apps, WebViews are essential for cross-platform development. Frameworks like Cordova, React Native, Electron, Tauri, and many others prove that. Other relevant use cases are: MiniApps, whose SuperApps implement dedicated embedded web engines for content rendering; EPUB readers; and infotainment systems. These domain-specific use cases sometimes do not require a full-fledged WebView with a full implementation of Web standards. Indeed, these platforms use hybrid technologies that are inspired by Web standards (e.g., restricted CSS modules, HTML subsets, and JavaScript APIs). Occasionally non standard features are added and can create fragmentation.

This breakout session aims to discuss the design and use of modular web engines, considering the concrete constraints of the application scenario and the benefits for potential new use cases, including the homogeneous implementation of cross-platform MiniApps, WoT apps, and AI agents. These hybrid platforms could benefit from these modular standards-based application profiles (i.e., subsets of current specifications) to reduce the size of engines, thereby increasing efficiency while maintaining compatibility with existing standards.

Some questions to be addressed during the session:

• How these modular Web engines support the growth of the Web without bringing fragmentation?
• How do new web engines define their roadmap and development priorities?
• Could the existing Web DevX tools (e.g., WPT, CanIUse, CanIWebView, Web-Features, …) support the development of new engines for these purposes?

Agenda

Chairs:
Martin Alvarez-Espinar, Niklas Merz

Description:
Beyond pure web apps, WebViews are essential for cross-platform development. Frameworks like Cordova, React Native, Electron, Tauri, and many others prove that. Other relevant use cases are: MiniApps, whose SuperApps implement dedicated embedded web engines for content rendering; EPUB readers; and infotainment systems. These domain-specific use cases sometimes do not require a full-fledged WebView with a full implementation of Web standards. Indeed, these platforms use hybrid technologies that are inspired by Web standards (e.g., restricted CSS modules, HTML subsets, and JavaScript APIs). Occasionally non standard features are added and can create fragmentation.

This breakout session aims to discuss the design and use of modular web engines, considering the concrete constraints of the application scenario and the benefits for potential new use cases, including the homogeneous implementation of cross-platform MiniApps, WoT apps, and AI agents. These hybrid platforms could benefit from these modular standards-based application profiles (i.e., subsets of current specifications) to reduce the size of engines, thereby increasing efficiency while maintaining compatibility with existing standards.

Some questions to be addressed during the session:

• How these modular Web engines support the growth of the Web without bringing fragmentation?
• How do new web engines define their roadmap and development priorities?
• Could the existing Web DevX tools (e.g., WPT, CanIUse, CanIWebView, Web-Features, …) support the development of new engines for these purposes?

Goal(s):
Discussion on new requirements and W3C activities for the web ecosystem

Agenda:

• Intro and background on the challenge (Chairs - 15')
• Design of a new embedded browser (Servo - 10')
• [feedback is welcome here, just bring your idea]
• Open questions and discussion (All - 30')

Materials:

• Session proposal on GitHub

Joining Instructions

Instructions are restricted to W3C users . You need to log in to see them.

Export options

Personal Links

Please log in to export this event with all the information you have access to.

Public Links

The following links do not contain any sensitive information and can be shared publicly.

• Download as ics