Home/ Questions/Q 7932383
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T21:00:07+00:00

I’m working with a small startup with the goal of creating an iPhone application.

  • 0

I’m working with a small startup with the goal of creating an iPhone application. The programmers on our team all know both C and Java, but we’ve got no ObjC/C#/iPhone experience — we’ll be learning something no matter what. All the questions I’ve seen on this subject have been from the perspective of a C# programmer getting into iOS, so I don’t have any information on the relative merits of learning one or the other.

So, what I want to know is the relative merits of C# and Objective-C for new programmers, with respect to these things:

  • Performance
  • Ease of use
  • Ease of learning
  • Reliability (i.e., will a new iOS version break a MonoTouch app?)

Also, would writing in MonoTouch have any benefits for cross-platform development with Android?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If the goal of your startup is to create an iPhone app, then obviously you should learn the language iOS applications are built with, Objective-C. Your team already has experience with C, so it should be very easy to get started. The Big Nerd Ranch books will get you up and running in a week or two (I’m not associated with Big Nerd Ranch, I just think they’re awesome).

    I don’t understand why you bring up MonoTouch, considering your team doesn’t have C#/.NET experience. There are tons of other frameworks like MonoTouch, including Titanium SDK (JavaScript), RubyMotion (Ruby), and so forth. All of these are great, but as I see it are primarily for those with experience with their respective languages. They allow you to write iOS applications using a language you’re more familiar with, but have the following drawbacks:

    1. Performance can be just as good, but usually a little (sometimes a lot) worse than an application written in Objective-C.
    2. Resources for learning are not as plentiful as those for iOS SDK/Objective-C. There are tons of people who want to make iOS apps, and of those people some use these frameworks, and they are diluted amongst them. Only a small fraction of the resources available for iOS development will be devoted to any given framework.
    3. These frameworks are based on the iOS SDK/Objective-C, so naturally development is always a step behind. If Apple rolls out radically new APIs in the next version of the iOS SDK, you’ll have to wait for these frameworks to adapt (applications written in Objective-C might break, too, but it’ll be easier to deal with based on point #2).
    4. Most of these frameworks require a familiarity with the iOS SDK. You will still need to know that an application calls the - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions method on launch, but in addition you will need to remember how to translate that into the appropriate method for MonoTouch: public override bool FinishedLaunching (UIApplication app, NSDictionary options). The iOS SDK is massive, and most iOS developers rely on Apple’s documentation for insight. So you will be looking at the API docs, written for Objective-C, and translating methods into the framework of your choice.
    5. The Objective-C ecosystem is constantly evolving, with cool new projects like CocoaPods, bwoken, etc. These are primarily developed with Objective-C and Xcode in mind. Configuring them to work with your framework of choice will almost invariably cause you extra time and work.

    The above points have generally kept me from delving too much into any of these other frameworks. They’re all very cool, but their primary merit in adoption seems to be facilitating development for people with deep skill sets outside of Objective-C, or allowing cross-platform development for small teams lacking the resources to invest in Android and iOS (and Windows Phone) programmers. Hopefully the benefits outweigh the above costs for adopters.

    Also, would writing in MonoTouch have any benefits for cross-platform development with Android?

    I suppose it would. Indeed, the MonoTouch homepage touts that as a primary advantage of using the framework. I’m not so sure about view/controller classes, since those seem like they would be tied into UIKit, but the logic encapsulated in your models should be fairly easy to port.

    Long story short, I think you and your team should stick with Objective-C for iOS development.

    • 0