Clever Geek Handbook

Should we build our native SDK with Swift or Objective-C and is there an SDK built entirely in Swift?

My company is currently planning to provide our services and UI components as their own SDK. What are the pros and cons of building SDKs in Swift vs Objective-C?

Note. Our clients who will integrate our SDK will either use Swift or Objective-C.

+3


source to share


1 answer


I'd really like to watch this talk by Jonathan Blochoxom : http://realm.io/news/swift-objc-best-friends-forever/

It says:

"Swift and Objective-C work together quite well, so there are many reasons why you would like to include both in the same project. Maybe a handy Swift library that you want to use in Objective-C, or vice versa. If you have a lot of code Obj-C base and you want to learn Swift, now is the right time to do it.Swift was built for Objective-C compatibility and also works with C but not C ++. types in Objective-C move fairly well to Swift : BOOL to Bool, NSInteger to Int, SEL to Selector, etc. "

In my limited experience, using Objective-C code from Swift is more common use case and rather trivial. Using Swift code from Objective-C is certainly possible, but it has some gotchas: In particular, check out "Alamofire in Obj-C Case Study" in the video.



Alamofire is an HTTP networking library written in Swift from the creator of AFNetworking : https://github.com/Alamofire/Alamofire

Also, I would recommend that you read the official doc: https://itunes.apple.com/us/book/using-swift-cocoa-objective/id888894773?mt=11

I hope this helps.

0


source






More articles:


All Articles