Using DispatchWorkItem to delay (and cancel) tasks
Performing delayed tasks and working with multithreading in Cocoa became much simpler since the introduction of GCD - Grand Central Dispatch. Before it existed, delaying a task would require using
NSOperationQueue, or the simple but limited
performSelector:withObject:afterDelay: method available in
NSOperations are better, in general, when you need to manage multiple tasks that can be added to a queue (like sequential image downloads, for example), GCD allows a simpler API to run blocks of code with the
dispatch_after (Objective-C) and
When to use a
With a practical example in mind, assuming we want to show a hint indicating that our messenger app supports voice messages now. To do so, we’ll make the microphone button jump:
If you’ve been developing with Swift for a while, chances are high you already used this API. Now, imagine that, if the user found the button before it jumped - we definitely don’t want to trigger the hint. We could do it in a way - not the cleanest one:
This is how we would to it before knowing about
DispatchWorkItem. Let’s compare with how this can be achieved, but using
Isn’t it much better? I believe so, for a few reasons. First, every task can be assigned to a different work item. Secondly, in case we want to cancel it, there is no need to keep one state variable for each task.
It is worth noting that, although GCD is available in both Objective-C and Swift,
DispatchWorkItem Swift only.
DIY - Keep things simple while you can
A few months ago, Guilherme Rambo tweeted a great example of how easily this API can be used to create things that, often, we consider using a framework for.
DispatchWorkItem ❤️ pic.twitter.com/6gxCLA4Wmo— Guilherme Rambo (@_inside) April 13, 2018
With less than 30 lines, Guilherme showed us how to create a simple throttler for a specific UI event. Within his tweet’s replies, some people suggested he should try RxSwift, as it offers the built in
.debounce() operators. Well, if we have a project that is already using it, fine. But if we don’t want to add to our app a new dependency, I believe it makes more sense to keep things simple. My rule of thumb is: Always prefer system APIs and simplicity over 3rd party frameworks when possible.
Of course, Gui’s example is a specific use case. But with little effort we could make it something more generic. For example, that listens to
NotificationCenter and throttles a
Notification when it’s posted:
Managing multiple work items
If we end up having multiple work items managed by the same view controller, we should think if the current design is correct. One way to fix it is splitting the responsibilities of a view controller in multiple child view controllers. If we tried doing so and still have 3 or 4 work items that need to be managed by the same view controller, having them as multiple references is far from ideal.
A solution that I came up with, was creating a
Dispatcher object, that would manage the work items according to an identifier. It should allow:
- Scheduling multiple tasks by identifier (a string) and delay (time interval);
- Overwriting (cancelling and rescheduling) a scheduled task if a task with the same identifier already exists;
- Cancelling tasks by identifier;
- Cancel all tasks when it is deallocated
After a few iterations and inputs from friends, I was able to get to this (you can see the playground version here):
In a Paragraph
DispatchWorkItems are provide us a simple way to perform powerful and complex tasks, that would require us using different or older APIs. Sticking to it might save us from unnecessary frameworks or wrong abstractions and architectures.
Feel free to add any comments below, or ping me on twitter if you have any suggestions or ideas: @natanrolnik