Uno Platform 7.0: 2x faster, 5x smaller, built for the agentic era

Uno Platform 7.0 is out. By commits, files, and lines changed, it is the largest release we have shipped.

AI agents can write code faster than ever. What turns that code into a great application is the foundation underneath it: how fast it runs, how small it ships, how many platforms it reaches, and how faithfully it behaves the way you and your agents expect. Uno Platform 7.0 strengthens every one of those layers.

Alongside it, we are releasing Uno Platform Studio 3.3, a workbench where developers and AI agents create applications together, built on that same foundation.

What’s new in Uno Platform 7.0:

Built in step with Microsoft, Uno Platform 7.0 brings the latest .NET and Windows UI innovations to more platforms while deepening our contribution to the open-source foundations that power them.

Getting started takes minutes with Uno Platform Studio, from your browser or your desktop.

Uno Platform 7.0 by the numbers.

Performance was a cornerstone of this release, and you should feel it the moment you run your application on 7.0: pages come up faster, lists scroll more smoothly, and there is less memory churn. These gains come from years of optimization work under the surface.

Uno Platform 7.0 vs 6.7, on the same benchmarks.

The result is a smoother UI under load and, on battery-powered devices, real power savings.

Every frame counts. On a 120 Hz screen, scrolling only looks smooth when the content moves on every frame. In 7.0, scrolling is synchronized with the display’s refresh rate, so lists glide with natural momentum and flings feel native.

Frame coverage while scrolling, 7.0 vs 6.7.

Improvements on specific platforms.

A pluggable rendering architecture lets you adopt new rendering technology without rebuilding your apps, and cuts platform-specific maintenance.

Uno Platform 7.0 unifies rendering across Android, iOS, tvOS, WebAssembly, Windows, macOS, and Linux: consistent results and fixes that apply everywhere, while native features such as maps and video players stay reachable.

SkiaSharp 4 is the default

The Skia backend now ships on SkiaSharp 4 by default, the first major SkiaSharp version built with Uno Platform as a co-maintainer alongside the .NET team at Microsoft. That gives our engineers a direct role in SkiaSharp’s releases, triage, and roadmap, so issues that affect cross-platform rendering get fixed faster. On Android, Windows, and Linux it now renders through Vulkan by default.

A new WebGPU backend

WebGPU joins Skia as a rendering option in Uno Platform 7.0, available on Windows, Linux, macOS, Android, iOS, and WebAssembly. It gives you a choice in how your app is drawn, without tying you to one rendering technology.

This works because drawing now goes through a backend-neutral layer underneath the compositor. The WebGPU backend is built on wgpu-native on desktop and mobile, and on the browser’s own WebGPU support in WebAssembly. The same layer brings managed, SkiaSharp-free implementations of geometry, fonts, image decoding, and SVG.

Rendering with the WebGPU backend can bring sizeable gains. Depending on the scene, we have measured up to a 50% improvement in frames per second.

An app that uses only WebGPU ships without SkiaSharp at all, which removes about 6 MB of uncompressed native code from WebAssembly apps: smaller downloads for your users, and a more flexible foundation for future rendering technologies.

To try it, add WebGpu to your UnoFeatures and register the backend on your host builder. WebGPU is experimental and opt-in for now, so give it a spin and tell us what you build with it.

Bring your own WebGPU code. The new WebGpuCanvasElement lets you draw with your own WebGPU commands inside your UI, on the same device the rest of your app renders with and with no copy, so a custom 3D view or visualization sits beside your XAML like any other control.

The .NET ecosystem is strongest when developers can build on what already exists instead of starting over, and this release takes another step in that direction.

