The key to dependency injection is protocols. From there sprouts many variations, flavours, and techniques. Although this is yet another dependency injection™ blog post, I would like to share a pure Swift, battle-tested DI implementation with no outside dependencies or magic. It combines protocol extension and type erasure to give you a solid, flexible dependency injection.
There are hundreds of complex routing frameworks and libraries in iOS. Usually they’re overly complex to retrofit into an existing app or they completely bypass Storyboards. In this post, I’d like to offer a simple, native-like routing mechanism that leverages Storyboards like a boss to handle navigation.
The launch of this app was inspired from uncovering the joys, pains, and realities of mobile, web, and software development. Many of the blog posts dissect this very open-source app and other real-world projects. I built the native iOS and Android apps and are completely open-source.
A Swift framework for rapid development using a collection of utility extensions for Foundation and UIKit classes and protocols, along with associated unit tests. Cross-platform targets for iOS, watchOS, and tvOS and were used across various apps for providing a central and extensible API.
Working with the UITableView and UICollectionView is verbose and inconvenient; also the API’s are inconsistent with each other. In this post, I’d like to reconcile the two API’s and add some sugar to make it more pleasant to work with these commonly used controls.
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.