A nudge directs users to take an action on something that might be relevant at the time they see it.
Use a nudge:
- to suggest a new feature or action that a user might not be aware of
- if there's an optional feature or action that's relevant to what the user is currently doing
Don't use a nudge:
- if the information is critical, or requires time sensitive action
- if the feature is something that everyone needs
- if there's no action for the user to take
There are 7 different variants of nudge, each with a different illustration.
Place a nudge at the top of the screen or section it applies to, or below a section header.
Never have more than one nudge on the same screen.
Nudges direct users to another view to complete an action.
Tapping anywhere on the nudge triggers the action — except for the area around the close button, which dismisses it.
Title
Title copy should:
start with a verb
describe the action the user might like to take
include a clear benefit for the user — like making something quicker, safer, or cheaper for them
be short (4–7 words)
capitalise the first letter of the first word
not have a full stop
If you can't fit the action and the benefit in one sentence, you can include a second sentence. Just make sure it:
explains the benefit to the user
includes full stops as there are 2 sentences
is short — no more than 6 words
Action
Action copy should:
start with a verb — like ‘add’, ‘enable’, ‘find’
describe a specific action the user will take — it shouldn't be vague
be no more than 3 words
capitalise the first letter of the first word
have no full stop
Platform | Available | Developer documentation |
|---|---|---|
Android | ||
iOS | ||
Web |