"Blazor Web App" vs "Blazor WebAssembly Standalone App"?

Jonas Andersson

I'm about to starting a Blazor project in Visual Studio using a project template.
When filtering on C# and Blazor I'm presented with these two options:

1. Blazor Web App
"A project template for creating a Blazor web app that supports both server-side rendering and client interactivity. This template can be used for web apps with rich dymanic user interfaces (UIs)."

2. Blazor WebAssembly Standalone App
"A project template for creating a Blazor app that runs on WebAssembly. This template can be used for web apps with rich dymanic user interfaces (UIs)."

I'm a newbie when it comes to Blazor. Which alternative is the best here?

I also find this information when using Google:
"The following are some major Blazor disadvantages: The use of Blazor WebAssembly is not supported by all web browsers, including Internet Explorer, due to certain restrictions. The execution time of Blazor framework depends on the application weight, hence performance is affected by app's complexity."

So does this mean that the first option is the best? It doesn't say anything about WebAssembly.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Jonas Andersson2y ago
Thanks for helping out.
This was very well described.

Is there any option that is more suitable for consuming web services? I was thinking option 2.
Or could it be that Blazor is not suitable at all for web services?
Amit Mohanty2y ago
Blazor Web App (Server-side Blazor):
- Uses server-side rendering.
- UI updates are handled on the server, minimizing the amount of client-side code.
- Supports older browsers like Internet Explorer.
- Good for applications where real-time updates and complex interactions are not the primary focus.
- Generally better for applications where server-side resources are more abundant than client resources.
- Pros:
  
  Better compatibility with older browsers like Internet Explorer.
  
  Lower client-side resource requirements.
  
  Seamless integration with existing ASP.NET Core services and libraries.
- Cons:
  
  Limited client-side interactivity compared to WebAssembly.
  
  Server load increases with the number of concurrent users.
Blazor WebAssembly Standalone App (Client-side Blazor):
- Runs directly on the client's browser using WebAssembly.
- Provides a more responsive and interactive user experience since most of the app's logic runs on the client.
- Requires modern browsers that support WebAssembly (which excludes older browsers like Internet Explorer).
- App performance can be affected by the size and complexity of the application due to client-side execution.
- Suitable for applications needing high interactivity and responsiveness, where client resources are sufficient.
- Pros:
  
  More responsive user interfaces with less reliance on server round-trips.
  
  Ability to run offline once loaded.
  
  Performance benefits as browser capabilities improve.
- Cons:
  
  Initial load times can be longer due to downloading and compiling the WebAssembly code.
  
  Limited browser support, especially for older browsers like Internet Explorer.
Best Option:

If you prioritize compatibility with older browsers or have concerns about server load and want easier integration with existing ASP.NET Core services, Blazor Web App (Server-Side) might be more suitable.

If you are focused on building a highly interactive client-side application, are comfortable with modern browser requirements, and want to leverage the benefits of WebAssembly, Blazor WebAssembly Standalone App would be the better choice.