User Perception: Immediate Feedback Matters Most
You'll learn why users prefer instant visual feedback with slightly outdated data over waiting for a perfectly frozen UI to update.
The Psychology of Waiting
When a user types in a search box or clicks a button, their brain expects immediate acknowledgment. Even if your app needs 500ms to compute results, showing something instantly—even if it's the old results marked as "loading"—feels dramatically faster than a frozen UI.
Think of it like ordering at a restaurant: Would you rather have the waiter say "Got it, your order is being prepared" immediately, or stand there in silence for two minutes wondering if they heard you? The first scenario feels responsive even though the food takes the same time to arrive.
Why Stale-But-Responsive Beats Perfect-But-Frozen
React's concurrent features (like useTransition and useDeferredValue) embrace this principle. They let you:
- Show immediate feedback to user input (the input updates instantly)
- Keep the old UI visible while new data loads (users can still see and interact)
- Indicate progress with visual cues like opacity or spinners
This pattern respects human perception: we judge responsiveness by the first visible change, not the final result. A UI that responds in 50ms but completes in 500ms feels faster than one that freezes for 300ms before showing perfect results.
The Concurrent Advantage
Without concurrent features, updates block the entire UI. With them, you decouple input feedback from expensive computation. The user sees their keypress reflected immediately, maintains context with the stale data visible, and perceives the app as snappy even when the underlying work takes time.
Key Takeaway: Users judge your app's speed by immediate feedback, not total completion time. Showing instant acknowledgment with stale data beats waiting for fresh data with a frozen UI every time.