The Nuvyntra Labs .NET MAUI Development Ecosystem

A production .NET MAUI app is not one library. It is a UI, an application shell, a network contract, a local store, and a set of device and operations concerns. Most teams assemble those from overlapping community packages — CommunityToolkit for properties, Prism or Shell for navigation, Refit for HTTP, and a scatter of plugins for GPS, offline, and crash reporting. The seams are where field apps fail.

Nuvyntra Labs ships the stack as independently versioned products. NuvyntraLabs.UIKit is the Lumina presentation catalog. Plugin.Maui.MVVMExpress is the application shell. Plugin.Maui.HttpForge is the typed REST contract. The MauiEssentials gallery fills location, connectivity, persistence, security, media, and observability. Compose only what the app needs. There is no mega-package dependency.

Cross-platform MAUI work collapses when one vendor SDK owns UI, navigation, HTTP, and storage. Teams cannot adopt a chart control without taking a session manager. They cannot pin TLS without taking a retry policy they did not ask for. They cannot upgrade a GPS plugin without a breaking change in the form engine.

The opposite failure is a pile of unrelated NuGets with no shared host story. CommunityToolkit.Mvvm covers properties and commands. Prism.Maui covers page navigation, not Shell. ReactiveUI covers observable pipelines. A field or enterprise app often needs all three, plus bindable async state, lifecycle-aware cancellation, and a typed REST client that can sit on the same HttpClient as retry, cache, and SPKI pin.

• Independently versioned. UIKit 1.0, MVVMExpress 1.3, HttpForge 1.1, and each gallery plugin ship on their own SemVer lock.
• Compose at the host. The UI kit does not PackageReference Plugin.Maui.*. HttpForge does not retry, cache, or refresh tokens. Missing siblings fail closed instead of silently degrading.
• Adopt only what the app needs. A catalog app can take UIKit + MVVMExpress + HttpForge. A depot inspection app adds GeoLocator, OfflineSync, MediaPipeline, and FileVault.
• Honest boundaries. PDF viewers are viewers. NVBarcode generates; it does not scan. LocalStore is not OfflineSync. HttpForge is a MauiEssentials-shaped subset of Refit, not a drop-in replacement.

A typical MAUI product maps onto six layers. The first three are the pillars this paper names. The rest come from the gallery and from NuvexaDB when the host wants an embedded document file.

Registration stays at MauiProgram. The kit, the shell, and the REST client are three calls. Gallery plugins register the same way.

builder
    .UseMauiApp<App>()
    .UseNuvyntraUIKit()
    .UseMvvmExpress()
    .UseHttpForge();

builder.Services.AddHttpForgeClient<IFieldApi>(client =>
{
    client.BaseAddress = new Uri("https://api.example.com");
});

NuvyntraLabs.UIKit (1.0.0) is the Lumina catalog for a typical MAUI app: foundation tokens, 177 NV* controls from primitives through advanced surfaces, and 57 NV*View page recipes. Register with UseNuvyntraUIKit(), then use xmlns:nv="http://nuvyntralabs.com/uikit". Kit-level 1.0 is a working Lumina API — not Telerik or Syncfusion parity.

Recipes set titles and seed demo children so a team can stand up sign-in, catalog, checkout, inbox, or settings without inventing chrome. PDF, Docx, and Spreadsheet are viewers. NVBarcode generates; it does not scan. Real biometrics stay on Plugin.Maui.BiometricPlus. Compose FormValidation and KeyboardManager at the host — the kit does not take those dependencies.

XAML and every kit attribute: UIKit component reference

Plugin.Maui.MVVMExpress 1.3.0 is the application shell for production MAUI apps on Android, iOS, Mac Catalyst, and Windows (single-window). CommunityToolkit.Mvvm covers properties and commands. Prism.Maui covers page navigation, not Shell. ReactiveUI covers observable pipelines. A field app often needs all three plus bindable async state, lifecycle-aware cancellation, and typed navigation — without taking three overlapping frameworks. Core targets net10.0 and does not reference MAUI.

• ViewModels. ObservableModel, ViewModel lifecycle, and ViewModelCancellationToken cancelled on dispose.
• Commands. Sync and async commands with UI-thread marshal, timeout, retry, debounce, and throttle. ICommand.Execute does not throw.
• Hosts. UseNavigationPage and UseShell are equal hosts. Navigators hop to IMainThread before new Page() or Shell.GoToAsync.
• Forms & lists. FormViewModel.Bind, dirty confirm, SectionHostView in-place tabs, SnapshotCollection, MvvmSearch.
• Auth & deep links. UseAuth<TChallenge>() wraps GuardedNavigator. UseSecureSessionAuth() and UseDeepLinks() fail closed if the sibling is missing.
• Modules & generators. IModule / AddModule<T>(), [Notify], [RegisterView], [PersistState], [RequiresAuth]. Analyzers MVVME001–003 and MVVME010–013.
• Scaffold. dotnet new mvvmexpress / mvvmexpress-page, plus Visual Studio Code and Visual Studio Marketplace extensions pinned to 1.3.0.

