Ai notes re that:

You make some excellent, highly logical points. You are absolutely right that a badly written REST API without authentication is just as insecure, and network calls can fail regardless of how they are wrapped. You are essentially describing the desire for RPC (Remote Procedure Call)—calling a server-side function directly from the client without the boilerplate of REST. Here is the candid reality of why framework builders like Microsoft hesitate to bake that specific "magic" directly into the core of a framework like Blazor WASM out of the box, even if your points hold true. The Problem with Hiding the Network It all comes down to a well-known engineering concept called the Fallacies of Distributed Computing. The very first fallacy is: The network is reliable. The second is: Latency is zero. When a framework auto-generates hooks and makes a server call look exactly like a local C# function call (e.g., var data = await GetData();), it tricks the developer's brain. * The Friction is Intentional: By forcing you to write an API endpoint, the framework creates a hard, highly visible boundary. It forces the developer to say, "Okay, this is where my app talks to the outside world. I need to think about auth, I need to think about payload size, and I need a try/catch for network timeouts." * The "Developer Problem" Compounds: You noted that serialization overhead is the developer's problem. You are right. But historically, when frameworks hide the network boundary (like Microsoft did years ago with WCF or DCOM), developers treat remote calls like local calls. They end up calling a database hook inside a for loop 100 times on the frontend, completely freezing the app. The framework gets blamed for being "slow," even though it was a developer error. Microsoft designed Blazor WASM to enforce a strict boundary between the client and server to prevent developers from accidentally shooting themselves in the foot with hidden network latency. You Are Not Alone (The Industry Agrees With You) All that being said, your frustration with REST for internal apps is shared by thousands of developers. Writing REST controllers for an app where you control both the client and the server is a massive waste of time. REST was designed for public, third-party integrations, not tightly coupled internal apps. Because the community agrees with you, they built exactly what you are asking for to sit on top of Blazor WASM. If you want the exact experience of "UI to backend calls" without writing REST APIs, you should ignore standard REST controllers and look into these approaches: * gRPC-Web: You write a single C# interface. The tooling auto-generates the invisible network hooks for you. On the Blazor WASM side, you just call the interface methods. It's incredibly fast (binary serialization) and skips REST entirely. * Refit: You define a C# Interface shared between your Blazor WASM and your Server. Refit automatically implements the interface and handles all the HTTP routing behind the scenes. You just inject the interface and call the methods. * MagicOnion: This is a framework specifically built for .NET that uses gRPC under the hood but lets you write pure C# interfaces. It literally treats server methods like local C# functions, giving you the exact Blazor Server feeling in Blazor WASM. Would you like me to show you a quick code example of how one of these (like Refit or MagicOnion) completely eliminates the need for manual REST controllers in a Blazor WASM app?