Why `isLoading` Breaks Down in Complex React Apps

A cleaner pattern for preventing duplicate submits, blocking conflicting actions, and coordinating async workflows across React components. For a small component, a local isLoading flag is usually fine. A button starts a request, disables itself, shows a spinner, and then goes back to normal when the request finishes. Simple and easy to reason about. But that simplicity rarely survives contact with a real application. The moment an async action starts affecting more than one component , isLoadin