Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I am planning to learn objective-c to be able to build iOS Applications I have seen some guys using Monotouch sdk, I am really confused where to start from.

I have a solid experience in Developing sites and Application using .NET Framework Technology, should I go with Monotouch?

Will the application made in the native platform run faster?

Many Thanks.

share|improve this question
Is it still possible? Apple usually either stop the possibility to use this kind of tools or sues the creator. –  Johan May 31 '11 at 6:24
@Johan: They tried that once, and got burned by developer reaction. They aren't going to do that again. –  David Thornley May 31 '11 at 18:19

3 Answers 3

up vote 5 down vote accepted

The situation with Monotouch has changed in the last few weeks. On May 2nd, all the Monotouch and Monodroid developers were laid off, including Miguel de Icaza. He documents what happened in this blog post. He and the other MonoTouch developers started a new company Xamarin, however as they don't own the MonoTouch code they will probably have to start from scratch with it.

Since Novell (who is owned by The Attachmate Group) hasn't seemed to have hired anyone to replace them (and I don't see how they could hire the anyone to match the talent they got rid of), I don't believe you will get very good support continuing to use MonoTouch. Even their website (monotouch.net) isn't loading for me. So I can't see any way to justify paying $400 for a product that now appears dead.

So while it was a really nice platform to work with, I would hold off using it and either wait for the Xamarin guys to produce their framework, or to just use the apple tools.

share|improve this answer
if you were anxious to get going you could get started with monotouch though, just use the trial version and switch to xamarin when it's suppose to be released in a couple of months. It's suppose to be source compatible. Heck, Monotouch is a working platform so you could even license it and release while you wait –  konrad May 31 '11 at 8:48
@mko: I had actually bought the full version. I was very lucky though as I found out about this within a month since I bought it and was able to get a refund (Novell offers refunds for purchases within a month). It was a very good framework to use while I had it (and I still have the trial one installed). While you could use MonoTouch and release, I think it is too risky to use an unsupported product, especially when it targets iOS, which often gets new features. If you were 90% the way through writing a program though, it could be worth sticking with MonoTouch. –  David Miani May 31 '11 at 11:37
Agree, guess it depends a little on the scope of the project, how much risk you were willing to take and how anxious you are to release something :) –  konrad May 31 '11 at 11:55

Obviously, using Xcode is the better option for any Apple developer as support is readily available from Apple itself and it truly does include all the essential tools you'd need to create an iOS or Mac application.

What's more, Xcode allows you to connect developer account within one centralised place meaning if you're working within a team managing iOS device certifications are somewhat less tedious.

Anyone that asks me what SDK they should use, I alway say learn and take advantage of the iOS SDK provided by Apple and embrace the features included with the IDE of the SDK: Xcode.

share|improve this answer
Xcode is not an SDK, -1. –  alternative Jun 23 '11 at 13:39
My mistake: all edited. –  dbramhall Jun 24 '11 at 20:08
Okay, downvote purged. –  alternative Jun 24 '11 at 20:43
Upvoted!!!!!!!! –  dbramhall Jun 24 '11 at 20:44

I suggest looking at the available support structure for your desired framework. Xcode has far more support from developers (and Apple) than does MonoTouch. While MT might work just fine, it might not either, and then you may have trouble fixing what's wrong.

Perhaps you could use it to "mock-up" the app and to get the basic functionality working, but I think it'd be more work to do that than to just start writing in XCode.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.