Async patterns
Every async operation in a screen is one of four shapes, and each has a hook built for it. Picking the right one is the difference between two lines and a tangle of useState flags.
FutureBuilder alternative for Flutter hooks
Use computed state hooks as a FutureBuilder alternative for loading, retry, refresh, gated reads, and async values in Flutter.
Submit state
A mutation - save, delete, send, log in - has a lifecycle the UI has to track
Flutter infinite scroll and pagination with hooks
Build cursor, page, token, pull-to-refresh, and infinite-scroll lists in Flutter with usePaginatedComputedState and PaginatedComputedStateWrapper.
Error handling
The async hooks share one rule: let errors crash by default. A useSubmitState.run rethrows; a failed useAutoComputedState lands its error in value and propagates the auto-load failure too. None of them swallow. That sounds reckless until you see where the crash lands - an app-root catcher that reports every uncaught error and surfaces it as a retryable dialog. The job of error handling is to build that catcher once, then get out of the way.