Summary
In short, mobile applications should not be designed to undertake long-running tasks on the user interaction tier, but rather user asynchronous mechanisms to execute these workflows. The UI, in this case, would just be responsible for keeping the user informed about the background execution status. While in the past, background tasks were handled through classic .NET threading model, nowadays, the TAP model provides a rich set of functionality, which releases the developers from the burden of creating, managing, and synchronizing the threads and thread pools. In this chapter, we have seen that there are various patterns that would allow for the creation of background tasks that would yield back to the UI thread so that the asynchronous ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access