Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ZillaG

macrumors newbie
Original poster
Nov 4, 2012
23
8
After years of being away from it, I want to get back into iOS development. I'm from the Objective-C world. Is everything with Swift now, or can I still develop in Objective-C? I don't mind learning Swift, so should I go ahead and do it?
 

firewood

macrumors G3
Jul 29, 2003
8,139
1,381
Silicon Valley
Currently, Xcode and Cocoa Touch fully support app development in both Swift and Objective C (either or both). So you can use either for iOS apps for which you can find decent API documentation. However, a lot of Apple's new documentation is Swift only.

Except for the evil stuff that Swift requires to get access to C pointers and memory, it's pretty easy for an experienced Objective C programmer to learn Swift 3 or 4. A few weeks of study to fall on all the gotchas, and a couple learning apps in Swift should do it.

So my earlier apps in Objective C, I'm keeping them in Objective C, even when doing significant updates. However any new apps that use completely new APIs, such as ARKit, etc., I'm writing in Swift.
 

ZillaG

macrumors newbie
Original poster
Nov 4, 2012
23
8
Ok make sense. I started an app in ObjC so I'll finish it in that. Thanks.
 

bjet767

Suspended
Oct 2, 2010
967
320
I use exclusively OC, but the frustration is all the example are now being given in Swift. I've been getting good at converting them to OC when I need to.

If it doesn't matter to you moving to Swift would be a good thing.
 

AxoNeuron

macrumors 65816
Apr 22, 2012
1,251
855
The Left Coast
Most of the job market these days is for Swift, that's for sure. The only time I see Objective-C these days is when you are working with legacy code.
 

Erendiox

macrumors 6502a
Oct 15, 2004
706
12
Brooklyn NY
My experience working in the field is that there's still a ton of legacy code written in Objective C and companies aren't exactly chomping at the bit to convert their entire codebase over to a new language. Swift also has a bit more growing to do before many would consider it to be fully matured. Because of that, being able to read and write Objective-C code is still a valued skillset.

That being said, Swift is the future. The new code I'm writing is almost entirely in Swift. Knowledge around interoperability of the two languages, handling mixed projects, is central to being marketable as an iOS developer right now.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.