State of WebViews - Can we fix things?

<p><a href="https://caniwebview.com/about/">WebViews</a> are everywhere—but fragmented, inconsistent, and often invisible to web developers. Used for in-app browsers, hybrid apps, and <a href="https://www.w3.org/groups/wg/miniapps/">MiniApps</a>, WebViews form a significant part of the web platform that many developers unknowingly target. Some developers specifically build for WebViews in hybrid apps or MiniApps, while others create standard websites without realizing they'll run in WebView contexts with different behaviors and constraints. </p> <p>Through initiatives like <a href="https://caniwebview.com/baseline">Baseline</a>, <a href="https://caniwebview.com">CanIWebView</a>, <a href="https://caniwebview.com/apps">apps</a>, and the <a href="https://github.com/WebView-CG">WebView Community Group</a>, we're working to map this fragmented landscape and identify paths forward. MiniApps that are very popular in some markets also show a very strong fragmentation and very little standardization. With collaboration and improvements between WebViews, MiniApps, PWA, new technologies like <a href="https://chromeos.dev/en/web/isolated-web-apps">Isolated Web Apps</a> or new engines like Servo there is good potential to improve the web in this space, but it's complicated.</p> <p>The <a href="https://www.w3.org/community/webview/">W3C WebView Community Group</a> was formed to identify, understand, and reduce the issues arising from the use of software components (typically referred as WebViews) that are used to render Web technology-based content. As member and co-chair of the community group I'd like to give a little overview what WebViews are today, the work we've done to improve interoperability, and call to action to "fix things" in this overlooked but critical part of the web platform.</p>