With the <error-dialog>, we provide a consistent and easily recognisable design for communicating errors back to the user.
We currently don’t have an equivalent UI for communicating success. On the one hand, that’s not as critical as failures, but on the other hand, it would be more fun and engaging for the user to always see a distinct state after their desired operations succeeded.
Here is a quick-and-dirty layout mockup:
Features:
Green top border (equivalent to the red one of the error dialog)
A slightly green-ish background color
A big checkmark icon (not sure about that, though)
With the
<error-dialog>
, we provide a consistent and easily recognisable design for communicating errors back to the user.We currently don’t have an equivalent UI for communicating success. On the one hand, that’s not as critical as failures, but on the other hand, it would be more fun and engaging for the user to always see a distinct state after their desired operations succeeded.
Here is a quick-and-dirty layout mockup:
Features:
Related https://github.com/tiny-pilot/tinypilot/issues/714.