Starting an iOS project involves making a key decision: choosing the language for the development. When it comes to native mobile app development, there are two possibilities: Objective-C and Swift. What are the differences between them? What are pros and cons of each one? And, finally, which language will be better for your project?

With Swift 2.0 already out, most of the community is already familiar with the major new features, including reflection, error handling and Objective-C generics, which we’ve covered on our blog before. But the latest Swift version includes many other lesser-known functionalities, some of which I would like to discuss today.

Today there's a substantial number of people working at Netguru, especially at the HQ, in Poznań. Together with the Netguru iOS team we have addressed the problem of quick and easy room reservations for calls and meetings. We developed the Roomguru app for managing your meetings in Google calendars. And it’s open source!

Recently, we’ve developed our first Swift app, with a few folks involved, and most of them new to Swift. The problem I want to describe emerged pretty quickly and there was only one way to deal with it - outlining our own Swift style guide.

Should startups build new iOS MVP projects in Objective-C or Apple's new language, Swift? When trying to answer this question, it’s helpful to understand a little bit about the history of Objective-C and Swift.