The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
So I asked this question once a few months after Windows 10 was released, but now that it has matured a little I wonder what people's opinions are. I personally don't see any advantage to UWP. Windows Phone is dead, Hololens is kinda cool, but is expensive and despite what Microsoft wants you to think, there is probably o value in porting your apps to work with it. That leaves us left with targeting Xbone and PC. Hardly universal anymore, and to be honest, unless you are developing games (I'm not) Xbone is not a useful target. I'm sure there are a lot of PC users to target, but how many people actually use the store? I know I have 3 or 4 store apps and they are all games. It makes more sense just to use WinForms or WPF at this point. What do y'all think? Is there much point in targeting UWP for you apps?
I was initially going to deploy as UWP to the windows store, but the burdens of it became so overwhelming that I've mostly given up on it and the thing is that it actually runs. It's just all of the stuff for deployment. Getting the icons and splash screens going.
I did all of that for the Android app and it was a really streamlined process. Even getting it into the Android store was so easy. Lots of hurdles to get to the UWP release.
The last straw was when I learned that the UWP would run exclusively on Windows 10 Anniversary edition. To get it to run on people's Win8.1 machines I had to target another UNIVERSAL deployment.
I even made this graphic in dishonor of microsoft's use of the word UNIVERSAL: http://raddev.us/images/cp/uwpNot.png[^]
does that mean you've dumped the UWP code in the bitbucket entirely, or has MS came up with a sane way to distribute UWP outside the store?
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
does that mean you've dumped the UWP code in the bitbucket
Thanks for asking and continuing the conversation.
I plan to still deploy the UWP (probably as two versions - win8.1 and win10) because the code is completely done. I just need to get a WinStore / dev account and do all that overhead work.
Right now focusing on getting to iOS then after that I'll release the UWP.
Honestly, I'm already quivering from the possibility of problems.
I'm hoping somehow I fall through the cracks and my app is immedately received.
I just got an email (minutes ago) and it looks like I'm officially an AppleDev now so we will see.
I am not actively doing it, but my question would be this.
Does targeting UWP guarantee Xamarin compability? If so, this would dismiss your Windows Phone concern as you could then deploy easily to android and iOS. If you target WinForm or even WPF you are likely to run into snags in a deployment (you can do it, but I am thinking UWP is seemless)
Otherwise, your thoughts are as I think most are in that most systems have no point on the Xbox and the Hololens just seems to far out to be worried about. I mean, I could see targeting it for the sake of targeting it to learn about it and deploy something, but I would certainly not recommend it for an actual business system that is being paid for unless that is what is requested. In fact, if that was requested I would likely even ask "why" to make sure they actually know what they are asking for.
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
The interesting thing about software is it can not reproduce, until it can.
I'd say that depends on your target audience. If they want a desktop or a client/server app, Winforms and/or WPF should be perfectly fine. If they want a web-app then perhaps you'd use ASP.NET or something similar. If they want a mobile app - your priority targets would certainly need to be iOS and Android (95%+ combined market share), and if so you'd want to use Xamarin.
Using UWP would make sense if your product includes a device - so you'd be selling a pre-customized Win 10 tablet/laptop with your app running on it. Although at that point you need to ask yourself if you'd be better off writing an old fashioned desktop app.
> It makes more sense just to use WinForms or WPF at this point
I preferring an ultimate way in Windows development - firstly target Windows Desktop (WinForms/WPF/etc. for Windows XP+), and next Windows Phone and UWP/Metro (Windows 8+ only).
All another depends on specific application and its goals.