Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial


iOS Dev with Objective-C VS iOS Dev with Swift

Hi i'm very curious about IOS Dev and i was wondering which would you you recommend me take?

2 Answers

Hi Derrick,

So, if you have the time, it would be advantageous to learn both. If not, the smart decision would then depend on your goals.

If you're planning on creating a brand new iOS / OS X app, go with Swift. It is much, much, much, much easier to use and understand than Objective-C's arcane inanity. Of course, somewhere along the line, there's a teensy-weensy chance you might need to understand basic Objective-C to ... Idk... use some framework or something. But that's okay, that's what this course is for.

If you're planning on getting a job in industry as an iOS developer, you're better off learning Objective-C first. Most active app companies expect the iOS developers they hire to be able to maintain and update existing codebases, almost all of which will have been written in Objective-C. And that's not going to change anytime soon either since the novelty of Swift is hardly an incentive for a company to re-write their entire codebase. So if you're trying to get hired, go down this path.

Thanks for your insight Mikis! What you and Michael said made sense. I think i will start with Objective-C first.

Michael Hulet
Michael Hulet
47,912 Points

Many of my peers won't agree with me, but I personally say you should start with Objective-C, and then move onto Swift, and not vice versa. My reasoning as to why is discussed thoroughly in another one of my answers that I'll look for when I'm not as remarkably tired as I am now

Thanks Michael. I will look out for your response another time then.

Michael Hulet
Michael Hulet
47,912 Points

I'll be sure to comment here when I find the detailed explanation of my reasoning that I previously typed out, so you get a notification, but in the meantime, you can totally start on either one. Have fun!