Third-party .NET MAUI controls, now on every Uno Platform target. With .NET MAUI Embedding, Uno Platform developers have long been able to use controls from the leading .NET component vendors, such as Syncfusion, Telerik, Infragistics, DevExpress, and Esri, along with the .NET MAUI Community Toolkit, inside their Uno Platform apps. Until now, those controls only ran on the targets .NET MAUI itself supports: iOS, Android, macOS, and Windows. Uno Platform 7.0 removes that limit. The same third-party .NET MAUI controls now work everywhere Uno Platform runs, including the web and Linux, so the charts, data grids, maps, and editors you already license can follow your app to every platform it targets, without waiting for native ports or rebuilding your UI.

.NET MAUI apps in the browser and on Linux. .NET MAUI developers get the reverse: bring an existing app to the browser and Linux through our .NET MAUI handlers, and keep the third-party dependencies it relies on. Whichever framework you started with, the controls and code you have invested in now go further.

Microsoft.UI.Reactor is Microsoft’s new declarative, component-based C# framework for WinUI. There is no XAML: you describe your UI as a function of state, with hooks such as UseState and fluent modifiers, in a style that will feel familiar if you come from React, SwiftUI, or Jetpack Compose.

With 7.0, Reactor apps run on Uno Platform too: on the desktop, in the browser, and on Android and iOS. Add Reactor to your UnoFeatures:

<UnoFeatures>Reactor</UnoFeatures>

Your existing XAML pages, styles, and view models stay as they are, and Reactor components render real WinUI controls in the same visual tree. Reactor support is in preview; the Reactor guide covers single-file apps and the unoapp-reactor template.

Because Uno Platform keeps a 1:1 API surface with WinUI, an automated sync brings the latest changes from the Microsoft.UI.Reactor repository over with little effort.

Apple TV is a new target platform in 7.0. Add net10.0-tvos to your app’s TargetFrameworks, and the same app runs on Apple TV with tvOS 15 and later: same XAML, same controls, same Fluent styles. It renders through Metal, as on iOS, and the Siri Remote drives focus navigation.

Together with Android TV, added in 6.7, your apps now reach both TV platforms.

Uno Platform 7.0 ships full support for .NET 11 on day zero, across every head: Desktop, WebAssembly, Android, iOS, Apple TV, and Windows App SDK. Create an app with dotnet new unoapp -tfm net11.0, and uno-check installs everything you need. .NET 10 remains fully supported as the long-term support release.

Shipping this close to Microsoft’s own timeline reflects a partnership that goes both ways: Uno Platform is now a co-maintainer of SkiaSharp alongside the .NET team at Microsoft, and contributes to other parts of .NET, including the Android bindings.

See it live at .NET Conf 2026. Join us at .NET Conf 2026, the free virtual event for the launch of .NET 11, on November 12 at 4:30 p.m. EST, and see Uno Platform 7.0 running on .NET 11.

RichTextBlock and RichEditBox are now available on every platform we support. The request dates back to one of Uno Platform’s earliest issues, #81 from 2018. Both controls bring WinUI-compatible rich text display and editing to every target, backed by extensive compatibility testing.

Your WinUI knowledge should carry over to Uno Platform unchanged. That has been our promise from the start. Uno Platform 7.0 ports more controls directly from WinUI’s open-source code, preserving their Windows layout, selection, and automation behavior. The WinUI team has been moving fast, advancing WinUI in the open with the community, and we are glad to bring that work to the cross-platform world. What’s new:

This release is large, and if you have read this far, thank you. A few more items, or read the full release notes.

Most apps on Uno.Sdk upgrade by bumping the SDK version, and the migrating to Uno Platform 7.0 guide walks through everything, with before and after code. The changes to plan for:

Ready to upgrade? Update the Uno.Sdk version in your global.json:

{
  "msbuild-sdks": {
    "Uno.Sdk": "7.0.x"
  }
}

Then follow the migration guide.

Finally, a huge thank you to everyone who contributed code, issues, and reviews to our largest release yet, from first-time contributors to community members whose long-standing contributions have now landed.

Uno Platform 7.0 gives you more ways to build. Uno Platform Studio brings it all together. We can’t wait to see what you build next.