Uno Platform 6.6 Adds Native AOT, Vulkan Rendering, and Broader Accessibility Support

Uno Platform 6.6 ships Native AOT publishing across five target platforms, an optional Vulkan rendering backend, and automatic registration for the framework’s Model Context Protocol servers. The release also reduces XAML boilerplate, expands cross-platform WinUI API coverage, and improves accessibility and multilingual text handling, as reported by Edin Kapić on InfoQ.

Native AOT publishing means builds can compile ahead of time on those five targets instead of relying on a JIT-heavy path at startup. The Vulkan backend sits as an optional rendering path rather than a forced default, so teams can keep existing graphics stacks or opt into GPU-oriented composition where the platform supports it. Automatic MCP server registration wires the framework’s Model Context Protocol endpoints without manual setup steps, and the XAML and WinUI surface work aims to cut repetitive markup while aligning more of the shared API set with WinUI expectations.

For engineers shipping .NET UI across desktop and mobile from one codebase, Native AOT is the lever that usually shortens cold start and shrinks the runtime tax on constrained devices. Broader WinUI API coverage lowers the cost of porting controls and patterns that already exist on Windows. Accessibility and multilingual text fixes matter for products that must pass audit gates and ship outside a single locale without forking layout logic per platform.

In the cross-platform .NET UI field, Uno competes on fidelity to WinUI-style APIs and on how little platform-specific glue a team must own. Vulkan as an optional renderer is a direct bid for graphics-heavy or latency-sensitive clients. MCP auto-registration places the stack next to agent-tooling workflows that already expect Model Context Protocol servers, rather than treating AI integration as an aftermarket bolt-on.

If you are already on Uno, evaluate Native AOT on your five target platforms first and measure startup size and cold-start behavior against your current publish profile. Treat Vulkan as an opt-in experiment on the surfaces that hit GPU limits today. Check how much of your XAML and WinUI-shaped code can drop custom wrappers under the expanded API coverage, and verify accessibility plus multilingual text paths against your existing audit and localization suites. Watch whether MCP registration stays automatic and stable as you adopt agent tooling against the same app process.