Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
Cancel obsolete work where possible and accept a response only if it still matches the current query or request generation. Debouncing reduces work but does not guarantee correct ordering.
Assign each search a query identity or monotonically increasing generation. Before updating the screen, compare the response with the active request. Cancellation helps save resources, but callbacks may still arrive or work may complete before cancellation is observed. Debounce rapid typing if appropriate, scope work to the screen lifetime, and test responses arriving out of order. Keep loading and error state associated with the same active request.