[aqadan]

I've been an iOS guy for 6 years now; recently, I've had to pick up swift to adapt with the market and the many readily available resources being in swift. I say this because the advice I'll give you is based on what I've seen in the Bay Area, larger companies, and even from a personal learning experience. If you can build an app from scratch in Swift and publish it to the App Store, then you're golden in the job market. It's always the apps you have in the App Store that will bring out your resume when companies look to bring you in for interviews. With that being said, here are some pieces of advice I have for Swift vs. Objective-C: - Learn Swift through the iTunes U Standford course and master it - Stay upto date with the NSHipster blog for many of the ins and outs of Swift, Obj-C, and the iOS framework - Be sure to learn some of the Objective-C concepts that aren't that common in Swift (contact me for more details) - Research the common iOS interview questions as many of them still pertain to Objective-C - Understand your basic CS theory: Data Structures, Algorithms & their complexities, OOP, System programming - Integrate libraries that are written in Objective-C into one of your Swift apps and be sure to know how to incorporate it correctly

Currently, I'm working with a team of iOS engineers to build out our SDK for our service. One of the issues we've come up with over the past year was Swift vs. Objective-C. We made the decision to continue development and refactoring in Swift while maintaining our well written Objective-C code base. So, anyone coming on to our team would need Swift experience and be able to understand some details in Objective-C.

If you have any questions about what I mentioned, you can email me: [e-mail]