所以，我对之前类似问题的回答是学习Objective-C。(另外，不要忘记调试支持)

This will probably offend some but to be honest, if you are going to do any serious development, you should learn Objective-C. Not knowing Objective-C in iPhone development will just be a hindrance. You won't be able to understand many examples; you have to deal with the quirks of Mono whereas if you had a working knowledge of Objective-C you could get a lot more out of the platform documentation. Personally, I don't understand the position that says increasing the amount of information you need in favor of using Mono over the platform's native language. It seems somewhat counterproductive to me. I think if this is a very expensive proposition (learning a new language) then it may be worthwhile spending some time on fundamental programming concepts so that learning new languages is a fairly cheap proposition.

另一位用户也这样写道:

现在单触摸对你来说更容易了。但之后就更难了。

例如，当新的种子出现时，你需要测试，但由于某种原因破坏了MonoTouch，会发生什么?

通过坚持使用Mono，任何时候你在寻找框架的资源时，你都必须在心里转换成你将如何在Mono中使用它们。你的应用二进制文件会更大，在使用Objective-C几个月后，你的开发时间不会更快，而其他应用开发者会比你更有优势，因为他们使用的是原生平台。

另一个需要考虑的问题是，您希望使用c#，因为您对该语言比Objective-C更熟悉。但是iPhone学习曲线的绝大部分并不是Objective-C，而是框架——你也必须调用c#。

对于任何平台，你都应该使用直接表达该平台设计理念的平台——在iPhone上，那就是Objective-C。从相反的角度考虑这个问题，如果一个习惯用GTK编程的Linux开发人员想要编写Windows应用程序，你会认真地建议他们不要使用c#而坚持使用GTK，因为这样做对他们来说“更容易”吗?

作为一个同时拥有c#和Objective-C经验的人，我想说对于大多数人来说Xamarin是物有所值的。

c#是一门设计得很好的语言，c# API也是设计得很好的。当然Cocoa Touch的API(包括UIKit)也有很好的设计，但是语言可以在几个方面得到改进。当你用c#写代码时，你可能会比用Objective-C写相同的代码更有效率。这是由于几个原因，但其中一些原因是:

C# has type inference. Type inference makes writing code quicker, since you don't have to "know" the type on the left-hand side of an assignment. It also makes refactoring easier and more saver. C# has generics, which will reduce errors compared to equivalent Objective-C code (though there are some work-arounds in Objective-C, in most situations developers will avoid them). Recently Xamarin added support for Async / Await, which makes writing asynchronous code very easy. You'll be able to reuse part of the code base on iOS, Android and Windows Phone. MonoTouch largely implements the CocoaTouch API's in a very straightforward way. E.g.: if you've got experience with CocoaTouch, you'll know where to find classes for controls in MonoTouch (MonoTouch.UIKit contains classes for UIButton, UIView, UINavigationController, etc..., likewise MonoTouch.Foundation got classes for NSString, NSData, etc...). Xamarin will give users a native experience, unlike solutions like PhoneGap or Titanium.

现在Objective-C比c#有一些优势，但在大多数情况下，用c#编写应用程序通常会减少开发时间和更清晰的代码，并减少将同一应用程序移植到其他平台的工作。一个值得注意的例外可能是依赖OpenGL的高性能游戏。

在这篇文章中有很多开发者没有尝试过MonoTouch和Objective-C的传闻。似乎大多数Objective-C开发者从未尝试过MonoTouch。

我显然是有偏见的，但你可以看看MonoTouch社区一直在做什么:

http://xamarin.com

在那里，你会发现一些开发人员用Objective-C和c#开发的文章。

使用Mono并不是一种依赖。它为iPhone操作系统增加了很多功能。LINQ, WCF, Silverlight应用程序之间的可共享代码，ASP。NET页面，一个WPF应用程序，一个Windows Form应用程序，还有针对Android的mono它也适用于Windows Mobile。

So, you can spend a bunch of time writing Objective-C (You'll see from many studies where the exact same sample code in C# is significantly less to write than OC) and then DUPLICATE it all for other platforms. For me, I chose MonoTouch because the Cloud App I'm writing will have many interfaces, the iPhone being only one of them. Having WCF data streaming from the cloud to MonoTouch app is insanely simple. I have core libraries that are shared among the various platforms and then only need to write a simple presentation layer for the iPhone/WinMobile/Android/SilverLight/WPF/ASP.NET deployments. Recreating it all in Objective-C would be an enormous waste of time both for initial dev and maintenance as the product continues to move forward since all functionality would have to be replicated rather than reused.

那些侮辱MonoTouch或暗示它的用户需要拐杖的人，是缺乏拥有。net框架的大蓝图，可能不理解逻辑与表示的正确分离，这种分离可以在跨平台和设备上重用。

Objective-C is interesting and very different from many common languages. I like a challenge and learning different approaches... but not when doing so impedes my progress or creates unnecessary re-coding. There are some really great things about the iPhone SDK framework, but all that greatness is fully supported with MonoTouch and cuts out all the manual memory management, reduces the amount of code required to perform the same tasks, allows me to reuse my assemblies, and keeps my options open to be able to move to other devices and platforms.

如果这是你唯一要开发的iPhone应用程序，而你对开发Mac应用程序毫无兴趣，那么MonoTouch可能是值得的。

如果你想要开发更多的iPhone应用，或者想要做一些Mac原生开发，那么学习Objective-C和相关框架可能是值得的。另外，如果你是那种喜欢学习新东西的程序员，这是一个有趣的新范式。

所以，我对之前类似问题的回答是学习Objective-C。(另外，不要忘记调试支持)

This will probably offend some but to be honest, if you are going to do any serious development, you should learn Objective-C. Not knowing Objective-C in iPhone development will just be a hindrance. You won't be able to understand many examples; you have to deal with the quirks of Mono whereas if you had a working knowledge of Objective-C you could get a lot more out of the platform documentation. Personally, I don't understand the position that says increasing the amount of information you need in favor of using Mono over the platform's native language. It seems somewhat counterproductive to me. I think if this is a very expensive proposition (learning a new language) then it may be worthwhile spending some time on fundamental programming concepts so that learning new languages is a fairly cheap proposition.

另一位用户也这样写道:

现在单触摸对你来说更容易了。但之后就更难了。

例如，当新的种子出现时，你需要测试，但由于某种原因破坏了MonoTouch，会发生什么?

通过坚持使用Mono，任何时候你在寻找框架的资源时，你都必须在心里转换成你将如何在Mono中使用它们。你的应用二进制文件会更大，在使用Objective-C几个月后，你的开发时间不会更快，而其他应用开发者会比你更有优势，因为他们使用的是原生平台。

另一个需要考虑的问题是，您希望使用c#，因为您对该语言比Objective-C更熟悉。但是iPhone学习曲线的绝大部分并不是Objective-C，而是框架——你也必须调用c#。

对于任何平台，你都应该使用直接表达该平台设计理念的平台——在iPhone上，那就是Objective-C。从相反的角度考虑这个问题，如果一个习惯用GTK编程的Linux开发人员想要编写Windows应用程序，你会认真地建议他们不要使用c#而坚持使用GTK，因为这样做对他们来说“更容易”吗?