Update selecting a tech page (#3790)

GrantMeStrength · web-flow · commit 12cad27551c8 · 2023-09-26T14:41:14.000-07:00
* Update selecting a tech page

* Update selecting a tech page

* Update TOC in the get started section

* Update TOC in the get started section

* Corrected yml and title
diff --git a/hub/apps/get-started/index.md b/hub/apps/get-started/index.md
@@ -1,35 +1,37 @@
 ---
-description: Learn how to get started building new apps for Windows desktop and modernizing existing apps.
-title: Writing apps for Windows
+description: An overview of Windows development options - Writing apps for Windows and how to select a development technology
+title: An overview of app development option
 ms.topic: article
-ms.date: 6/23/2023
-keywords: windows win32, desktop development
+ms.date: 9/26/2023
+keywords: windows, desktop development
 ms.localizationpriority: medium
 ---
 
-# Writing apps for Windows: Selecting a development technology
+# An overview of Windows development options
 
 This article contains the information you need to get started building apps for the Windows desktop environment.
 
 ![Developer at desk](./images/developer-at-desk.jpg)
 
 Windows offers a wide range of options for building apps, including [C++](/windows/uwp/cpp-and-winrt-apis/), [.NET](/dotnet/), and other emerging technologies such as [open source tools on WSL](/windows/wsl/) and [Rust](../../dev-environment/rust/index.yml). With so many choices, it can be difficult to know where to begin.
 
-## IDE 
+## Visual Studio
 
-[Visual Studio](/visualstudio) is the go-to development environment for most Windows developers, providing various starting points for different types of apps, each with their own strengths and project types ([here's a quick C# tutorial](/visualstudio/get-started/csharp/tutorial-console?view=vs-2022)). Every app type includes an app model that defines the app's lifecycle, a default UI framework, and access to a comprehensive set of APIs for using Windows features.
+[Visual Studio](/visualstudio) is the preferred integrated development environment (IDE) for most Windows developers. It offers a variety of templates for different app types, each with its own strengths and project types. For instance, you can use the [C# tutorial](/visualstudio/get-started/csharp/tutorial-console?view=vs-2022) for console apps to get started. Every app type includes an app model that defines the app’s lifecycle, a default UI framework, and access to a comprehensive set of APIs for using Windows features.
 
-[Visual Studio Code](https://code.visualstudio.com) is another popular tool, with extensions and support for a large number of development languages and tools. For languages other than C# and C++, it's a great place to start.
+[Visual Studio Code](https://code.visualstudio.com) is another popular tool that provides extensions and support for a wide range of development languages and tools. It’s an excellent starting point for languages other than C# and C++ (although it supports those too).
 
 ## Languages and frameworks
 
-Many apps for Windows are written using [WPF](/dotnet/desktop/wpf/get-started/create-app-visual-studio?view=netdesktop-7.0) or [Windows Forms](/dotnet/desktop/winforms/getting-started-with-windows-forms?view=netframeworkdesktop-4.8), and they remain viable tools today.
+Many apps for Windows are written using [UWP](/windows/uwp), [WPF](/dotnet/desktop/wpf/get-started/create-app-visual-studio?view=netdesktop-7.0) or [Windows Forms](/dotnet/desktop/winforms/getting-started-with-windows-forms?view=netframeworkdesktop-4.8), and they all remain viable tools today.
 
-Looking to the future, if your app will only run on Windows we recommend investigating the [Windows App SDK](../windows-app-sdk/index.md) and [WinUI 3](../winui/winui3/index.md). If you need your app to be cross-platform, consider [.NET MAUI](/dotnet/maui/what-is-maui), a [Progressive Web App (PWA)](/microsoft-edge/progressive-web-apps-chromium/), or [React Native for Windows](../../dev-environment/javascript/react-native-for-windows.md). There are many other options available ([here's a list of popular options](../../dev-environment/index.md)), but the above are some good starting points.
+Looking to the future, if your app will only run on Windows you might want to investigate the [Windows App SDK](../windows-app-sdk/index.md) and [WinUI 3](../winui/winui3/index.md). If you need your app to be cross-platform, consider [.NET MAUI](/dotnet/maui/what-is-maui), a [Progressive Web App (PWA)](/microsoft-edge/progressive-web-apps-chromium/), or [React Native for Windows](../../dev-environment/javascript/react-native-for-windows.md). There are many other choices available ([here's a list of popular options](../../dev-environment/index.md)), but the above are some good starting points.
 
-> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RWQwHD]
+## Windows platforms
 
-## Create a WinUI 3 app
+For more information about the app types you can choose from, see the following tabs.
+
+### [WinAppSDK and WinUI](#tab/winappsdk-winui)
 
 The Windows UI Library (WinUI) 3 is the latest 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. It is still under very active development, so while it might not be able to meet all your needs today it's maturing with [every release](/windows/apps/windows-app-sdk/stable-channel).
 
@@ -40,6 +42,57 @@ By incorporating the [Fluent Design System](https://www.microsoft.com/design/flu
 
 If you have already installed the required developer tools, you are ready to [Create your first WinUI 3 project](../winui/winui3/create-your-first-winui3-app.md).
 
+### [Win32](#tab/cpp-win32)
+
+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 this 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 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).
+- Use [C++/WinRT](/windows/uwp/cpp-and-winrt-apis/) to create modern desktop Win32 apps with first-class access to Windows Runtime (WinRT) APIs.
+
+> [!div class="button"]
+> [Get started with Win32](/windows/win32/desktop-programming/)
+
+You also have access to modern Windows platform features and APIs provided by the **Windows App SDK**. For more information, see [Modernize your desktop apps](../desktop/modernize/index.md).
+
+### [WPF](#tab/wpf)
+
+WPF is a well-established platform for managed Windows applications with access to .NET or the .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 WinUI 3 development skills, so migrating from WPF to WinUI 3 is easier than migrating from Windows Forms.
+
+> [!div class="button"]
+> [Get started with WPF](/dotnet/framework/wpf/getting-started/)
+
+You also have access to modern Windows platform features and APIs provided by the **Windows App SDK**. For more information, see [Modernize your desktop apps](../desktop/modernize/index.md).
+
+### [Windows Forms](#tab/windows-forms)
+
+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 3 entails a complete re-write of your UI.
+
+> [!div class="button"]
+> [Get started with Windows Forms](/dotnet/framework/winforms/getting-started-with-windows-forms)
+
+You also have access to modern Windows platform features and APIs provided by the **Windows App SDK**. For more information, see [Modernize your desktop apps](../desktop/modernize/index.md).
+
+### [UWP](#tab/uwp)
+
+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.
+
+UWP is a highly customizable platform that uses XAML markup to separate UI (presentation) from code (business logic). UWP is suitable for desktop apps that require a sophisticated UI, styles customization, and graphics-intensive scenarios. UWP also has built-in support for the [Fluent Design System](/windows/uwp/design/fluent-design-system/) for the default UX experience and provides access to the [Windows Runtime (WinRT) APIs](/windows/uwp/get-started/universal-application-platform-guide#how-the-universal-windows-platform-relates-to-windows-runtime-apis).
+
+> [!div class="button"]
+> [Get started with UWP](/windows/uwp/get-started/)
+
+You will not have access to the APIs provided by the **Windows App SDK**. To use the Windows App SDK, you will have to migrate your UWP app to WinUI 3. For more information, see [Migrate to the Windows App SDK](../windows-app-sdk/migrate-to-windows-app-sdk/overall-migration-strategy.md).
+
+---
+
 ## Cross-platform options
 
 WinUI also serves as the basis for cross-platform technologies that provide great native Windows experiences using a variety of coding languages. .NET MAUI and React Native for Windows harness the power of WinUI on Windows, while also enabling execution on other operating systems. Another cross-platform option, Progressive Web Apps (PWAs), are websites that function like installed, native apps on Windows and other supported platforms, while functioning like regular websites on browsers.
@@ -120,57 +173,4 @@ For more information about React Native for Windows, see the following links:
 - [Community modules directory](https://reactnative.directory)
 - [More resources](https://microsoft.github.io/react-native-windows/resources)
 
----
-
-## Other app types
-
-For more information about the app types you can choose from, see the following tabs.
-
-### [Win32](#tab/cpp-win32)
-
-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 this 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 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).
-- Use [C++/WinRT](/windows/uwp/cpp-and-winrt-apis/) to create modern desktop Win32 apps with first-class access to Windows Runtime (WinRT) APIs.
-
-> [!div class="button"]
-> [Get started with Win32](/windows/win32/desktop-programming/)
-
-You also have access to modern Windows platform features and APIs provided by the **Windows App SDK**. For more information, see [Modernize your desktop apps](../desktop/modernize/index.md).
-
-### [WPF](#tab/wpf)
-
-WPF is a well-established platform for managed Windows applications with access to .NET or the .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 WinUI 3 development skills, so migrating from WPF to WinUI 3 is easier than migrating from Windows Forms.
-
-> [!div class="button"]
-> [Get started with WPF](/dotnet/framework/wpf/getting-started/)
-
-You also have access to modern Windows platform features and APIs provided by the **Windows App SDK**. For more information, see [Modernize your desktop apps](../desktop/modernize/index.md).
-
-### [Windows Forms](#tab/windows-forms)
-
-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 3 entails a complete re-write of your UI.
-
-> [!div class="button"]
-> [Get started with Windows Forms](/dotnet/framework/winforms/getting-started-with-windows-forms)
-
-You also have access to modern Windows platform features and APIs provided by the **Windows App SDK**. For more information, see [Modernize your desktop apps](../desktop/modernize/index.md).
-
-### [UWP](#tab/uwp)
-
-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.
-
-UWP is a highly customizable platform that uses XAML markup to separate UI (presentation) from code (business logic). UWP is suitable for desktop apps that require a sophisticated UI, styles customization, and graphics-intensive scenarios. UWP also has built-in support for the [Fluent Design System](/windows/uwp/design/fluent-design-system/) for the default UX experience and provides access to the [Windows Runtime (WinRT) APIs](/windows/uwp/get-started/universal-application-platform-guide#how-the-universal-windows-platform-relates-to-windows-runtime-apis).
-
-> [!div class="button"]
-> [Get started with UWP](/windows/uwp/get-started/)
-
-You will not have access to the APIs provided by the **Windows App SDK**. To use the Windows App SDK, you will have to migrate your UWP app to WinUI 3. For more information, see [Migrate to the Windows App SDK](../windows-app-sdk/migrate-to-windows-app-sdk/overall-migration-strategy.md).
+---
diff --git a/hub/apps/index.yml b/hub/apps/index.yml
@@ -47,7 +47,7 @@ productDirectory:
     imageSrc: /media/common/i_get-started.svg
     links:
       - url: ./get-started/index.md
-        text: Overview of app development options
+        text: Overview of Windows development options
       - url: ./windows-app-sdk/set-up-your-development-environment.md
         text: Install tools for the Windows App SDK
       - url: ./winui/winui3/create-your-first-winui3-app.md
@@ -97,9 +97,9 @@ tools:
     - title: Windows for IoT
       imageSrc: /media/hubs/windows/win_developer-4.svg
       url: /windows/iot-core/
-    - title: Xbox One
+    - title: Games
       imageSrc: /media/hubs/windows/win_developer-3.svg
-      url: https://www.xbox.com/developers
+      url: https://developer.microsoft.com/games/
 
 additionalContent:
   sections:
diff --git a/hub/apps/toc.yml b/hub/apps/toc.yml
@@ -30,16 +30,6 @@ items:
     items:
         - name: Overview of app development options
           href: get-started/index.md
-        - name: About migrating from UWP to Windows App SDK
-          href: get-started/migrate-from-uwp-to-winappsdk.md
-        - name: Install tools for the Windows App SDK
-          href: windows-app-sdk/set-up-your-development-environment.md
-        - name: "Create your first WinUI 3 project"
-          href: winui/winui3/create-your-first-winui3-app.md
-        - name: "Tutorial: Create a simple photo viewer with WinUI 3"
-          href: get-started/simple-photo-viewer-winui3.md
-        - name: "Tutorial: Create a simple multi-platform photo viewer"
-          href: get-started/uno-simple-photo-viewer.md
         - name: Sample apps for Windows
           href: get-started/samples.md
         - name: Windows developer best practices 
@@ -58,6 +48,8 @@ items:
           href: get-started/developer-mode-features-and-debugging.md
         - name: Create a developer account
           href: get-started/sign-up.md
+        - name: Install tools for the Windows App SDK
+          href: windows-app-sdk/set-up-your-development-environment.md
         - name: Visual Studio project templates
           items:
             - name: All templates for Windows apps
@@ -70,6 +62,14 @@ items:
         href: how-tos/hello-world-winui3.md
       - name: Target multiple platforms with WinUI 3
         href: how-tos/uno-multiplatform.md
+      - name: About migrating from UWP to Windows App SDK
+        href: get-started/migrate-from-uwp-to-winappsdk.md
+      - name: "Create your first WinUI 3 project"
+        href: winui/winui3/create-your-first-winui3-app.md
+      - name: "Tutorial: Create a simple photo viewer with WinUI 3"
+        href: get-started/simple-photo-viewer-winui3.md
+      - name: "Tutorial: Create a simple multi-platform photo viewer"
+        href: get-started/uno-simple-photo-viewer.md
   - name: Design
     href: design/toc.yml
   - name: Develop
@@ -509,12 +509,12 @@ items:
             href: develop/smart-app-control/code-signing-for-smart-app-control.md
           - name: Test your app's signature with Smart App Control
             href: develop/smart-app-control/test-your-app-with-smart-app-control.md
-  - name: Windows app restore
-    href: develop/windows-app-restore.md
   - name: Deploy
     items:
       - name: Deployment overview
         href: package-and-deploy/index.md
+      - name: Windows app restore
+        href: develop/windows-app-restore.md
       - name: Windows App SDK deployment guide
         items:
           - name: Windows App SDK deployment overview
diff --git a/uwp/get-started/index.md b/uwp/get-started/index.md
@@ -7,7 +7,7 @@ keywords: get started, windows 10, uwp, xaml, c#
 ms.localizationpriority: medium
 ---
 
-# Get started with UWP (Universal Windows Platform)
+# Universal Windows Platform (UWP) - Get Started
 
 Build apps that work across different Windows devices.
 
