3 ms·

As a Microsoft shop: Any experience with Blazor and PWA? I find Blazor very awesome for developing an App using WebAssembly. When using it as a PWA and caching

by oaiey 3y ago

As a Microsoft shop: Any experience with Blazor and PWA? I find Blazor very awesome for developing an App using WebAssembly. When using it as a PWA and caching the .NET runtime locally etc, the combination of productivity and ease of deployment could be theoretically really awesome.

asabla 3y ago
Built an application using strictly Blazor wasm for my last assignment (so .Net 7). It wasn't a easy ride (especially when it comes to LSP support for razor pages). But the overall experience was pretty decent. Almost half of our users preferred to use the application as a PWA (using windows 10 and edge) instead of an ordinary tab in your browser. Somethings to consider tho: Upgrades to service workers and what not can be a bit challenging depending on your situation. Keep in mind that a lot of firewalls and antivituses may block all those binary downloads (since it's just dll files). There are ways around it ofc, but still expect files to be blocked. Authorization changed between .net 7 and 8. So make sure you understand what these changes are (if you use packages from Microsoft)
- oaiey 3y ago
  Editing in VS Code is really bad right now. It got worse actually. The dll/firewall should be solved in .NET8 since the browser stack defined a native format (cil I think). Thanks for the pro tips!!!
bob1029 3y ago
Yes. Tons with server-side Blazor apps. We currently use Blazor for our internal admin UIs, but at this point I'd never put it in something customer facing (even in B2B setting). We haven't played with the client-side WASM stuff, but the conclusion is that server-side blazor is not a fantastic technology if you want something that "just works". Websockets in particular are kind of nasty when you have a client device ecosystem where screens and apps are frequently changing activity state. Stateless forms are much easier to reason about. iOS/Safari is very aggressive with closing down unused resources. Stateless forms can survive for days on those user agents. Our blazor apps would require refreshes after a few minutes of inactivity. Vanilla web forms & SSR is what we run with today. Our "framework" is to use string verbatim & interpolation operators in C# to compose our responses. Looks something like PHP and has zero dependencies.
- oaiey 3y ago
  Yeah, server side blazor is IMHO a bad product. Blazor with wasm on browser or PWA or Blazor with MAUI and a web view (without wasm) is the deal.
Kuraj 3y ago
Personally I am in love with Avalonia UI for client-side because it just feels like WPF/Silverlight done right. I can use all my WPF knowledge to develop cross-platform PWA apps. It's the shit.

by oaiey 3y ago

asabla 3y ago

Built an application using strictly Blazor wasm for my last assignment (so .Net 7). It wasn't a easy ride (especially when it comes to LSP support for razor pages). But the overall experience was pretty decent. Almost half of our users preferred to use the application as a PWA (using windows 10 and edge) instead of an ordinary tab in your browser. Somethings to consider tho: Upgrades to service workers and what not can be a bit challenging depending on your situation. Keep in mind that a lot of firewalls and antivituses may block all those binary downloads (since it's just dll files). There are ways around it ofc, but still expect files to be blocked. Authorization changed between .net 7 and 8. So make sure you understand what these changes are (if you use packages from Microsoft)

oaiey 3y ago
Editing in VS Code is really bad right now. It got worse actually. The dll/firewall should be solved in .NET8 since the browser stack defined a native format (cil I think). Thanks for the pro tips!!!

bob1029 3y ago

Yes. Tons with server-side Blazor apps. We currently use Blazor for our internal admin UIs, but at this point I'd never put it in something customer facing (even in B2B setting). We haven't played with the client-side WASM stuff, but the conclusion is that server-side blazor is not a fantastic technology if you want something that "just works". Websockets in particular are kind of nasty when you have a client device ecosystem where screens and apps are frequently changing activity state. Stateless forms are much easier to reason about. iOS/Safari is very aggressive with closing down unused resources. Stateless forms can survive for days on those user agents. Our blazor apps would require refreshes after a few minutes of inactivity. Vanilla web forms & SSR is what we run with today. Our "framework" is to use string verbatim & interpolation operators in C# to compose our responses. Looks something like PHP and has zero dependencies.

oaiey 3y ago
Yeah, server side blazor is IMHO a bad product. Blazor with wasm on browser or PWA or Blazor with MAUI and a web view (without wasm) is the deal.

Kuraj 3y ago

Personally I am in love with Avalonia UI for client-side because it just feels like WPF/Silverlight done right. I can use all my WPF knowledge to develop cross-platform PWA apps. It's the shit.