Microsoft's UWP = Unwanted Windows Platform?
I&#x27;m probably the only person who started learning UWP in 2020; when the pandemic hit and I suddenly had a lot of time on my hands, I spent months building a UWP application for my own use.<p>I think this is the right call on Microsoft&#x27;s part. UWP has been semi-abandoned for a while now and it&#x27;s nice to get some clarity on its future (or lack thereof).<p>UWP had many pain points (the .NET Native compiler, installation, filesystem access, sandboxing, longstanding XAML limitations), but it wasn&#x27;t all bad. You can tell that the Windows team spent a <i>lot</i> of effort trying to make UWP&#x2F;WinRT&#x2F;WinUI successful, and it&#x27;s a little sad that most developers never got to see the good parts of UWP. Among other things, UWP made it remarkably easy to build interfaces that &quot;just work&quot; with both touch input and keyboard+mouse.<p>It&#x27;s unfortunate that UWP was hobbled from the start with so many restrictions. I think it would have seen much more adoption if it had been built with an escape hatch from the draconian distribution+sandboxing requirements.