Avalonia 12 · .NET 10 · Native AOT

Build desktop apps that feel native.

Manta is a UI toolkit and MVVM framework for Avalonia. Themeable controls, an explicit MVVM runtime and compile-time code generation — fully Native AOT compatible, without the ceremony.

dotnet add package ONEO.Manta

Everything you need, nothing you don't

Manta layers a focused control set, a predictable MVVM runtime and source generators on top of Avalonia.

M-prefixed controls
A broad set of controls plus themed styles for the Avalonia controls you already use.
Light and dark themes
Two palettes built on the OKLch color space, so both stay perceptually even.
Explicit MVVM runtime
Model, ViewModel, WindowModel and DialogModel base classes with no hidden magic.
Compile-time view creation
The [View<T>] attribute generates view plumbing, so models only declare their bindings.
Regions and tab navigation
RegionManager<T> opens, reuses and switches views with a single call.
Type-safe localization
Language keys are generated from YAML files and consumed through the {Lang} markup.

Native AOT, first-class

Manta is built for trimming and Native AOT. Publish a self-contained native binary with no JIT and no reflection surprises.

  • Reflection-free deploymentSource generators wire views and language keys at compile time, so no reflection-based discovery runs at startup.
  • Trim-safe by constructionThe library builds with IsAotCompatible, so the trimmer and the AOT analyzer stay clean.
  • Proven by the reference appMantaDemo publishes with PublishAot, exercising the whole toolkit in a native binary.
<PropertyGroup>
    <PublishAot>true</PublishAot>
    <PublishTrimmed>true</PublishTrimmed>
</PropertyGroup>
dotnet publish -c Release
$dotnet publish -c Release
Trimmed managed assemblies
Generated native code with ILC
Wrote a single native binary
MantaDemo published as a native binary
Native AOT0 trim · 0 AOT warnings

Use only what you need

Manta is not all-or-nothing. Every layer ships independently, so you can adopt localization, theming, MVVM or the control set on its own.

Localization only
Reference ONEO.Manta for the {Lang} markup and generated keys, and keep the Fluent theme and the standard Avalonia controls.Lang.Register(LangData.Load())
Theming only
Add <MantaTheme /> to Application.Styles to restyle Manta and the Avalonia controls. No base classes required.<MantaTheme />
MVVM only
Take Model, WindowModel, [View<T>] and RegionManager<T> while keeping your own look and theme.[View<Main>] sealed partial class Main_Model : WindowModel
Controls only
Drop the M controls and theme variables into an existing app with a hand-written ObservableObject and RelayCommand.dotnet add package ONEO.Manta
See the components-only and localization-only samples

Less ceremony, more product

Register the theme, pair a view model with its view and let the generator wire the rest.

using Avalonia;
using Manta;

static class Program
{
    [STAThread]
    public static void Main(string[] args)
        => MApp.Build<App>()
            .StartWithClassicDesktopLifetime(args);
}

Theming that stays consistent

Every color, size and radius flows through theme variables. Swap a resource dictionary and the whole application follows.

primary
secondary
muted
accent
border
foreground
  • OKLch color spaceLight and dark palettes share the same perceived lightness steps.
  • Theme variablesResolve colors and spacing through MBrush, MSize, MRadius and friends — never hardcode values.
  • One switch, two moodsMove between light and dark without touching a single control style.

Up and running in a minute

Manta targets .NET 10 and Avalonia 12. Add the packages, then build and run the demo.

1Add the library
dotnet add package ONEO.Manta
2Add the source generators
dotnet add package ONEO.Manta.Generators
3Explore the reference app
cd source && dotnet run --project MantaDemo
Requires the .NET 10 SDK. Native AOT publishing is fully supported.NuGet

Frequently asked questions

Short answers before you open the docs.

Ready to build with Manta?

Add the package, explore the demo, and shape the toolkit with us.