Then came WebView2. Microsoft’s answer to native embedding of modern web technologies seemed perfect—until developers hit the distribution problem . Should you ship the fixed, 200MB "Fixed Version" runtime with your app? Or ask your user to download the "Bootstrapper"?
That’s it. You now have an Evergreen-powered hybrid app. There is an emerging environmental angle to Evergreen that is rarely discussed: Reducing redundant binaries. evergreen webview2
CoreWebView2Environment? env = null; try { env = await CoreWebView2Environment.CreateAsync(); } catch (WebView2RuntimeNotFoundException) { // Fallback to a fixed version you bundled in a subfolder env = await CoreWebView2Environment.CreateAsync( browserExecutableFolder: "./FixedWebView2/" ); } Evergreen does not prevent you from isolating profiles. For a multi-tenant app, you can launch different WebView2 instances with different user data folders, leveraging the same shared runtime binaries. Then came WebView2