Uno Platform 6.6 delivers Native AOT publishing across Android, iOS, Linux, macOS, and Windows, cutting application startup times by as much as 61 percent on Android and 21 percent on iOS in tests. Uno Platform, which enables developers to create applications for Windows, WebAssembly, Android, iOS, macOS, and Linux through WinUI-style XAML and .NET, released version 6.6 with a focus on runtime performance and closing functionality gaps between WinUI APIs and the framework's Skia-based targets. The update also introduces an optional Vulkan rendering backend, automatic registration for Model Context Protocol servers, reduced XAML boilerplate, expanded cross-platform WinUI API coverage, and enhanced accessibility and multilingual text handling.
The most substantial runtime change is Native AOT support for five platforms. Native AOT compiles application code in advance rather than depending on just-in-time compilation during startup. Uno reported startup gains between 21 percent on iOS and 61 percent on Android when testing with its Chefs sample application on .NET 10, though outcomes will vary based on application architecture, hardware specifications, and deployment settings. JIT-based publishing continues to be available. The release also adds an opt-in Vulkan backend for Windows, Linux, and Android, while OpenGL stays the default Skia backend on those systems, Apple platforms keep using Metal, and WebAssembly continues with WebGL. According to the Uno team, Vulkan cut per-frame rendering costs by up to 50 percent in certain tests, making it a potentially valuable option for animation-heavy or graphics-intensive software.
The release simplifies XAML authoring by automatically including the standard WinUI presentation namespace and the x: namespace, allowing developers to define shared namespaces centrally in a GlobalNamespaces.xaml file. Pages that declare x:Class can now receive generated code-behind classes automatically, enabling XAML-only pages to exist without an otherwise empty .xaml.cs file, though manual code-behind remains available when applications require constructors, event handlers, or lifecycle overrides. For AI-assisted workflows, Uno's App MCP and Docs MCP servers can now register themselves with supported development agents, with the App MCP exposing a running application to an agent for inspection and interaction while the Docs MCP provides access to current Uno documentation.
The update broadens WinUI compatibility with APIs for projections, geometry transforms, text highlighting, spell checking, flyouts, clipboard operations, drag and drop, and WebView2, though exact support levels differ by target platform. Accessibility support has expanded for applications rendered through Skia, with screen readers now able to access Uno interfaces on Windows, macOS, and WebAssembly, while Android and iOS support remains in development and Linux support is planned. The release provides complete Input Method Editor composition for multi-keystroke Asian languages across all primary Uno targets and introduces automatic font fallback for interfaces containing multiple writing systems. Other additions include animated WebP playback and Mica and Acrylic window backdrops on macOS, with SkiaSharp 4.x available as an opt-in dependency while Uno 6.6 defaults to SkiaSharp 3.x.
Developers upgrading existing applications must update the Uno SDK entry in global.json and consult the migration guide for project-specific changes, with further details, benchmarks, setup instructions, and API coverage notes available in the Uno Platform announcement, GitHub release notes, and documentation. The emphasis on Native AOT and Vulkan rendering reflects broader industry pressure to deliver desktop-class performance across mobile and web targets without sacrificing cross-platform reach. Organizations evaluating Uno will need to weigh the startup and rendering gains against the integration effort required to migrate existing WinUI codebases and test behavior across six distinct operating environments.