@ViewBuilder usage explained with code examples
The @ViewBuilder attribute allows you to create compact code and improve readability. SwiftUI forces you already to use the result builder.
The @ViewBuilder attribute allows you to create compact code and improve readability. SwiftUI forces you already to use the result builder.
In this tutorial I will try to present you how to use clean, testable and maintainable architecture when using SwiftUI. We start with diagram depicting this architecture and then we dive deep into…
Add RawRepresentable conformance to a custom type that represents a setting or a view state in SwiftUI to be able to save it in AppStorage or SceneStorage.
Since Apple introduced SF Symbols in 2019, many product designers for iOS, including myself, have been asking themselves when it will
Everything you need to know about the new application life cycle in SwiftUI 2
There seems to almost be a consensus in the community that singletons are
Dependency injection is an essential tool when it comes to making code more testable. This week, let's take a look at a dependency injection technique that lets us enable testability without forcing us to write massive initializers or complicated dependency management code.
How the MainActor attribute eliminates the need for us to manually dispatch UI updates on the main queue when using Swift 5.5’s new concurrency system.
Explaining the Dependency Injection pattern, by contrasting it with Service Locator. The choice between them is less important than the principle of separating configuration from use.
Learn how to use Resolver to implement dependency injection in your SwiftUI iOS apps to achieve easily readable and maintainable codebases.
Swift's type system is (mostly) fantastic. Its tight constraints and flexible generics allow developers to express complicated concepts in an extremely safe manner because the Swift compiler will…
Various techniques that let us define fully dynamic colors that adapt to the user’s selected color scheme, using either SwiftUI or UIKit.
When creating collections of objects or values in Swift, we usually use data structures provided by the standard library - such as Array, Dictionary and Set. While those three cover most use cases, sometimes creating a custom wrapper collection can enable us to make our code more predictable and less prone to errors.
The Codable protocols (Decodable and Encodable) were introduced to the Swift standard library with Swift 4.
The Codable protocols are one of the coolest recent additions to Swift. Even though it works similarly to its community counterparts like Unbox, Codable has the advantage of being powered by the compiler. One of my favorite features in Unbox was to give a context to the decoding operation. Let's take a look at how we can achieve the same with Codable and how I use to power a type-erased Decodable type.