สถานะกำลังโหลดและข้อผิดพลาด

A real request moves through states: loading, success, and failure. Showing each one makes your app feel trustworthy. 🔄

An enum captures each phase cleanly. The view then switches on it to decide exactly what to display.

While loading, show a ProgressView. This native spinner reassures users that something is happening behind the scenes.

Use a switch in your body to render a spinner, the data, or an error view based on the current phase.

Wrap the fetch in do/catch and move to the failed phase on error, storing a friendly message for the screen.

Avoid raw error text. Show a clear sentence the user understands, like "Check your connection and try again."

On failure, add a retry button that runs the fetch again. Letting users recover beats a dead-end error screen.

Success with no data deserves its own empty view, like "No results yet", so the screen never looks broken.

Move to the loading phase before awaiting. That instantly shows the spinner so the screen never feels frozen.

For very fast responses, a tiny delay before hiding the spinner prevents a jarring flash of loading UI.

Kick off the whole flow from .task, which sets loading, fetches, and lands on loaded or failed automatically.

You now model fetches as loading, loaded, and failed, show a spinner and friendly errors with retry, and drive it all from .task. 🎯