Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ: Update "What's a UWP" section #328

Closed
wants to merge 4 commits into from

Conversation

Felix-Dev
Copy link

@Felix-Dev Felix-Dev commented Dec 5, 2020

Reading through the What's a UWP section in the FAQ, I always felt a fundamental aspect of being a UWP app was missing - namely the fact that UWP is currently the only supported platform for Xbox, HoloLens, and Surface Hub applications. It's possible this might change in the future but it's far from guaranteed and in case it does happen it will likely be years from now. As such, I think it is worthwile to point out this characteristic of a UWP app compared to a Win32 app for us Windows developers.

Additional note

Indirectly related to this PR, perhaps the FAQ could also be extended with the question "Will Project Reunion enable my Win32 app to run on all Windows 10 devices including Xbox, HoloLens and Surface Hub?"? We have seen this question come up a few times already in one form or another (see here and here for example) so I think it makes sense to list this question directly in the FAQ, even though it already appears to have been answered at least indirectly.

Add note about UWP being the only supported platform for Xbox, HoloLens, and Surface Hub applications.
@ghost ghost added the needs-triage label Dec 5, 2020
docs/faq.md Outdated
@@ -115,7 +115,8 @@ We're looking to support:
Referenced throughout this repo, the term "UWP" references a
[Universal Windows Platform App](https://docs.microsoft.com/en-us/windows/uwp/get-started/) -
an app running inside an app container, at a lower privilege level, with
package identity, delivered via an MSIX. This app's lifecycle from activation
package identity, delivered via an MSIX. It is the only app type supported on Windows devices
such as Xbox, HoloLens and Surface Hub (Windows 10 Team). This app's lifecycle from activation
Copy link
Author

@Felix-Dev Felix-Dev Dec 5, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Three remarks:

  • I chose not to list Windows 10 IoT Core here since to my understanding that product is currently in the process of being superseded by Windows 10 IoT Enterprise - which supports Win32 apps. As such, IoT Core will likely become less and less relevant for the Windows development story, but I can still add it if it makes sense.
    Edit: Now added.
  • I am also not yet listing Windows 10X here since I don't yet know about the exact development details Windows 10X will arrive with.
  • Windows 10 Team now supports apps like the new Edge browser based on Chromium or Microsoft Teams (see here) which to my understanding aren't UWP apps even on the Surface Hub so that wording might be a bit imprecise ("only app type supported"). That said, at least commonly UWP apps are the only ones being supported on Windows 10 Team so the wording might be fine after all.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please move the "It is the only type..." to a separate paragraph. This paragraph should describe precisely what a UWP is and put the where it's useful separately.

@hansmbakker
Copy link

For raspberry pi-like devices there seems no path forward to Windows IoT (Enterprise) given by Microsoft so please do include Windows IoT Core

@Felix-Dev
Copy link
Author

@hansmbakker Added Windows 10 IoT Core to the list.

@asklar
Copy link
Member

asklar commented Dec 6, 2020

Fyi I wrote something similar/complementary for react native for Windows apps (which are UWPs)
https://microsoft.github.io/react-native-windows/docs/next/native-code

through termination is controlled by the platform for best power and resource
usage. Its access to the user's resources are gated by a Request model so the
package identity, delivered via an MSIX. It is the only app type supported on Windows devices
such as Xbox, HoloLens, Surface Hub (Windows 10 Team) and devices running Windows 10 IoT Core.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this sentence is correct, please move it from here to a separate paragraph so the flow of "what defines the app type" isn't mixed with "where might the app type be useful."

Copy link
Contributor

@riverar riverar Mar 4, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
such as Xbox, HoloLens, Surface Hub (Windows 10 Team) and devices running Windows 10 IoT Core.
such as Xbox, HoloLens, and devices running Windows 10 Team (e.g. Surface Hub) or Windows 10 IoT Core.

Nit: Surface Hub can be configured to run alternate Windows 10 SKUs that do allow for other app types.

I think the fact these restrictions are arbitrary and could be changed at any time, is a good reason to not make the requested changes to the FAQ. We're adding to the documentation debt here.

@ghost
Copy link

ghost commented Apr 4, 2021

@Felix-Dev
well, two types of apps will be here , (1.)native modern windows apps(mix of both win32+winRT apis),,, (2.)PWA/Web apps.

there's no place for a third.
UWP itself will be redundant basically, once Windows App Container technology comes to all win32 apps.

therefore, I humbly suggest you to drop the PR altogether. thanks.

@BenJKuhn
Copy link
Member

Closing old or abandoned pull requests. If you would like to pick this up again, address feedback, and push it over the finish line go ahead and reactivate.

@BenJKuhn BenJKuhn closed this Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants