Overview of framework options

Win32 desktop apps (also sometimes called classic desktop apps) are the original app type for native Windows applications that require direct access to Windows and hardware. This makes Win32 the app type of choice for applications that need the highest level of performance and direct access to system hardware.

Using the Win32 API with C++ makes it possible to achieve the highest levels of performance and efficiency by taking more control of the target platform with un-managed code than is possible on a managed runtime environment like WinRT and .NET. However, exercising such a level of control over your application's execution requires greater care and attention to get right, and trades development productivity for runtime performance.

Here are a few highlights of what the Win32 API and C++ offers to enable you to build high-performance applications.

• Hardware-level optimizations, including tight control over resource allocation, object lifetimes, data layout, alignment, byte packing, and more.
• Access to performance-oriented instruction sets like SSE and AVX through intrinsic functions.
• Efficient, type-safe generic programming by using templates.
• Efficient and safe containers and algorithms.
• DirectX, in particular Direct3D and DirectCompute.
• Use C++/WinRT to create modern desktop Win32 apps with first-class access to Windows Runtime (WinRT) APIs.

Additionally, you can now integrate a sandbox environment into your Win32 applications, providing an additional layer of security. This enhancement requires little to no change to your code, thanks to the new Win32 App Isolation security feature.

You also have access to modern Windows platform features and APIs provided by the Windows App SDK. For more information, see Use the Windows App SDK in an existing project and Modernize your desktop apps.

Windows Forms is the original platform for managed Windows applications with a lightweight UI model and access to .NET or the .NET Framework. It excels at enabling developers to quickly get started building applications, even for developers new to the platform. This is a forms-based, rapid application development platform with a large built-in collection of visual and non-visual drag-and-drop controls. Windows Forms does not use XAML, so deciding later to rewrite your application to WinUI entails a complete re-write of your UI.

Additionally, you can now integrate a sandbox environment into your packaged Windows Forms applications, providing an additional layer of security. This enhancement requires little to no change to your code, thanks to the new Win32 App Isolation security feature.

If you have a Windows Forms .NET app, you also have access to modern Windows platform features and APIs provided by the Windows App SDK. For more information, see Use the Windows App SDK in a Windows Forms (WinForms) app and Modernize your desktop apps.

The Universal Windows Platform (UWP) provides a common type system, APIs, and application model for all devices in the Universal Windows Platform. Not only can you use UWP to create desktop applications for Windows PCs, but UWP is also the only supported platform to write a single native universal app that runs across Xbox, HoloLens, and Surface Hub. UWP apps can be native or managed.

You will not have access to the APIs provided by the Windows App SDK or .NET 6 and later. To use the Windows App SDK, you will have to migrate your UWP app to WinUI and the Windows App SDK. For more information, see Migrate to the Windows App SDK.

.NET Multi-platform App UI (MAUI) is an open-source, cross-platform framework for building Android, iOS, macOS, and Windows applications that leverage the native UI and services of each platform from a single .NET code base. Because .NET MAUI favors platform native experiences, it uses WinUI and the Windows App SDK so apps get the latest user experience on Windows. This gives your apps access to everything you get with WinUI plus the ability to reach to other platforms.

.NET MAUI for Windows is a great choice if:

• You want to share as much .NET code as possible across mobile and desktop applications.
• You want to ship your application beyond Windows to other desktop and mobile targets with native platform experiences.
• You want to use C# and/or XAML for building cross-platform apps.
• You're using Blazor for web development and wish to include all or part of that in a mobile or desktop application.

For more information about .NET MAUI, see the following links:

• .NET MAUI documentation
• .NET MAUI on GitHub
• .NET MAUI Product Roadmap
• Build Windows apps with .NET MAUI
• Resources for learning .NET MAUI
• Video Series - .NET MAUI for Beginners
• Build 2022: Build native apps for any device with .NET and Visual Studio

Progressive Web Apps (PWAs) provide access to open web technologies to provide cross-platform interoperability. PWAs provide your users with an app-like experience that's customized for their devices. PWAs are websites that are progressively enhanced to function like installed, native apps on supporting platforms (including Windows), while functioning like regular websites on other browsers.

When installed on Windows, PWAs are just like other apps. For example:

• A PWA can be added to the Start menu.
• A PWA can be pinned to the Taskbar.
• PWAs can handle files.
• PWAs can run when the user signs in.
• PWAs can be submitted to the Microsoft Store where millions of Windows users can discover and easily install them alongside other Windows apps.

For more information about building PWAs, see the following links:

• Overview of PWAs
• Publish a PWA to the Microsoft Store
• Re-engage users with badges, notifications, and push messages
• Build PWA-driven widgets
• Progressive Web App demos
• PWABuilder - Helping developers build and publish PWAs

React Native is a development platform which allows building cross-platform apps. React Native for Windows brings React Native support to the Windows 10 and Windows 11 SDKs, letting you use JavaScript to build native Windows apps for all devices supported by Windows 10 and Windows 11. This includes PCs, tablets, 2-in-1s, Xbox, Mixed Reality devices, etc.

With React Native for Windows, you write most or all of your app code in JavaScript - or TypeScript - and the framework produces a native UWP XAML application. If your app needs to call a platform API, you can usually do so through one of the many community modules, or if a module does not yet exist, you can easily write a native module to expose it.

Here are some reasons to choose React Native for Windows:

• You want to share code across platforms as much as possible, or you have web properties that you want to share code with.
• Improved developer productivity and inner loop, thanks to fast refresh.
• Your app's fundamentals (performance, accessibility, internationalization) are as good as a native UWP app.
• You have experience with and a preference for JavaScript or TypeScript
• You would like to leverage JavaScript-only libraries on npmjs.com, and many native libraries too.
• Your app will use the native controls, visual appearance, animations and colors, and therefore will feel integrated into the design language used in Windows. In addition, React Native for Windows apps do not have to compromise on the set of APIs they can call, as the framework allows you to call platform APIs as well as write your own view managers and native modules.
• Large and growing community momentum, with lots of community modules.

For more information about React Native for Windows, see the following links:

• React Native for Windows repo on GitHub
• Native modules in React Native for Windows
• API reference
• Community modules directory
• More resources