The Future of Cross Platform Blazor
summary
Comparison of concrete targets and demos: a responsive PWA (manifest + service worker, installable, limited Apple support) runs as WebAssembly in the browser so it’s fine for UI but too slow for heavy tasks (demo notes avoid client PDF generation); Electron.NET (Blazor Server, full .NET runtime, .NET 5, file-system access) boots via electronize, shows reading the Documents folder and gives native desktop speed but is memory hungry and desktop-only; Blazor Hybrid with .NET MAUI (BlazorWebView, full runtime, shared Razor class library) embeds Blazor in a WebView2, supports Windows/Mac/iOS/Android, runs heavy work locally and shares UI across web, desktop and mobile projects.
AI-written summary · about
chapters (9)
- 0:00Blazor cross-platform future
- 1:35Responsive design with Blazor WASM
- 6:56Limitations of responsive Blazor
- 7:17Progressive Web Apps in Blazor
- 15:44Blazor on Electron
- 28:38Blazor Hybrid with .NET MAUI
- 37:11Comparing Blazor options
- 38:13Sharing UI across Blazor
- 45:17Q&A
related talks
58mThe Future of Cross-Platform Blazor
58mBlazor Hybrid - Build Hybrid Mobile, Desktop, and Web apps with .NET MAUI
01h 01mBlazor, a new framework for browser-based .NET apps
31mBuilding desktop apps using .NET MAUI and Blazor
46m.NET: What's Blazor - Front .NET
47mBlazor - Next Generation UI with .NET 6
01h 01mBlazor, a new framework for browser-based .NET apps
52mThe Blazor Multiverse: get to know the different Blazor frameworks
