Hmmm, so you mean the fact that Wp7 and win8 dev is all XAML + C# (or VB.NET) doesn't reduce the learning time? And the fact that we have state of the art application design tools doesn't make it quicker to build apps? I'm confused, what more do you want Microsoft to do.
In terms of a geek phone - sure Android is always going to be a better option as it's an open platform but with it comes developer frustration and fragmentation (have you tried testing and shipping an Android app!). You also have to remember that Windows Phone trails by a year or so, and as such the apis are also trailing by that amount. I'd expect that the next drop will have some more goodness that will make our lives easier. Nick Randolph | Built to Roam Pty Ltd | Microsoft MVP - Windows Phone Development | +61 412 413 425 | @btroam The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of ifum...@gmail.com Sent: Friday, 8 June 2012 8:55 AM To: 'ozDotNet' Subject: RE: Win8 Release Preview I agree, i have found that Microsoft is changing the development paradigms so often that i have been looking at learning android/ios because i no longer see any gap differences between learning non MS development. I have had a wp7 phone for a year and still find the android better suited to my needs. Basically, anything advanced is not being done on wp7 as it restricts so much the apis. Anthony From: ozdotnet-boun...@ozdotnet.com<mailto:ozdotnet-boun...@ozdotnet.com> [mailto:ozdotnet-boun...@ozdotnet.com]<mailto:[mailto:ozdotnet-boun...@ozdotnet.com]> On Behalf Of Greg Keogh Sent: Friday, 8 June 2012 8:06 AM To: 'ozDotNet' Subject: RE: Win8 Release Preview >sorry Greg, you indicated that you thought it's more confusing now, >I completely disagree as the metro guidelines are very strong) A web search for "Windows 8 design guidelines" produces some possibly useful information, and some of it is frightening. Where are the technical guidelines for developers? http://msdn.microsoft.com/en-us/library/windows/apps/hh464920.aspx >From this, I can understand that the points are admirable and must be the >result of vast amounts of research into how our eyes and brains work: clear, >clean, touch, scaling, charms, tiles, roaming, suspend, etc. It all generally >makes ergonomic and usability sense. Yes it's all certainly an admirable mission to implement these things. But I'm quite upset at the degree of sudden paradigm change and the lack of warning and advertising (even as a developer). Even if "the metro guidelines are very strong", they're completely mutated away from any guidelines that have gone before. I'm extra angry simply because of the extra workload and burden of leaning yet another suddenly released standard. Development is hard enough already with a huge mess of kits, tools, operating systems, languages and patterns all competing with each other and giving me too much choice (too much choice is a bad thing!). Now I have Win8 and Metro on top if it all, just more sh*t to bog me down and waste more time futzing around in what I know will be hopeless hair-tearing frustration where everything doesn't work. So I guess I'll have to try and develop a Win8 compliant app and see how difficult it is. How anyone done this and can report from the coal face of coding? Greg
