What is the Difference Between Blazor.Server and Asp.Net Web API? [closed]

Question

Blazor is one of those technologies that has me really excited to get started with. I am an experienced Asp.Net MVC and Web API (.Net Framework. not Core) developer. My first app that I am creating in Blazor is a PWA Web Assembly App with Individual User Accounts Hosted on Asp.Net Core using .Net 5.0. I've chosen to go the hosted route mainly because I want the Asp.Net Identity User Store functionality.

In my newly constructed Blazor Core Hosted Wasm PWA I have three projects.

1. App.Client
2. App.Server
3. App.Library

App.Server in many ways functions like an Api but it is different. One of those differences as far as I can tell is how it authenticates with App.Client. My question is two-fold in the fact that I want to know if other technologies/ clients like Xamarin.Forms can integrate with Blazor's App.Server... or can only Blazor Clients?

Second Question is that App.Server "seems" like an Api... but it is not. What are the differences specifically?

Answer 1

Blazor is designed to be used with html and create web content delivery applications. A Web API project has the similarities you've noted because they both exist as a content delivery service via web server. The difference is in the content you're delivering. Blazor is made for web pages, while an API project enables you to deliver data via REST endpoints.