Localization in Xcode is handled with NSLocalizedString, but it is such a verbose and legacy-like API. There’s a Swiftier way that still respects Xcode .xliff exports and comments.
Swift is a unique language that has some revolutionary ideas. One of which is protocol conformance extension. This concept allows you to take an existing type and force it to adopt another protocol it never knew it existed before.
In this post, I’d like to show you how to create a Swift framework for iOS, watchOS, and tvOS and get them distributed via Carthage and CocoaPods. It’s a technique I use to share frameworks across all my apps and with the community.
CocoaPods are a must for any serious iOS project. Why reinvent the wheel when the community has produced robust and feature-rich plugins? In this post, I’d like to highlight the best CocoaPods I’ve used in real-world project that are also Swift-friendly.
CocoaPods are the de facto way of sharing and distributing iOS and OS X code. It manages third-party dependencies in a easy, fast, and safe way. There are thousands of CocoaPods available, but almost all of them are in Objective-C. Today I’d like to show you how to create a CocoaPods in Swift.
Are you rocking Swift yet? Now is time to share your code across the whole project for maximum reusability. This becomes even especially essential when creating Apple Watch apps since sharing code between the watch and the phone is a natural occurrence. In this post, I will show you how to create a framework in Swift to do this.
In this post, I’ve outlined the steps for submitting your shiny new watch app to the App Store. If you done this before with the iPhone, the steps are similar. However, there are slight differences with Apple Watch and also the latest Xcode 6+ makes this a bit easier with some automation.