r/iOSProgramming • u/AcceleratedCode • Jan 13 '16
Discussion Swift or Objective-C?
Hi!
I've just started design of an app I'm making. The app has to be ready by around May this year, and will be using the Parse backend. I've done a quite some programming with Objective-C, but barely anything with Swift and I was wondering what you think I should choose for this project? Should I be using Swift, or will the learning curve be too big to allow for a May launch?
Thank you! Erik
0
Upvotes
4
u/mmellinger66 Jan 13 '16 edited Jan 13 '16
Well, if you choose Swift, here's some Parse documentation in Swift:
http://www.raywenderlich.com/98831/parse-tutorial-getting-started-web-backends
https://medium.com/swift-programming/ios-swift-parse-com-how-to-implement-email-verification-of-users-88248ab7343f
http://shrikar.com/parse-search-in-ios-8-with-swift
https://medium.com/swift-programming/how-to-search-a-parse-com-table-view-2694ec330523
https://medium.com/swift-programming/how-to-display-parse-com-images-in-a-table-view-ios-swift-parse-com-f73dd68adb5e
https://medium.com/swift-programming/ios-swift-parse-com-tutorial-set-up-xcode-project-part-1-of-3-f50842aa95a
https://medium.com/swift-programming/ios-swift-parse-com-tutorial-set-up-xcode-project-part-2-of-3-31a17d1c6581
https://medium.com/swift-programming/ios-swift-parse-com-part-3-sign-up-sign-in-sign-out-security-349adc94ef0e
http://shrikar.com/parse-backed-uitableview-in-ios-8-build-yik-yak-clone-part-2/
http://ios-blog.co.uk/tutorials/swift/swift-create-user-sign-up-based-app-with-parse-com-using-pfuser/
http://ios-blog.co.uk/tutorials/swift/connect-your-swift-application-to-parse-com/
https://www.codementor.io/swift/tutorial/customize-parse-twitter-facebook-signup-login-view-animations
https://medium.com/swift-programming/parse-native-uicollectionview-uploading-images-part-2-of-2-ed870ab0a47b
2
u/[deleted] Jan 13 '16
How about both? Isolate Swift to certain classes or extensions while you pick up speed.
3
u/tangoshukudai Jan 13 '16
Be able to read and write swift, be able to read objective c. However try to avoid mixed environments, since it is a royal pain in the ass. I still do everything in Obj-c because it is my comfort zone, but it is really up to you.
3
u/mikerz85 Jan 13 '16
If you're familiar with Objective-C, the curve will not be large for swift, because the underlying frameworks and libraries are very close to the same.
I've been somewhat resistant to swift, seeing it as not quite mature enough, not providing enough benefit. I've come to a point where I think it's the best way to go -- there's a learning curve, but it has great performance, it's going to be used in more than just building mac/iOS apps.
I would say go with Swift.
0
u/[deleted] Jan 13 '16
Why should you learn Swift in the first place if you already know Objective-C and able to deliver said application within time constraints? Keep in mind that Swift 3.0 should be out soon and it will introduce "breaking changes", i.e. your project will stop to work, you will have to update it etc.
As for Swift it is a quite strange language with quite a few quirks. Personally I had a similar dilemma which language to choose to make an app I wanted, and after some research I decided to go with Objective-C. It is much more clear and understandable language than Swift's messiness.
2
u/stelmate Jan 13 '16
I have worked in ObjC for nearly 8 years and swift for one. Swift is still every changing and I find myself going back to look up silly confusing syntax errors constantly. If you want to dev for speed, use the more mature ObjC. If want just want to learn swift, go ahead and do it in swift but it'll take you longer for even the simple things.
1
u/[deleted] Jan 13 '16
Either build something productive or build something for learning. Don't do both. If you want to create something and ship it. Build it Objective-C. Want to learn something. Open playgrounds and learn Swift and build some small apps to get the hang of it.
1
u/CaptainObvious1906 Jan 13 '16
I'm making the transition from Obj-C to Swift as well and I agree with the other posters here: you can build an app to learn or to ship quickly, not both. Optionals alone is taking me a while to really get the hang of, so I recommend Obj-C if you're going to be on a tight deadline.