Choose your app platform

When you want to create a new desktop application for Windows PCs, the first decision you make is which application platform to use. Windows provides four main application platforms, each with different strengths:

All of these application platforms let you create desktop apps like Word, Excel, and Photoshop that run in the classic Windows desktop and take full advantage of that environment's specific features. However, some of these platforms share some traits and are better suited for certain types of applications:

  • UWP, WPF, and Windows Forms. These platforms provide managed runtime environments (the Windows Runtime for UWP, and .NET for Windows Forms and WPF) with many benefits, especially in the areas of developer productivity, sophisticated and customizable UI, and application security. Because these frameworks support visual designers and UI markup for rapidly creating UI, they are particularly well-suited for line-of-business applications.

  • Win32 API. The Win32 API (also called the Windows API) is the original platform for native C/C++ Windows applications that require direct access to Windows and hardware. It provides a first-class development experience without depending on a managed runtime environment like .NET and WinRT. This makes the Win32 API the platform of choice for applications that need the highest level of performance and direct access to system hardware.

This article describes these platforms in more detail and helps you determine the best one for your application.


No matter which app platform you choose, you can use many features of the Universal Windows Platform (UWP) to deliver a modern experience in your app on Windows 10. For example, even if your desktop app is built using WPF, Windows Forms, or the Win32 API, you can still use many features first introduced with UWP, such as MSIX package deployment and UWP XAML controls. For more information, see Modernize your desktop apps.


UWP is the leading-edge platform for Windows 10 applications and games. It's a highly customizable platform that uses XAML markup to separate UI (presentation) from code (business logic). UWP is suitable for desktop applications that require a sophisticated UI, styles customization, and graphics-intensive scenarios. UWP also has built-in support for the Fluent Design System for the default UX experience and provides access to the Windows Runtime (WinRT) APIs. By adopting Fluent, UWP automatically supports common input methods such as ink, touch, gamepad, keyboard, and mouse.

Not only can you use UWP to create desktop applications for Windows PCs, but UWP is also the only supported platform for Xbox, HoloLens, and Surface Hub applications. UWP is our newest, leading-edge application platform.

For more information about UWP, see the following articles:


WPF is the established platform for managed Windows applications with access to .NET Core or the full .NET Framework, and it also uses XAML markup to separate UI from code. This platform is designed for desktop applications that require a sophisticated UI, styles customization, and graphics-intensive scenarios. WPF development skills are similar to UWP development skills, so migration from WPF to UWP apps is easier than migration from Windows Forms.

For more information about WPF, see the following articles:

Windows Forms

Windows Forms is the original platform for managed Windows applications with a lightweight UI model and access to .NET Core or the full .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 extend your application to UWP entails a complete re-write of your UI.

For more information about Windows Forms, see the following articles:


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 unmanaged 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 (note that UWP also offers DirectX interop).

For more information, see the following articles:

Platform comparison: UWP, WPF, and Windows Forms

The following table compares various characteristics of Windows Forms, WPF, and UWP in detail.

Feature or scenario UWP WPF Windows Forms
Supported versions Windows 10 Windows 7 and later Windows 7 and later
Languages C#, C++/WinRT, C++/CX, VB, JavaScript C#, C++/CLI (Managed Extensions for C++), F#, VB C#, C++/CLI (Managed Extensions for C++), F#, VB
UI runtime Native (C++/WinRT and C++/CX) and managed (.NET Native) Managed (.NET Framework and .NET Core 3) Managed (.NET Framework and .NET Core 3)
Open source Yes (Windows UI Library only) Yes (.NET Core only) Yes (.NET Core only)
Supports XAML Yes Yes No
  • XAML markup for UI
  • Rich and customizable UX
  • Your existing code bases are .NET Standard compliant
  • High DPI support
  • Support for multiple input types across Windows devices (including touch, pen, gamepad, mouse, and keyboard)
  • Support for Xbox, HoloLens, IoT or Surface Hub
  • Optional dense (compact) UI
  • Support for native C++
  • Optimized battery life
  • Modern accessibility support (such as screen readers)
  • Rich text data capabilities (such as built-in spell check)
  • Inking support
  • Secure execution via application containers (for example, untrusted content is sandboxed)
  • XAML markup for UI
  • Rich and customizable UX
  • Large collection of controls from Microsoft and partners
  • Dense UI
  • Support for Windows 7
  • Platform support for input validation
  • Rapid application development
  • WYSIWYG editor for building UI
  • Large collection of controls from Microsoft and partners
  • Dense UI
  • Support for Windows 7
  • Keyboard and mouse input
Scenarios that have limited support
  • Multiple window support1
  • Platform support for input validation1
  • Windows 7 is not supported
  • Some UWP APIs require specific minimum versions of Windows 10
  • Full platform support and shell integration (for example, UWP currently doesn't support System Tray integration or full access to all devices)
  • Direct access to all files on disk
  • Existing code-base class libraries that use non-.NET Standard or non-Windows App Certification Kit compliant APIs
  • Local network loopback support (that is, if your app needs to communicate with localhost without creating a loopback exemption on the target device)
  • Intensive file I/O
  • High DPI support2
  • Touch input2
  • High DPI support2
  • Touch input2
  • Customizable UI
  • Rich graphics and user experiences (such as touch and animations)
  • Rich abstraction of views and data models

1 We have publicly announced features that will address this scenario in a future release of Windows 10.

2 Although the platform lacks first-class API support for this scenario, developers can support this scenario with workarounds.

Other app platforms

Progressive Web Apps (PWAs)

PWAs let developers package their website code so it can be installed and run like an application on Windows 10 PCs. For more information, see Progressive Web Apps.


Use Xamarin to build cross-platform applications for Windows 10 that can also run on iOS and Android. For more information, see Xamarin.