Buttons are used to initialize an action.
Button labels express what action will occur when the user interacts with it.
For buttons, we use 3 major factors – that we can mix in between to produce any kind of call to actions depends on its hierarchy.
and here we will express this three factors in details.
We use only two weights of buttons, normal, small. and that goes across all the types of the buttons (primary,
secondary, circle). we will express them in details.
NOTE: During the samples of button’s weights, we will use any color, and any type. but it
does not represent a guideline. buttons types already covered. and colors guidelines of buttons will be covered
There is two different status we usually use for buttons, active and disabled.
For active button status. we use colors. usually, CTA buttons come in the brand color (check this link for more about
primary brand color). Here are some samples.
For Disabled action buttons. we use only the gry color. to unify the experience all-over the platform.
For the best experience in interactions with buttons, the response should be clearly communicated. we define three levels of interactions for buttons:
- From Disabled to Enabled.
- Hover / Click.
- Progress indication.
From Disabled to Enabled
Disabled buttons appear when there is a required information to complete a task. it will automatically convert to enabled whenever this task is completed.
Example: The user wants to reset his password. the button will be disabled till the user enter a valid ID.
Hover and Click
The Response that happens when the user starts to interact with a button on the screen. we use shadows to emphasize the action itself. and encouraging the user to take this action.
After any sort of action, the user should be aware “what is going on” – communicating with users while they have to wait is very important – and we use instantly load buttons to communicate this state clearly.