Last March 3rd, Flutter 2 was released, and among the key features announced, the output for Web was finally promoted to a production-ready state.
👍 Google recommends Flutter for Web as a production-ready tool for app-centric web apps like Games, SPA, PWA, and Mobile Apps looking to be present on the web.
👎 Flutter for Web isn’t yet a recommendation for DOM-centric demands on the web like Blogs, E-Commerces, SEO…
🏎 WebAssembly and WebGL are the resources explored under Flutter for Web “canvaskit” output to optimize performance and enhance the UX.
🔥 Flutter for Web brings to the web Skia, the same Graphic Engine used by Chrome and Android.
⚡️ Flutter for Web has two main renderer paths:
“html” for web apps loading on mobile devices due to small bundle size
“canvaskit” for web apps loading on desktop browsers due to performance optimization and design consistency but with larger bundle size.
🔌 There is also an “auto” render path that switches between “html” and “canvaskit” when the developer wants to use the user platform context to optimize on-demand.
🎨 Flutter for Web has full support for Cupertino and Material design systems.
🛠 Flutter for Web is stable for Chrome, Firefox, Safari, and Edge.
🧰 Flutter for Web offers opinionated features like gestures, custom URL strategies, web-app deep linking, and PWA basics output.
🤩 I don’t know if I will massively use Flutter for Web. Maybe on listtta.com, an app that I built using Flutter for Android/iOS.
Anyway, being a Flutter and Web enthusiast, I’ll keep tracking Flutter’s proposal for the web.
💌 If you want to receive content like this about Web Development, please, subscribe to my newsletter