Guidance for designing component-owned loading, empty, error, auth, permission, and gated states so UI surfaces own their state shape while screens stay focused on orchestration.
-
Updated
Jun 21, 2026
Guidance for designing component-owned loading, empty, error, auth, permission, and gated states so UI surfaces own their state shape while screens stay focused on orchestration.
Add a description, image, and links to the ui-states topic page so that developers can more easily learn about it.
To associate your repository with the ui-states topic, visit your repo's landing page and select "manage topics."