3 ms·

Disagree with the simplistic conclusion. Before I make a long comment, please spend a few minutes to take a look at this video and make your own conclusion: ht

by hz10 7y ago

Disagree with the simplistic conclusion. Before I make a long comment, please spend a few minutes to take a look at this video and make your own conclusion: https://youtu.be/GrKA4D_8ngY?t=382 https://youtu.be/GrKA4D_8ngY?t=382

hz10 7y ago
My interpretation of the direction is the opposite of Thurrott’s in some sense – UWP will be expanded and morphed together with Windows Forms and WPP into .Net core app eventually with .Net Core 5.0 Here is my take of UWP development that I have expressed on different occasions: 1. The best target OS compared with Android and iOS. 2. The best IDE (VS). Android Studio is catching up fast, but still has a long way to go before rivaling VS. 3. The best user experience compared with apps on other platforms (e.g. Android) for for which I also develop apps. 4. The worst app store by far. I have been suspecting that Microsoft Store killed Windows Phone. WP came out late, but it had a decent chance to survive and thrive (its market share actually reached double digits in some European countries), but the lack of apps killed it eventually. I blame Microsoft Store for it. It is pretty much the worst in every sense and had glitches one after another. If Microsoft had outsourced the app store to a competent company, Windows Phone could be rivaling iPhone and Android now. It is as if Microsoft thought the poor store was not hurting UWP apps enough, they introduced .Net Native toolchain nightmare to hit UWP further. I have never noticed any promised app performance benefit. Instead, one app’s performance deteriorated so much that it became almost unusable under certain circumstances after .Net Native was used. An app’s debug version may behave significantly differently than its release version compiled with .Net Native. It takes 10 to 20 minutes to generate an app package with .Net Native. More than 90% app development problems I have encountered are related to .Net Native nightmare one way or another. Sideloading UWP app could make up a little bit for the store’s deficiency, but it seems they have changed the sideloading mechanism many times. I have lost track of it. In summary, UWP apps are the first-class products marketed and sold by a third-class store. I cannot help mentioning one emerging technology that adds absolute excitement to UWP – Uno Platform. It allows C# UWP code used for creating iOS, Android and WebAssembly web apps. It is truly “program once, run on billions of devices".
- miguelrochefort 7y ago
  I worked on Uno for a few years. We used it to build over a hundred iOS and Android apps. Nobody would guess they're built with UWP. I have done native development for UWP, iOS, Android. UWP delivers the most consistent API, advanced tooling, and productive devrloper experience by far. This is part of why we picked UWP as the abstraction API for Uno. That said, I believe that modern web development frameworks offer an even better developer experience, thanks to projects like TypeScript and React. I can't comment about Flutter yet.

by hz10 7y ago

hz10 7y ago

My interpretation of the direction is the opposite of Thurrott’s in some sense – UWP will be expanded and morphed together with Windows Forms and WPP into .Net core app eventually with .Net Core 5.0 Here is my take of UWP development that I have expressed on different occasions: 1. The best target OS compared with Android and iOS. 2. The best IDE (VS). Android Studio is catching up fast, but still has a long way to go before rivaling VS. 3. The best user experience compared with apps on other platforms (e.g. Android) for for which I also develop apps. 4. The worst app store by far. I have been suspecting that Microsoft Store killed Windows Phone. WP came out late, but it had a decent chance to survive and thrive (its market share actually reached double digits in some European countries), but the lack of apps killed it eventually. I blame Microsoft Store for it. It is pretty much the worst in every sense and had glitches one after another. If Microsoft had outsourced the app store to a competent company, Windows Phone could be rivaling iPhone and Android now. It is as if Microsoft thought the poor store was not hurting UWP apps enough, they introduced .Net Native toolchain nightmare to hit UWP further. I have never noticed any promised app performance benefit. Instead, one app’s performance deteriorated so much that it became almost unusable under certain circumstances after .Net Native was used. An app’s debug version may behave significantly differently than its release version compiled with .Net Native. It takes 10 to 20 minutes to generate an app package with .Net Native. More than 90% app development problems I have encountered are related to .Net Native nightmare one way or another. Sideloading UWP app could make up a little bit for the store’s deficiency, but it seems they have changed the sideloading mechanism many times. I have lost track of it. In summary, UWP apps are the first-class products marketed and sold by a third-class store. I cannot help mentioning one emerging technology that adds absolute excitement to UWP – Uno Platform. It allows C# UWP code used for creating iOS, Android and WebAssembly web apps. It is truly “program once, run on billions of devices".

miguelrochefort 7y ago
I worked on Uno for a few years. We used it to build over a hundred iOS and Android apps. Nobody would guess they're built with UWP. I have done native development for UWP, iOS, Android. UWP delivers the most consistent API, advanced tooling, and productive devrloper experience by far. This is part of why we picked UWP as the abstraction API for Uno. That said, I believe that modern web development frameworks offer an even better developer experience, thanks to projects like TypeScript and React. I can't comment about Flutter yet.