Patterns and safety
Apply IPEX to forms, operational data, feedback, and consequential writes.
Use the component recipes within a workflow that explains the task, its impact, and the result. Match page composition to the layout archetype before choosing local spacing.
Forms and setup
Keep labels visible and place helper text near the field. Explain consequences in language the person can act on. Validate on blur or submit unless immediate validation improves the task; avoid showing errors while someone is still entering a valid value.
Group related settings. Keep numeric steppers and fields planar. In authentication or onboarding, allow enough space around the focal surface to support trust and comprehension.
Operational data
Keep text aligned for scanning and quantities aligned for comparison. Preserve column widths during loading. Keep sorting, filtering, selection, pagination, and row actions predictable.
Show selected counts and place bulk actions near their affected records. Use an explicit review when the action changes a broad set of data. Group related dashboard metrics within a moderate composition width.
Drag and drop
Use a quiet idle region, info color for a valid target, and destructive feedback for an invalid target. Make the active destination clear while dragging. Offer a keyboard path to the same action and confirm completion.
Feedback and recovery
| Situation | Response |
|---|---|
| A region is loading | Match the final geometry and keep unrelated work available. |
| An action is processing | Keep its dimensions stable and prevent duplicate writes. |
| A view is empty | Explain the condition and provide one useful next action. |
| Work completes | Confirm the result through status text or a notification. |
| Work fails | Say what failed, what it affected, and how to recover. |
| Some records fail | Report success and failure counts, identify the failed records, and support retrying those records. |
Use semantic colors according to Color. A lifecycle label such as Queued or Cancelled can remain neutral.
Confirmation by impact
For a low-risk reversible change, prefer execution with reliable undo. For a broad reversible operation, show the affected count and a review when useful. Require impact confirmation for destructive, hard-to-reverse, external, financial, legal, tax, or irreversible actions.
A consequential confirmation should make the affected count, old/new differences, impact, Cancel action, and final execution action visible. Offer backup or export when appropriate. After execution, show progress and a recovery path for failures.
Use direct consequence statements, such as “This will overwrite 238 existing barcodes.” Keep the destructive effect clear before the final action.
Review a screen
Check its working width, resting visual weight, control density, selected states, focus, loading geometry, mobile flow, and recovery messages. Use real product data when evaluating operational screens. Keep demos identifiable as examples.