1.0.0 remains the SemVer lock. Public 1.x APIs stay source-compatible. Capability work — captive portal, HTTP cache, offline sync, form XAML, flags, deep links — stays in focused gallery plugins. The testing package ships LeakProbe, FakeNavigator, FakeDialogs, and 1.0 contract tests.

ViewModels, hosts, generators, templates: MVVMExpress documentation

Plugin.Maui.HttpForge 1.1.1 is the contract layer. Declare GET, POST, PUT, DELETE, PATCH, and HEAD as a C# interface. The source generator emits the HttpClient implementation at compile time — there is no runtime reflection request builder. It is a MauiEssentials-shaped subset of Refit for Android, iOS, Mac Catalyst, and Windows, not a drop-in Refit replacement.

public interface IFieldApi
{
    [Get("/sites/{id}")]
    Task<Site> GetSite(int id, CancellationToken cancellationToken = default);

    [Post("/inspections")]
    Task<Inspection> Submit([Body] InspectionDraft draft);
}

var site = await api.GetSite(42);

1.1 adds the Refit-parity request surface: query objects, collection formats, naming presets, [Timeout] / [Url] / [PathPrefix], optional segments, [FormObject], IAsyncEnumerable streaming (JSON Lines / SSE), request compression, and AuthorizationHeaderValueGetter. Optional packages cover Testing, Newtonsoft.Json, and XML. Compile-time diagnostics are HFG001–HFG010.

Contract, analyzers, and sibling recipes: HttpForge documentation

The three pillars stand up UI, architecture, and the API contract. A shipped app still needs local data, a truthful network, sessions, field capture, and a way to see why a session failed. The product catalog is that gallery. The rows below are the libraries a development team actually reaches for — not the full index.

HttpForge is the contract. These plugins are the runtime the contract sits on — and the diagnostics when the OS says “connected” but the API is unreachable.

These are the libraries that show up once the app leaves the office — inspection, depot, POS, attendance, and always-connected field work.

An inspection or field-commerce app is the composition this ecosystem was built for. The table is a recommended set, not a required install.

A catalog or internal tool can stop at UIKit + MVVMExpress + HttpForge. A kiosk or POS add KeepAwake, DeviceOrientationPlus, Printing, and BluetoothManager. A VoIP surface adds VoipCore. The catalog is opt-in by design.

• UIKit is a UI library, not a MauiEssentials runtime plugin. It does not PackageReference Plugin.Maui.*.
• MVVMExpress does not own HTTP, location, or storage. Adapters compose siblings and throw if they are missing.
• HttpForge is the contract, not retry, cache, pin, or upload. Chain those on IHttpClientBuilder.
• LocalStore is CRUD. OfflineSync is the sync engine. JobQueue is planned work. RetryQueue is a failed call. FileVault is encrypted files. They do not replace each other.
• NuvexaDB is a standalone engine with its own white paper. LocalStore can host it; Data Studio stays on the engine.
• Most gallery plugins are Android + iOS. Do not assume Mac Catalyst or Windows unless the package page says so.
• **Plugin.Maui.\* restores from GitHub Packages**, not nuget.org. A project needs two feeds. GitHub Packages requires a token even when the packages are public.

1. Scaffold the host: dotnet new install Plugin.Maui.MVVMExpress.Templates then dotnet new mvvmexpress -n MyApp. Or install the MVVMExpress Visual Studio Code / Visual Studio Marketplace listings.
2. Add the GitHub Packages feed for Plugin.Maui.*. nuget.org remains the feed for Microsoft.*, UIKit, and public packages.
3. Register UseNuvyntraUIKit() and paint the first screen from an NV* recipe or a primitive.
4. Declare the API as an HttpForge interface and AddHttpForgeClient<T>(). Add ApiResilience or TlsPin only when the environment needs them.
5. Pull gallery plugins as the product requires them. Start with LocalStore if the app writes on-device; NetworkMonitor if the app must distinguish captive Wi-Fi from real internet.
6. Run maui-dev doctor before a store build. The getting-started guide is the install path; this paper is the map.

Every independently versioned plugin: Full product catalog

Nuvyntra Labs is the development ecosystem for teams who want to ship .NET MAUI apps without a mega-SDK and without an unmanaged pile of community packages. UIKit covers the rich UI. MVVMExpress covers the architecture. HttpForge covers the REST contract. The gallery covers the rest of development — local data, network truth, session, field capture, and operations — as focused plugins a team can name, version, and replace.

Research and public proofs still come first. When a pattern is reusable, it becomes a package. The catalog is the published form of that loop. Evaluate a pillar, compose a set, or contact the lab.