Modern app development often requires asynchronous tasks to be triggered, executed in the background, then responded to once the asynchronous task has completed. While async/await has made this a far simpler process in structured environments, sometimes asynchronous jobs have to be handled in an unstructured way via Apple's Task {} API. This interface represents a convenient way to spawn tasks when we do not wish to block the current execution context waiting for the results. However, usage of this API can represent a challenge when trying to unit test our app, resulting in code that is difficult or impossible to test reliably. In this article we will explore ways to banish this unreliability forever by bringing structure to our use of Swift's unstructured concurrency. Read more…
One of the areas where SwiftUI's declarative architecture shows its fundamental departure from UIKit's object-oriented approach is in the field of gesture handling. Today we will explore a particular difficulty caused by this, and a potential solution. Read more…