.net 9

In .NET 9 (and earlier from .NET 6+), a MAUI Hybrid model project refers to a .NET MAUI (Multi-platform App UI) application that combines native app development with web technologies — specifically Blazor.

What is MAUI Hybrid?

.NET MAUI Hybrid combines:

• .NET MAUI: For building native mobile/desktop apps (Android, iOS, Windows, macOS)

• Blazor: For building interactive UI using HTML, CSS, and C# (instead of JavaScript)

In a hybrid project:

• You write the UI in Razor/Blazor components

• It's rendered inside a native WebView in the MAUI app

• You can interact with native device APIs (camera, GPS, file system, etc.)

• You can share code across web and native platforms

In .NET 9, MAUI Hybrid Apps allow you to build applications that combine native UI + Blazor UI in a single app.

• MAUI (Multi-platform App UI): Framework to build native apps (Android, iOS, Windows, macOS) with C# and XAML.

• Blazor Hybrid: Lets you use Blazor components (Razor + C# + HTML + CSS) directly inside a native MAUI app.

So a MAUI Hybrid project is a .NET MAUI app that embeds a BlazorWebView control, which hosts your Blazor components locally (not from a server).

Why use Hybrid?

• You want cross-platform native features (camera, GPS, notifications, file system) and

• You want to reuse existing Blazor components (web-like UI) inside your app.

This avoids rewriting everything in XAML if you already have Blazor-based business logic or UI.

Example Project Structure

When you create a .NET MAUI Blazor Hybrid App, you’ll see:

• MauiProgram.cs → App startup (register services, fonts, handlers).

• MainPage.xaml → Contains where your Blazor UI is rendered.

• wwwroot/ → Static assets like CSS, JS (same as Blazor Web).

• Pages/ → Razor components (.razor files) for UI.

• Platforms/ → Platform-specific code (Android, iOS, Mac, Windows).

Conclusion: A MAUI Hybrid Model Project in .NET 9 = A native cross-platform app where you can use both MAUI XAML UI and Blazor (web-style UI) together in one solution.