


Responsiveness: If you only perform user-visible work on the main UI thread, then users won’t notice that the app slows down or freezes up periodically due to work that could be performed on another thread.Faster execution: By running tasks on threads, it’s possible for work to be done concurrently, which will allow it to finish faster than running everything serially.There are many advantages to splitting your app’s work into multiple threads: You can have as many threads executing at once as you have cores in your device’s CPU. Your iOS app is a process that runs multiple tasks by utilizing multiple threads. You’ve probably heard the term multithreading at some point, yes? A thread is really short for thread of execution, and it’s how a running process splits tasks across resources on the system. In this chapter, you’ll get a much deeper understanding of what Dispatch queue and Threads are, and how to best incorporate them in your development workflow. Dispatch queues and threads have been mentioned a couple of times now, and you’re probably wondering what they are at this point.
