Should my iOS SDK (to be released early in 2016) be written in Swift or Objective-C?

| | August 10, 2015

Let’s assume I know both languages. What language should I choose regarding the pros and cons of the two options?

Swift 2.0 will be out at that time so I’m seriously considering this option. On the other hand, I don’t want the Objective-C developers who will need to integrate the SDK to find difficult to do so because of the bridges they need to configure. Moreover, by choosing Swift the target would have to be iOS 7+.

What do you think?

One Response to “Should my iOS SDK (to be released early in 2016) be written in Swift or Objective-C?”

  1. If you’re comfortable with Swift then by all means use it, the only issue is that swift as a language isn’t actually finished so it’s likely to change over time.

    Most Frameworks tend to be written in Objective-C as it allows them to be ported to other platforms e.g. using Unity as it can interface with C code.

    So basically this one is down to personal preference, I would tend to use Objective-C for frameworks as I would probably want to use it from Unity but if it’s only ever going to be used in a native iOS app then it doesn’t particularly matter.

Leave a Reply