Stupid Question 138: In RE to WinRT development what is the hardest bit to grasp/interesting for an iOS dev?
Yesterday I had the pleasure of doing a talk for the Cocoaheads Gothenburg user group on the topic WinRT for iOS developers. I was nervous and excited, maybe a little bit more than usual. .Net meets iOS- what can possibly go wrong?
The event rapidly got booked and it was pretty awesome to see the interest for such a different platform. I had prepared a one hour session, and it was packed with information- I had a lot to cover and although I had some idea what I would need to spend some more time on, I still decided to cover most topics on WinRT development comparing it to iOS development.
The session went really well, and in the spur of the moment I did some live coding for two hours while answering questions and at 9PM I basically had to start kicking people out because we all had (have) work the next day. It was awesome, and what a bunch of great developers I must say! I can’t wait to join on their future meetups!
Since the session was also a live rehearsal for my TechDays sessions I wanted feedback – it is always easier to get that from smaller groups than a large crowd.
One of the questions I had was what they considered to be the hardest bit to grasp and what was the most interesting as an iOS developer, basically what to spend more time on the next time. Turns out it was the concept of XAML- and also the MVVM pattern.
And by that I mean XAML and it belongings, so the language itself, the concept of datatemplates, defining styles and resources, the databindings,- and also how to leverage VS2012 and Blend (the tools used to work with Windows Store Apps, and other XAML technologies (and JS and Html Windows Store Apps). I had not gotten into the details of usercontrols and customcontrols, and that was something they would have liked to see and hear more about.
So more XAML and MVVM next time, anything else?
Comments
Last modified on 2013-01-29