Platform 7.0: faster rendering, broader.NET reach
Uno reports approximately twice the speed and five-times-smaller applications versus version 6.7, including an 83% package-size reduction in its published comparisons. These are vendor benchmarks, not independently established results for every application.
The architectural centerpiece is unified rendering across Windows, macOS, Linux, Android, iOS, tvOS, and WebAssembly. SkiaSharp 4 is the default, with Vulkan used by default on Android, Windows, and Linux. An experimental WebGPU backend is optional.
Other additions include:
- .NET 11 support, alongside.NET 10.
- Microsoft.UI.Reactor support in preview, allowing declarative C# components without requiring XAML.
- Third-party.NET MAUI controls across Uno targets, including browsers and Linux.
- Apple TV support, extending the platform’s television reach.
- RichTextBlock and RichEditBox, plus expanded WinUI controls and styles, including ItemsRepeater, LinedFlowLayout, and TitleBar.
The practical question is not whether every application becomes twice as fast. It is whether your application’s bottlenecks—layout, scrolling, text, startup, or download size—benefit enough to justify the migration. Benchmark representative screens rather than treating a headline multiplier as a service-level agreement.
Studio 3.3: control the agent, not just the prompt
Studio 3.3 adds a desktop application alongside its browser version. Builds cover Windows x64 and Arm64, Intel and Apple-silicon Macs, and Linux x64. It runs beside an IDE rather than replacing it.
At startup, Studio runs uno-check to identify missing development components, including SDKs, workloads, and templates, and offers fixes inside the application. That checks the build environment—not whether generated code is secure or correct.
Its checkpoints restore both project code and the AI conversation to an earlier instruction. Preview Variants display phone and desktop layouts in light and dark themes together, replacing Studio 3.2’s single-preview approach.
Studio Mobile is available for testing on iOS and Android. Users sign in, open a project, and receive over-the-air Hot Reload updates while working from Studio, an IDE, or the CLI. The new Theme Editor changes colors, typography, shapes, and spacing live, saving changes as XAML; access requires a Pro or Business plan.
The useful distinction: checkpoints make experimentation easier, but teams should still retain source control, review changes, and test independently. An undo button is a safety aid, not a software-quality department.
Existing applications face real migration work
Uno’s migration documentation makes clear that 7.0 is not merely a faster renderer selected through a switch:
- Native rendering backends are removed.
- Single-project
Uno.Sdkapplications are the supported project format. - .NET 9 targets must move to.NET 10 or later.
- Mac Catalyst targets are removed; macOS applications use the Desktop target.
- Libraries compiled against Uno 6.x are binary-incompatible and require compatible updates or rebuilding.
Default minimums also rise to iOS and tvOS 15.0, Android API 24, and Windows build 19041. Explicitly pinned lower values may remain, but Uno says those combinations are no longer tested.
One especially important upgrade trap concerns iOS and tvOS applications using LocalSettings or RoamingSettings: Uno requires a startup settings migration before those settings are first read. Otherwise, updating users lose access to their existing settings without a compiler warning. Android applications also require startup-head changes.
That is why a successful build should be the beginning of validation, not the finish line.
Windows deployment needs a separate check
Uno’s package documentation supplies an important detail beyond the launch announcement: packaged Windows applications now declare a Windows App Runtime framework dependency instead of bundling it by default. They require Windows App Runtime 2.4.0 or later.
According to Uno, Microsoft Store distribution installs that dependency. For sideloaded packages, developers must arrange runtime installation on the destination PC or explicitly retain bundling through:
<WindowsAppSDKSelfContained>true</WindowsAppSDKSelfContained>
Uno attributes an approximately 75 MB MSIX reduction to this packaging change. That is a specific deployment saving, distinct from its broader performance and size comparisons.
For enterprise teams, the recommendation is straightforward: test the installer on a clean destination machine, not only a developer workstation.
The takeaway
These releases deserve evaluation for different reasons. Platform 7.0 offers broader UI reuse and a more unified rendering foundation; Studio 3.3 concentrates on inspecting and reversing AI-assisted changes. Both directions are useful, but neither removes the need for engineering judgment.
Start an upgrade in a separate branch, inventory library compatibility and deployment dependencies, and compare representative workloads. Let the agent accelerate the work—but keep a human responsible for deciding when it is ready to ship.