LambdaLambdaLambdaFn Posted January 26, 2015 Share Posted January 26, 2015 Is there a reason for developers to make a modern app after Windows 10 vs a desktop app in the short- to medium-term? The same seamlessness that attracts more users to 10 could be a disincentive for developers to re-program their stuff for modern. If you're bringing a new product to market, would you develop for 10 and give up that Win32 market that hasn't upgraded in exchange for Windows Phone and tablet? Link to comment Share on other sites More sharing options...
greenwizard88 Posted January 26, 2015 Share Posted January 26, 2015 It's Windows Phone and Tablet, but through services like Xamarin, it's also iOS and Android. Link to comment Share on other sites More sharing options...
elenarie Posted January 26, 2015 Share Posted January 26, 2015 For one, it is somewhat frustrating, because you have to change your development mindset. Many things are missing, and many things are being done differently, and because XAML WinRT development is so "similar" to XAML WPF, it ends up an infuriating experience when you can't do something in WinRT when you could do the same in WPF. Many APIs, classes and members are also missing detailed documentation regarding exceptions and practical examples. Also, the use of MVVM and similar patterns is hugely encouraged, which may not be for all people. I have actually switched from learning WPF to learning WinRT few days ago, and I think I made the right decision, because I can always go back to WPF when I need more power and access to the system. But for most consumer-facing stuff, I won't need to do that. But again, one must change one's dev mindset. Link to comment Share on other sites More sharing options...
PGHammer Posted January 29, 2015 Share Posted January 29, 2015 For one, it is somewhat frustrating, because you have to change your development mindset. Many things are missing, and many things are being done differently, and because XAML WinRT development is so "similar" to XAML WPF, it ends up an infuriating experience when you can't do something in WinRT when you could do the same in WPF. Many APIs, classes and members are also missing detailed documentation regarding exceptions and practical examples. Also, the use of MVVM and similar patterns is hugely encouraged, which may not be for all people. I have actually switched from learning WPF to learning WinRT few days ago, and I think I made the right decision, because I can always go back to WPF when I need more power and access to the system. But for most consumer-facing stuff, I won't need to do that. But again, one must change one's dev mindset. That, I think, is the REAL issue for developers - the mindset IS different. Link to comment Share on other sites More sharing options...
Ve7878 Posted February 6, 2015 Share Posted February 6, 2015 I suppose it will make it easier to get their apps on mobile. Link to comment Share on other sites More sharing options...
SledgeNZ Posted February 6, 2015 Share Posted February 6, 2015 Quite easy to code share and target multi clients with xaml \ .net. If you've had any experience with Silverlight then it's best to stick with how you do things within there as opposed to WPF as the majority of SL was transferred to RT. WPF was MS's first attempt at Xaml and it has so many nasty things which are best left in WPF. (Routed events \ bubbling, triggers). Quite easy now to write basic xaml that can be ported between WP\Win8\Wpf and even Xamarin. As to Win32, can't see any need to go anywhere near it. Handy to have as a bit of background knowledge. Link to comment Share on other sites More sharing options...
elenarie Posted February 9, 2015 Share Posted February 9, 2015 At least localisation is child's play. Just add a few files and everything is done automagically. Took me like 10 seconds to set up localisation for multiple languages. Link to comment Share on other sites More sharing options...
PGHammer Posted February 12, 2015 Share Posted February 12, 2015 Quite easy to code share and target multi clients with xaml \ .net. If you've had any experience with Silverlight then it's best to stick with how you do things within there as opposed to WPF as the majority of SL was transferred to RT. WPF was MS's first attempt at Xaml and it has so many nasty things which are best left in WPF. (Routed events \ bubbling, triggers). Quite easy now to write basic xaml that can be ported between WP\Win8\Wpf and even Xamarin. As to Win32, can't see any need to go anywhere near it. Handy to have as a bit of background knowledge. All too true - however, that became true when x64 reached ubiquity status, which had nothing to do with 8 at all. The only REAL reason for x32 when THAT happened was compatibility with XP, which was well-under-represented on the x64 side of things. With XP dead, that issue (except for niches) is just AS dead. Link to comment Share on other sites More sharing options...
Recommended Posts