Have you developed any application which is approved by Apple and is available on App Store??

When you guys have made that then you can argue on merits of Monotouch.
Moreover, they charge a lot for their License.

I am a objective-c developer and c# developer.
I really found monotouch very frustrating experience.
I dont think developer who only knows Monotouch and c# can develop iphone Apps

I do however agree with Jeff’s blog post that you reference much more wholly than yours. There are defiantly allot of good reasons to spend the time learning the tools apple has supplied, and there allot of lessons that are absolutely essential that everyone working on the platform learn that the process will short-cut. From what it seems so far, the UI tools are half baked, the resulting ipa is bloated and in efficient, and though there are many great flash developers out there, there is little to no great flash applications out there. When they bring it out and the app store gets flooded with every bit of nonsense someone has made in flash over the last 5 years being compiled for iPhone with no thought at all and good apps are hanging in a que for review for months I think it will reflect badly on Apple, the iPhone development community, and the platform itself, the user won’t even consider Adobe.

I’ll admit my attitude towards Flash has been bad for a long time despite the fact I think it is a powerful too with great potential for what it was originally designed to do. The problem I have with flash is that it give people who don’t have a clue the means to do something semi complex with great ease and not so great implementation, then because they don’t have a clue they run wild. There are enough people who have half a smattering of common sense and can actually write good code shoving absolute crap like fart apps etc onto the platform, I don’t feel like I would want to happily invite what has turned into a plague on the web into the platform as well even if it will bring with it a handful of extremely talented developers.

I have been trying to stay out of what I see as a religious war on this topic. Life is too short for that. After reading Martin’s tweets on this topic (see @pilky… you’re welcome ;) ), I thought I was going to come here only to find more of the same from him: all potential MonoTouch developers are lazy bastards because they don’t want to use native APIs. Well, all those native APIs are available. As MonoTouch developers we are using UIKit, Foundation, MapKit, etc. You name it, we can use it. If there’s an Objective-C library you want to use, you can bind it. And you mentioned C – we have P/Invoke for that too. The world, as they say, is your oyster.

Are there times when Apple’s tooling might make life easier at the moment? Certainly. Right now MonoDevelop (the IDE for MonoTouch development) is able to pick up changes made in Interface Builder (yes, we use Interface Builder), but Interface Builder does not pick up changes made in MonoDevelop. So the seamless to’ing and fro’ing that you get from XcodeIB is not quite there yet (I suspect it will be eventually). However, when you add an outlet in Interface Builder a property is automatically code-gen’d back in MonoDevelop and that’s a pretty nifty timesaver.

I suppose what I’m hoping is that we can all get along. I love Cocoa and Objective-C, but I also love .NET and C#. Given that MonoTouch has made it possible to use all of the iPhone’s native APIs so that user’s get a fantastic native experience, can’t we put aside our differences in preference? In the end, isn’t it all about providing high quality applications to the user?

Now maybe I’m jaded by the many appalling cross platform APIs and programs on desktop computers, none of which really fit in or work very well. Maybe MonoTouch will be different, being only for the iPhone. But from everything I’ve seen on any platform to date in terms of trying to work around native APIs has led to inferior quality applications.

But one of the most important business needs of any developer should be to provide a great user experience

Absolutely. But I don’t think you’ve shown that native tools are the only way to do that. As Miguel points out, here is no way to tell whether an app has been written in MonoTouch or not since it’s using the exact same libraries. The only difference is that the compilation process to produce the binary is different. How does that suggest a poorer user experience?

I’d also be very interested in your (and other Objective-C devs’) feedback on Miguel’s point: objectively, MonoTouch is *better* than Cocoa Touch since it implements everything Cocoa Touch does, plus Garbage Collection and so on.

As an existing Cocoa developer, naturally Objective-C and Xcode feel right. What makes you think that someone looking at Miguel’s comment is a lazy developer who doesn’t want to learn a new language, and not just one who wants to write bug-free iPhone apps with a great user experience?

Thought experiment: if someone made a compiler so that you could target .NET with Objective-C (there probably is one, actually), how would using that language be ‘lazy’ if you already knew it compared to learning, say, C#. I think the point is that .NET developers are used to seeing the platform as one thing, and the language as another. You can target .NET in pretty much any language ever conceived, and all languages are (or at least can be) equal citizens.

If MonoTouch delivers what Miguel says it does, how is it in any way lazy or likely to lead to a poor user experience?