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

The 6.6 release shifts Uno Platform toward tighter runtime performance by introducing native ahead-of-time (AOT) compilation for five major targets. This replaces just-in-time (JIT) compilation at startup, which the team reports can shrink launch times by roughly a fifth to over half depending on the platform. Existing projects can continue using JIT, but moving to AOT requires enabling the new publishing mode and testing the resulting binaries. The change is confined to the Uno runtime; any external native libraries remain unaffected.

A new optional Vulkan rendering backend is added for Windows, Linux, and Android, while the default Skia-based OpenGL path stays unchanged. Developers must explicitly opt-in to Vulkan, and Apple platforms continue using Metal, with WebAssembly still on WebGL. Reported per-frame rendering costs can drop by as much as half, which is most relevant for animation-intensive or 3D-heavy apps. Because Vulkan is not the default, existing builds will not break, but performance-critical workloads may need to be re-benchmarked after the switch.

XAML authoring sees several convenience upgrades: the WinUI presentation namespace and the x: namespace are now implicitly available, and a shared GlobalNamespaces.xaml file can centralise namespace declarations. Pages that declare x:Class can automatically receive generated code-behind files, allowing pure XAML pages without empty .xaml.cs stubs. These changes reduce boilerplate but do not alter the underlying compilation model, so existing tooling pipelines remain compatible.

The Model Context Protocol (MCP) servers for both the application and documentation now self-register with supported AI-assisted development agents such as Visual Studio, VS Code Copilot, Claude Code, and others. This enables agents to inspect a running Uno app or pull documentation without manual configuration. Not all agents have implemented the registration hook yet, so developers should verify compatibility with their preferred tooling before relying on the feature.

Accessibility and multilingual text handling have been broadened for Skia-rendered targets, adding screen-reader support on Windows, macOS, and WebAssembly, and full IME composition for Asian languages across all primary platforms. Android and iOS screen-reader integration is still in progress, and Linux support is slated for a future update. Additionally, the release expands WinUI API coverage (e.g., geometry transforms, drag-and-drop, WebView2) but notes that support levels vary per target, so developers must consult the platform-specific notes when using these newer APIs.