Cool link with a side-by-side comparison of WP7, iOS, and Android development features and classes from a mono (C#) perspective.
XIB (Interface Builder)
n/a (any view)
n/a (binding, IEnumerable)
n/a (object properties)
Xaml Uri querystring params
n/a (object properties)
NavigationContext .QueryString .TryGetValue()
C# .NET objects – shared thanks to Mono on iOS & Android. Also WebClient, Linq, Generics, Xml, Serialization, etc…
And while we are on the mono subject, they just released a Mono droid update, which means they now have comprahensive tool chains for C# development for the following systems, iOS (including app store), Mac (including app store), Android (including app store).
Published on February 15, 2011. ClosedTags:mobile, WP7.
Lots of mobile news over at MWC at the moment. Found this interesting video showing of Windows Phone 7′s Internet Explorer 9 Mobile with hardware acceleration. Next to a non hardware-accelerated iPhone 4 browsing experience the difference is very dramatic.
This has been doing the rounds on the inter-webs today. It’s an interesting take, and a cool campaign, but I think I agree with the guys over at mobilecrunch. While I’m guilty of having my face down far more than I should, especially around my kids, I think it’s actually because I enjoy it, not because the present phone UI metaphore is too clunky (not that it isn’t clunky though).
Many a Sci-Fi writer has a decent take on this phenomenon in the future with their stories of massively wireless interconnected minds and the way people stare off into nowhere with absent eyes when they are busy communicating.
The thing I love about monotouch is that it lets me leverage my .Net Skills (not just c#, but how the .Net run time works) and marries it to the low-level iPhone development infrastructure. The hardest part about getting into iPhone development for me was Objective-C, and now I don’t need to go there.
Points to note:
Obviously since interpretation is not allowed on the iPhone the guys at the mono project had to put together monotouch, which statically links the parts of the .net framework needed into each iPhone app.
According to miggie, Monotouch for iPhone goes 1.0.
This enables you to use a static version of .Net (actual mono) with native C# bindings of the iPhone API, so no Compact Framework concepts for iPhone just yet. I agree with this decision, since people developing for the iPhone want their apps to look like they were developed for the iPhone.