Avalonia, Uno, WinUI, and WPF
Framework Bridges
Bring the GPU substrate into an existing XAML application model.
Explore source ↗Capability
Framework and platform packages connect ProGPU presentation, controls, charts, media, and interop to Avalonia, Uno Platform, portable WinUI, LibreWPF, LibreWinForms, Android, iOS, and the browser.
- 01
Avalonia 11/12 and Uno integration
- 02
Portable WinUI, WPF, and WinForms compatibility
- 03
Android Vulkan, iOS Metal, and browser WebGPU hosts
- 04
Shared typed GPU backend underneath
How it composes
From intent
to working system.
Framework
XAML, properties, input, and lifecycle remain native to the host.
Adapter
Integration packages translate framework state into ProGPU resources and visuals.
Scene
Shared vector, text, scene, and compute packages prepare work.
Backend
WebGPU presents through the selected platform surface.
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 ProGPU.Uno --prerelease<PackageReference Include="ProGPU.Avalonia" Version="VERSION" /><PackageVersion Include="ProGPU.Avalonia" Version="VERSION" /><progpu:GpuView Render="{x:Bind ViewModel.Render}" />Modules in this capability
Use one layer.
Compose the rest.
Avalonia integration and control hosting.
↗02ProGPU.UnoUno Platform integration.
↗03ProGPU.WinUIWinUI controls and presentation.
↗04LibreWPF.InteropWPF-compatible compositor interop.
↗05ProGPU.AndroidNative Android SurfaceView and Vulkan/WebGPU host.
↗06ProGPU.iOSNative UIKit, CAMetalLayer, and Metal/WebGPU host.
↗07ProGPU.BrowserBatched WebAssembly dispatcher and navigator.gpu host.
↗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.