Windows App SDK
The Windows App SDK is a set of new developer components and tools that represent the next evolution in the Windows app development platform. The Windows App SDK provides a unified set of APIs and tools that can be used in a consistent way by any desktop app on Windows 11 and downlevel to Windows 10, version 1809.
The Windows App SDK doesn't replace the Windows SDK or existing desktop Windows app types such as .NET (including Windows Forms and WPF) and desktop Win32 with C++. Instead, the Windows App SDK complements those existing tools and app types with a common set of APIs that developers can rely on across these platforms. For more details, see Benefits of the Windows App SDK.
Important
If you're working on a UWP app, then refer to Migrate from UWP to the Windows App SDK.
The Windows App SDK provides extensions for Visual Studio 2022 and Visual Studio 2019. Those extensions include project templates configured to use the Windows App SDK components in new projects. The Windows App SDK libraries are also available via a NuGet package that you can install in existing projects.
To learn about configuring Visual Studio for creating new Windows App SDK projects, including the required workloads and components, see Getting Started with WinUI.
If you've already installed the required developer tools, then you're ready to Create your first WinUI 3 project. You can also use the Windows App SDK in an existing project.
For guidance on specific Windows App SDK versions, see Release channels and Downloads.
The following table highlights the development features that are provided by the current releases of the Windows App SDK. For more details about the release channels of the Windows App SDK that include each of these features, see Features available by release channel.
Feature | Description |
---|---|
WinUI 3 | The premiere native user interface (UI) framework for Windows desktop apps, including managed apps that use C# and .NET and native apps that use C++ with the Win32 API. WinUI 3 provides consistent, intuitive, and accessible experiences using the latest user interface (UI) patterns. |
Render text with DWriteCore | Render text using a device-independent text layout system, high quality sub-pixel Microsoft ClearType text rendering, hardware-accelerated text, multi-format text, wide language support, and much more. |
Manage resources with MRT Core | Manage app resources such as strings and images in multiple languages, scales, and contrast variants independently of your app's logic. |
App lifecycle: App instancing | Control whether multiple instances of your app's process can run at the same time. |
App lifecycle: Rich activation | Process information about different kinds activations for your app. |
App lifecycle: Power management | Gain visibility into how your app affects the device's power state, and enable the app to make intelligent decisions about resource usage. |
Manage app windows | Create and manage the windows associated with your app. |
Push notifications | Send raw notifications and app notifications to your app from the cloud using Azure App Registration identities. |
App notifications | Send app notifications to your app locally. |
Deployment | Deploy Windows App SDK runtime with your unpackaged and packaged app |
The following table provides an overview of the different release channels.
Release channel | Description |
---|---|
Stable | This channel is supported for use by apps in production environments. It only includes stable APIs. By default, the Windows App SDK docs focus on the Stable channel. |
Preview | This channel provides a preview of the next stable release. There may be breaking API changes between a given preview channel release and the next stable release. For documentation on using the Preview release, see Install tools for preview and experimental channels of the Windows App SDK. |
Experimental | This channel includes experimental features that are in early stages of development. Experimental features may be removed from the next release, or may never be released. For documentation on using the Experimental release, see Install tools for preview and experimental channels of the Windows App SDK. |
For more details about the release channels of the Windows App SDK, see Windows App SDK release channels.
The Windows App SDK provides a broad set of Windows APIs with implementations that are decoupled from the OS and released to developers via NuGet packages. The Windows App SDK is not meant to replace the Windows SDK. The Windows SDK will continue to work as is, and there are many core components of Windows that will continue to evolve via APIs that are delivered via OS and Windows SDK releases. Developers are encouraged to adopt the Windows App SDK at their own pace.
Developers who want to create desktop Windows apps must choose between several app platforms and frameworks. Although each platform provides many features and APIs that can be used by apps that are built using other platforms, some features and APIs can only be used by specific platforms. The Windows App SDK unifies access to Windows APIs for desktop Windows 11 and Windows 10 apps. No matter which app model you choose, you will have access to the same set of Windows APIs that are available in the Windows App SDK.
Over time, we plan to make further investments in the Windows App SDK that remove more distinctions between the different app models. For example, your app might use the WinUI Desktop model, it might use the XAML Islands model, it might use WPF, or it could be a non-XAML app that uses Composition Islands or other aspects of the Windows App SDK. In any of these cases, we aim to make access to the Windows APIs in the Windows App SDK the same easy experience. The Windows App SDK will include both WinRT APIs and native C APIs.
As the Windows APIs continue to evolve with new OS versions, developers must use techniques such as version adaptive code to account for all the differences in versions to reach their application audience. This can add complexity to the code and the development experience.
Windows App SDK APIs will work on Windows 11 and downlevel to Windows 10, version 1809. This means that as long as your customers are on Windows 10, version 1809, or any later version of Windows, you can use new Windows App SDK APIs and features as soon as they are released, and without having to write version adaptive code.
New Windows APIs and features are usually shipped within major Windows OS updates that release about once a year (often less frequently). Windows App SDK ships new releases about once every six months. This release cadence ensures that you continuously have access to the latest innovations in the Windows development platform.
We are building the Windows App SDK as an open source project. We have a lot more information on our Github page about how we're building the Windows App SDK, and how you can be a part of the development process. Check out our contributor guide to ask questions, start discussions, or make feature proposals. We want to make sure that the Windows App SDK brings the biggest benefits to developers like you.
Windows developer feedback
Windows developer is an open source project. Select a link to provide feedback: