MicrosoftOk, so there's a lot of comments about the name "Windows App" and nothing about either "Windows" or "App" two overloaded terms that everyone here seems to know what they mean. For those of use that are worried about RDP compatibility calling it "Windows App" is not the most important problem. Call it Fred, Joe, Bob or Sally. It simple doesn't matter. For those of us dealing with .Net, .Net Framework, .Net Standard and .Net Core or Windows Universal Platform, WindowsRT or Windows App libraries, not to forget Xaml, Xamarin, and MAUI. It just doesn't matter. Microsoft is desperately trying to get rid of its baggage and move to virtual desktops. So, the plan seems to be -- use an "app." And since this is Microsoft, it should be the "Windows App." And, since Windows will no longer be tied to the desktop -- everyone will be remote, using the app on Android, iOS, Mac, Windows desktop or the browser to get to their virtual desktops running seamlessly in the cloud. Therefore, discard all previous meanings and preconceptions and think: one app to rule them all. That is, until the division is laid off, the initiative is dropped, and we go back to our PCs, Macs, phones and devices running Baidu+.
