Native framework presentation
Avalonia & Uno Hosts
Compose a packaged web-authored surface inside a native XAML application lifecycle.
Explore source ↗Capability
Avalonia and Uno hosts expose the same packaged component model while retaining each framework’s application lifecycle and native composition boundary.
- 01
Avalonia reference presenter
- 02
Uno Skia desktop presenter
- 03
Shared packaged component lifecycle
- 04
Native input and scene integration
How it composes
From intent
to working system.
Component
A trusted package supplies scripts, assets, manifest, and entry point.
Runtime
The native engine owns script, document, layout, and paint state.
Presenter
Framework-specific backends consume scene updates and route lifecycle and input.
Application
Avalonia or Uno owns the surrounding windows, navigation, services, and deployment.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package WebScene.Sdk.Avalonia --prerelease<PackageReference Include="WebScene.Backend.Avalonia" Version="VERSION" /><PackageVersion Include="WebScene.Backend.Avalonia" Version="VERSION" /><webscene:WebSceneView Component="dashboard" HostCapabilities="{Binding Capabilities}" />Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.