---
url: /foundations/content-design/notifications.md
description: Notifications help people see information they need or want at the right time
---

# Notifications

Notifications help people see information they need or want at the right time

![Notifications](/assets/fa64e927-mrodh0vv-content-design.DUdcngLP.webp)

Notifications should:

* Be about the user, not the product
* Be precise, timely, actionable, contextual, and relevant
* Give users easy controls to opt out
* Not be used to send unsolicited ads

![](/assets/c1b62b6d-lw53k6lt-1.B9TX4eZ0.webp)

### Put important information at the top

Put the most important info at the beginning and make it easy to understand. People skim rather than read, often in an F shape. When it makes sense, try to move the most critical information to the front of sentences, rather than the end, where it may get overlooked or truncated.

::: tip Do
![Three notifications from Google apps that include the point of the notification in the header.](/assets/529ae2e8-lw53kfhk-2.Cw3XvqwD.webp)

Prioritize the most important information
:::

::: danger Don't
![Three notifications from Google apps that include app names repeated in the header, instead of important information.](/assets/96193b38-lw53kk0k-3.Bsl2QBXw.webp)

Don't waste characters on app names, niceties, or unimportant information
:::

### Tell users what they can do

If you’re prompting someone to take action, make that clear. CTAs should be concise, specific, and actionable. If you know what motivates people to take action, add it. <br>

::: tip Do
![Two notifications from Google maps that include actionable information in the header.](/assets/38ef0b22-lw53kq5j-4.DabM4cwv.webp)

Clearly guide the user to their next action

<br>
:::

::: danger Don't
![Two notifications from Google apps with non-actionable headers.](/assets/4058dbb7-lw53kvqx-5.BffggmcX.webp)

Don't bury next steps
:::

### Make it relevant and personal

A notification shouldn’t be sent to everyone. The more you broaden the audience and the message for a notification, the more you risk being irrelevant. Consider user segments, in-app behavior, and personalized information to make sure notifications go to people who will benefit most from them.

::: tip Do
![A Google maps notification in Memphis, TN that’s personalized to the user’s location downtown.](/assets/fb20b136-lw53l2ot-6.RKkaSqKO.webp)

Be specific to capture user attention
:::

::: danger Don't
![A Google maps notification in Memphis, TN that’s generic to the city, rather than the area.](/assets/b9eaff77-lw53l86v-7.CEfLZqJ7.webp)

Don’t be so generic as to lose value
:::

### Avoid dynamic text

Dynamic text are words that are implemented by engineering to change based on the user or context, like adding a user’s campaign name to headline or “good afternoon” when users log in at certain times.<br><br>Try not to use dynamic text in notifications. It often breaks character limits, especially in headlines when translated. Text that gets truncated in the headline will not expand, even in expandable notifications. If you must use dynamic text in the headline, try to pair it with no more than one additional word. Create a backup notification that fits the character count when your primary notification won’t.

::: tip Do
![Two notifications, one with dynamic text in the body, and the other with dynamic text in the header that’s formatted to always be short.](/assets/b9bc0f99-lw53lep9-8.DONd4PTx.webp)

Place dynamic text in the notification body, where there is more space. If you place dynamic text in the title, keep it very short.
:::

::: danger Don't
![Two notifications with dynamic text in the header that’s too long and truncates.](/assets/e64554e7-lw53lk9g-9.CCM8w1S1.webp)

Don’t place dynamic text in a long notification title
:::

### Mind your characters

Stay within these suggested character counts so text doesn’t get cut off:

* Title: <29 chars
* Collapsed body: <40 chars
* Expanded  body: <80 chars; start with collapsed body and add to it
* Button: 1-2 buttons (1-2 words each)

<br>There’s more room for text on later versions of Android, but these limits are still recommended to prevent truncation on smaller devices.

::: tip Do
![A short, relevant, and informative notification.](/assets/1e96faad-lw53ls3l-10.CGIqo5ox.webp)

Keep notifications short and information-dense
:::

### SMS messages

SMS helps users get messages when they might not have access to their Google Account. It’s used for important or urgent communication only. <br><br>SMS breaks into multiple messages after a certain number of characters, resulting in increased costs. To avoid this, stick to the following character limits:

