You're asked to build, without third parties, a screen that calls a server search API on every keystroke in a search bar and refreshes the results list. How would you solve the problems a fast typist causes, using async/await?
A request goes out per keystroke and requests that are no longer needed go to waste. On every input, cancel the previous Task, sleep briefly as a debounce, then request.
ConcurrencyShort answerBasics
Calling the API on every keystroke in a search field floods it with requests. Can you…
#search #debounce
SwiftUIShort answerAdvanced
You're building a Combine pipeline for a SwiftUI search screen that calls the API as the…
#search #debounce
iOS system designShort answerBasics
Design the search screen of a music app: autocomplete while typing, a results list, and…
#search #debounce
NetworkingShort answerBasics
The legacy code has a function that waits on a URLSession response with DispatchSemaphore…
#async-await