I&#x27;ll take the counter-point here and vote for Objective-C. Swift has not reached a level of maturity that we&#x27;re comfortable with it for mission-critical code. Each Xcode revision brings breaking changes which require you to address manually, as the migrator is lacking. Interop with Obj-C works OK - not great - but with pure C, it&#x27;s a hassle. And the libraries and tools around Swift are just nowhere near as mature as they are for Obj-C... even first party; case in point, Xcode cannot even rename methods or extract constants from Swift code. No refactoring capability at all.<p>Having built several large apps which are live in the Store in both languages, I&#x27;m sticking with Obj-C for 2016. Give Swift another year before going all in.