.NET MAUI in .NET 11 Preview 3 - Release Notes

.NET 11 Preview 3 includes new .NET MAUI, .NET for Android, and .NET for iOS, Mac Catalyst, macOS, and tvOS improvements:

• Maps add clustering, styling, and richer interaction APIs
• XAML and styling improvements reduce startup work and speed up iteration
• LongPressGestureRecognizer is now built into .NET MAUI
• Platform integration adds iOS notification permission support
• .NET for Android adds Android 17 / API 37 preview support
• .NET for Android improves CLI device discovery and deploy flow
• .NET for Apple workloads improve packaging and binding quality
• .NET for Apple Xcode 26.3 support
• CoreCLR improvements on Apple platforms

.NET MAUI updates in .NET 11:

• What's new in .NET MAUI in .NET 11

Maps add clustering, styling, and richer interaction APIs

The Map control gets a substantial wave of functionality in Preview 3, including pin clustering, custom pin icons, custom JSON styling, MapLongClicked, click events for circles, polygons, and polylines, MapElement.IsVisible and ZIndex, programmatic info-window control, smoother region changes, and richer user-location events (dotnet/maui #29101, dotnet/maui #33831, dotnet/maui #33950, dotnet/maui #33982, dotnet/maui #33985, dotnet/maui #33792, dotnet/maui #33799, dotnet/maui #33991, dotnet/maui #33993). These APIs make it easier to build dense, interactive map experiences without falling back to platform-specific implementations.

<maps:Map IsClusteringEnabled="True"
          MapLongClicked="OnMapLongClicked">
    <maps:Pin Label="Seattle"
              Location="47.6062,-122.3321"
              ClusteringIdentifier="stores"
              ImageSource="store.png" />
</maps:Map>

XAML and styling improvements reduce startup work and speed up iteration

XAML Source Generation now registers ResourceDictionary entries as factories and inflates them on demand instead of materializing every style and brush at page startup (dotnet/maui #33826). Preview 3 also enables implicit XAML namespace declarations by default, adds explicit APIs to reapply mutated styles and visual states during Hot Reload or dynamic UI updates, and makes MAUI CSS trimmable when an app does not use stylesheets, reducing unnecessary app size (dotnet/maui #33834, dotnet/maui #34723, dotnet/maui #33160).

In particular, InvalidateStyle() and VisualStateManager.InvalidateVisualStates() give tooling and app code an explicit way to reapply in-place style and visual-state mutations without recreating the element tree.

<ContentPage.Resources>
    <Style x:Key="PrimaryButtonStyle" TargetType="Button">
        <Setter Property="Padding" Value="12,8" />
    </Style>
</ContentPage.Resources>

LongPressGestureRecognizer is now built into .NET MAUI

.NET MAUI now includes a built-in LongPressGestureRecognizer with duration, movement-threshold, state-change, and command support across platforms (dotnet/maui #33432). This gives press-and-hold interactions a first-party API instead of requiring toolkit behaviors or custom handlers.

<Image Source="avatar.png">
    <Image.GestureRecognizers>
        <LongPressGestureRecognizer
            MinimumPressDuration="750"
            Command="{Binding ShowContextMenuCommand}" />
    </Image.GestureRecognizers>
</Image>

Platform integration adds iOS notification permission support

Preview 3 adds an implementation of the PostNotifications permission on iOS, so apps can request notification authorization through the cross-platform Permissions API instead of dropping to platform-specific code (dotnet/maui #30132).

var status = await Permissions.RequestAsync<Permissions.PostNotifications>();

.NET for Android adds Android 17 / API 37 preview support

.NET for Android Preview 3 aligns with Android 17 / API 37 previews so apps can start validating against the upcoming platform now.

We're grateful to the Uno Platform team for their deep collaboration with the .NET MAUI team in preparation for .NET 11 Preview 3. Their contributions helped ensure .NET for Android is aligned with Google's latest platform updates, enabling developers to take advantage of Android 17 previews and API 37 right away. This kind of partnership strengthens the .NET ecosystem and reflects our shared commitment to delivering high-quality, cross-platform developer experiences.

To opt into API-37, update your .csproj:

<PropertyGroup>
  <TargetFramework>net11.0-android37</TargetFramework>
  <EnablePreviewFeatures>true</EnablePreviewFeatures>
</PropertyGroup>

To install API-37 in Visual Studio, use Tools > Android > Android SDK Manager > Repository > Full List:

See the API-37 HPKE Encryption Sample for a full example calling new APIs available in Android 17. For the complete list of changes, see the .NET for Android Preview 3 release notes.

.NET for Android improves CLI device discovery and deploy flow

dotnet run can now list available emulators and auto-boot a selected AVD before deployment (dotnet/android #10826). These changes make CLI-first Android development less dependent on IDE-only device management.

.NET for Apple workloads improve packaging and binding quality

Preview 3 improves Apple workload packaging by filtering static frameworks out of post-processing so only frameworks that actually ship in the app bundle are stripped and symbol-processed (dotnet/macios #24845). The release branch also includes binding-quality work such as improved nullability annotations for NSArray APIs (dotnet/macios #24907).

.NET for Apple Xcode 26.3 support

Xcode 26.3 is now supported for targeting Apple platforms. No new APIs were introduced.

CoreCLR improvements on Apple platforms

This preview includes several CoreCLR improvements across all Apple platforms (iOS, macOS, Mac Catalyst, and tvOS):

• Smaller Release builds. Native symbol stripping now covers CoreCLR and ReadyToRun (R2R) frameworks, reducing a MAUI template app's bundle size from 77.8 MB to 41.6 MB (dotnet/macios #24678).
• Faster incremental builds. R2R composite images are cached when only user assemblies change, cutting incremental build time from ~39s to ~26s (dotnet/macios #24735).
• Smarter code generation. The R2R compiler now targets the minimum instruction set for your deployment target (for example, ARMv8.2-A for iOS 16+), producing better native code without sacrificing device compatibility (dotnet/macios #24621).
• R2R on macOS. ReadyToRun compilation is now functional on macOS, completing R2R support across all Apple platforms (dotnet/macios #25080).

Contributors

Thank you contributors! ❤️

@adamzip, @Ahamed-Ali, @csigs, @dalexsoto, @davidnguyen-tech, @grendello, @Happypig375, @IeuanWalker, @jfversluis, @jonathanpeppers, @jonpryor, @kotlarmilos, @kubaflo, @mattleibow, @NirmalKumarYuvaraj, @noiseonwires, @PureWeen, @rmarinho, @rolfbjarne, @sbomer, @sheiksyedm, @simonrozsival, and @StephaneDelcroix.