* Latin languages:  <160 characters
* Non-latin languages: <134 characters

<br>If translation is needed, let translators know about the character limits in the message description.

::: tip Do
![An SMS notification that’s brief and truncates sensitive information.](/assets/23783a07-lw53lzfr-11.hmHy4HVN.webp)

SMS messages should be brief and important
:::

::: danger Don't
![An SMS notification that’s too long with too many links.](/assets/4840ddd2-lw53m528-12.DsQ_nUJR.webp)

Don’t use full emails or website links for text length
:::

### Emoji with caution

Use emoji sparingly. Many don’t translate and aren’t universally understood across cultures. Experiments show that face and hand gesture emoji perform better than generic emoji because they tell a better story. Emoji should enhance content, not replace it.<br><br>Since it’s not clear to users whether emoji mean we’re sympathizing with them or attempting to project our feelings onto them, don’t use emoji to accentuate bad news. In experiments, there was a strong negative reaction to negative emoji, such as frowning face, anguished face, and weary face.<br><br>Gen Z adds another cultural nuance to emoji by [inventing new meanings](https://www.textnow.com/blog/the-next-generation-of-emojis-gen-z-explained/) that go beyond the official or literal [definitions](https://emojipedia.org/).

::: tip Do
![A notification about coffee with a coffee emoji at the end of the header.](/assets/2e5f1286-lw53mcby-13.CtcSQb59.webp)

Use emoji only to enhance a message
:::

::: danger Don't
![A notification about high traffic volume on a route to work that uses upset emoji. A notification about coffee that substitutes a coffee emoji for the word “coffee.”](/assets/967a4383-lw53mhmr-14.D-6EBd7t.webp)

Don’t add negative emotions to a message. Don’t replace words with emoji.
:::

### Don’t overdo delight

What seems funny or cute may not come across that way. When vying for limited user attention, be useful. Don’t focus on delight: delicately added and tested polish can better support Google’s brand.

::: tip Do
![A notification that’s short and effective](/assets/1aed18ea-lw53mqhm-15.CDUxcc6E.webp)

Prioritize straightforward and useful messages

<br>
:::

::: danger Don't
![A notification that’s meant to be funny, but comes across as creepy where the application calls the user “human.”](/assets/26cd3621-lw53mx58-16.BzwVh2Q8.webp)

Jokes aren’t appropriate for notifications
:::

### Be day-specific

Use the days of the week. Don’t use “today,” “tomorrow,” “tonight,” or similar words. About 20% of users don’t see notifications on the day they’re sent, so “tomorrow” might be read when it’s “today” for the user.<br><br>An exception is when a notification auto-dismisses at a specific timestamp.

::: tip Do
![](/assets/8ca796fd-lw53n553-17.CtjEGM9K.webp)

Specify the day of the week so that it makes sense if someone reads it the following day
:::

::: danger Don't
![](/assets/492b977c-lw53nb80-18.C0Tjg-lv.webp)

Don’t use relative terms like “today” or “tomorrow”
:::

### Don’t interrupt the flow

If you have notifications or emails related to the onboarding process, make sure they don’t trigger during onboarding.

::: danger Don't
![](/assets/c9b27ca6-lw53nkf2-19.D7Py2Fi_.webp)

Don't prompt the user with a notification or email that might interrupt an important moment
:::

### Don’t name the product (again)

An app’s name or logo is already included in a notification’s design. Use the limited space for other information.

::: tip Do
![](/assets/1bf5c8b9-lw53ntem-20.BPB5QGBu.webp)

Use the available space for useful information
:::

::: danger Don't
![](/assets/5fb40a8c-lw53nz6w-21.D_I_K3Yq.webp)

Don’t waste space repeating information that is already included by the OS
:::

### Opting in and out

Give users a way to opt-out of notifications in context. If you don’t, they’ll have to dig into settings and may get frustrated. If you do offer opt-outs or opt-ins, make it clear what benefit the user is getting or losing.

::: tip Do
![](/assets/8370f28f-lw53o6jr-22.BQw3x03Y.webp)

Make it easy for users to start or stop receiving notifications
:::
