# Reminders: Send the Right Nudge at the Right Moment

> A good reminder brings someone back to an action they already meant to take. Learn when to send it, where, how often, and how to keep it from turning into noise.

**In short:** A reminder brings someone back to an action they already meant to take. It works best when it is well timed, gives one clear step and does not turn into noise.

From "UI/UX basics", a free course by Venkat R. Murty: https://designervenkat.online/learn/ui-ux/reminders

## What you will learn

A reminder is a short message that brings a person back to something they already planned to do. It can be a phone push, an email, a message inside the app, or a visual cue such as a badge or a counter on the screen. A reminder is useful when it helps. It is harmful when it nags. This lesson shows you how to time a reminder, pick its channel, control how often it appears, and make it personal without becoming annoying.

- **Reminder:** A message that calls a person back to an action they already intended to take.
- **Push notification:** A message that appears on a phone or computer even when the app is closed. It comes from the app's server.
- **In-app nudge:** A message or visual cue shown only while the person is using the app, such as a banner or a highlighted button.
- **Channel:** The route a message travels, such as push, email, text message, or in-app.
- **Trigger:** The event or moment that makes a reminder fire, such as a usual time of day, a location, or an unfinished task.
- **Frequency:** How often a person receives a reminder over a day or a week.
- **Opt-out:** A way for a person to turn off a type of message, or all messages, for good.
- **Snooze:** A way to pause a reminder for a short time and be asked again later.
- **Streak:** A count of days in a row that a person has done something, such as a daily lesson.
- **Behavior design:** The craft of shaping a product so people more often do the thing they want to do.

Reminders are one part of behavior design. In this course, they follow one rule: the right message, at the right moment, through the right channel.

## What makes a reminder work?

Three choices decide whether a reminder helps or annoys. Each one is covered in its own part of this lesson.

- **Timing and context:** The reminder must arrive when the person can act on it. The same message at a bad moment is ignored or resented.
- **Channel and frequency:** The route and the number of messages should match how urgent the task is and how much attention the person has to give. Users need controls to shape both.
- **Relevance and a personal touch:** The message should point to something the person really started or said they wanted. It should stop when the task is done or when the person keeps ignoring it.

## Why do timing and context decide everything?

Timing is often more important than the words in the message. Guides on notification design say the right notification sent at the wrong time can easily be ignored. A reminder sent too early gets forgotten, and one sent too late is no longer useful. Both problems are common, and the cure is to send the reminder when a decision can still be made.

### Send it when the user can act

A reminder works best when it is tied to a trigger. A trigger can be a time that the person usually studies or shops, a location they often visit, or an unfinished task they left in the app. Another good trigger is a deadline that is still far enough away that the person can do something about it. Some guides suggest a layered approach: send a first, early reminder, and add a second, closer reminder only if the task still matters.

Context also includes what the person is doing. A reminder that pops up in the middle of focused work is a distraction, even if the message is well written. The question to ask is whether the person can receive the message and act on it right now.

> **Tip:** Before you set a reminder time, ask: if this person saw the message right now, could they finish the task in a minute or two? If the answer is no, move the reminder to a better moment.

### Why give one clear next step?

- **Name the action:** Say the one thing the person should do, in plain words. A reminder that says 'Check in' is weaker than one that says 'Finish today's lesson'.
- **Link to the right screen:** Make the reminder open the exact screen where the action happens. Sending people to the home screen to hunt for their task wastes their time and their patience.
- **Skip the detours:** Avoid extra steps between the message and the action. Notification guides note that people want to save time, so a single tap that goes straight to the task is the ideal.

One clear step gives the reminder a purpose. A message with several choices, several links, or a long story makes the person stop and think, and many people will simply swipe it away.

## How do you choose the channel and frequency?

The channel is the route your message takes. A push notification can reach a person even when the app is closed. An in-app nudge only appears while the person is inside the product. An email can wait in an inbox, and a text message feels personal and immediate. Each channel has a different level of interruption, so the choice should follow how urgent the reminder is.

### How do you match the channel to the urgency?

Design guides say you should be honest about how urgent each message is. Apple's guidance asks designers to assign an interruption level that matches reality, because people can turn off notifications from an app altogether if too many feel urgent. In practice, a low-urgency reminder can be an in-app nudge that waits for the person to open the app. A time-sensitive reminder, such as one that protects a streak or a deadline that is close, can use a push. A slow planning task can go by email. Reserve the most interrupting channels for the few messages that truly need them.

> **Tip:** Ask yourself which channel would still feel fair if the person saw the message an hour late. If the answer is yes, a quieter channel is probably the right choice.

### Why give users control?

Reminders become spam when people have no say over them. Good designs give users control over how the reminder behaves, and they make that control easy to find.

- **Snooze:** Let the person pause a reminder for a while. A snooze lets them keep a task without being interrupted right now.
- **Frequency settings:** Offer choices for how often reminders come, so someone who wants a gentle nudge can have one and someone who wants more can ask for it.
- **Type-by-type settings:** Separate reminders into groups, so a user can keep the ones they want and turn off the rest. One vendor report says that detailed preference controls can cut unsubscribes without reducing how many messages are sent, though the figures come from a single blog and should be read with care.
- **Easy opt-out:** Make it simple to turn a reminder off completely. Hidden or buried switches make people feel trapped, and trapped people often delete the app.

Permission matters too. On Apple's platforms, an app must get the person's consent before it sends notifications at all. Guidance for promotional messages goes further and asks for clear, explicit permission and a simple way to opt in or out.

## How do you make the reminder relevant and personal?

A reminder feels helpful when it seems to know the person. A message that refers to what they actually did, or what they told the product they wanted, feels like a helpful friend. A generic message that could be sent to anyone feels like advertising. The next three parts cover how to make the message personal, keep it brief, and stop when it stops being useful.

### Reference what they started

Use details from the person's own activity. If someone began a lesson, name the lesson. If someone has a streak, name the streak. If someone saved an item in a shopping app, name the item. These details remind people of progress they have already made, so returning feels like continuing rather than starting over. Keep the reference accurate. A message that names the wrong item or the wrong number quickly loses trust.

> **Tip:** Use the person's real data for the message, but keep private details out of lock-screen previews. Someone else may see the message on a shared device.

### Keep it short, friendly, and useful

Notification guides agree that a message should be brief and easy to read at a glance. One guide suggests keeping push text to roughly 120 to 150 characters so it stays readable in both the short and long views. Apple's guidance says people turn on notifications to get quick updates, so each message should carry real value in a few words.

A friendly tone helps, but it should not become a guilt trip. A reminder can say what the person gains, such as keeping a streak alive or finishing a short lesson. Teardowns of popular apps note that guilt-based messages can backfire. One article says that pushes built on negative reinforcement saw higher opt-out rates, and the product team softened its tone for that reason.

### When should you stop or adapt?

- **Stop when the task is done:** If the person has completed the action, the reminder should end. Sending a reminder about a finished task is the fastest way to look careless.
- **Avoid duplicates:** Apple's guidance says to avoid sending several notifications about the same thing, even when the person has not answered. Several copies fill up the notification list and push people to turn everything off.
- **Adapt to silence:** If someone keeps ignoring a reminder, slow down. Send fewer, or switch to a quieter channel, or pause for a while. One set of teardown notes describes a pattern of one main reminder, one backup, and then a cooldown period if the person still does not respond.

## Worked example: Duolingo's daily practice push

Duolingo is a language app with a daily practice goal. Its practice push is a good example because it uses the ideas above together. Duolingo does not publish all of its rules, so the steps below come from the teardown pages and sample messages I read. Treat them as a reading of the design, not as official documentation.

1. **Find the usual study time:** One teardown describes the system reading a learner's habit window. If the learner practised at 6 pm yesterday, the push for today fires a little before 6 pm, not at a time set by the company. The reminder comes when the learner is most likely to be free.
2. **Send a separate save reminder late:** Duolingo also sends a last-chance message when a streak is at risk of breaking before midnight. The regular daily push and the late save push have different jobs, so each one is kept for its own moment.
3. **Name the streak:** Duolingo's own sample messages mention the learner's streak count and tell them not to lose it. Naming a real number makes the reminder specific. The learner sees exactly what is at stake and what has already been built.
4. **Open straight into the lesson:** The goal, as one teardown describes it, is a quick win: one tap opens one lesson, and the streak is saved. The reminder ends at the next lesson, not at a home screen.
5. **Adjust if the learner ignores it:** Duolingo has a Reminder Intensity setting that lets people choose how often they are nudged, and it has reduced push frequency for long-time users. One teardown describes a main reminder, a single backup, and then a cooldown if the person still does not respond. Some users reported feeling guilt-tripped, so the team moved toward playful, character-based messages.

What can you copy from this example? Use the person's own habit window for timing. Name the real progress they have made. Give one tap that leads to the task. Then give the person control over how often the reminder appears, and slow down when they are not responding.

## Common mistakes

- **Sending the same message to everyone at the same time:** A single fixed time ignores when each person actually has free time. Use each person's habit or the moment the task is due instead.
- **Sending many messages about one thing:** Repeated messages about the same task fill the notification list and push people to switch off the whole app. Send one well-timed message, then pause.
- **Hiding the opt-out:** If people cannot find a way to snooze or turn off a reminder, they will often turn off everything or delete the app instead.
- **Using guilt as the main tool:** A message that scolds the person can work once, but it tends to make people resent the product. Warm, useful messages hold attention for longer.
- **Ignoring how the reminder performs:** Do not assume that a schedule works. Watch how many people turn off reminders, and change the timing or frequency when opt-outs rise. A small trial on a stress app found that frequent reminders did not always push people away, and that smart timing did not always help, so measure instead of guessing.

## Check your understanding

Try these two short scenarios. Each one needs the ideas in this lesson to answer.

**Quick check:** A fitness app sends every user the same 'Time to work out!' push at 9 a.m. every day. Many users have turned notifications off. Which two changes would you make, and why?

A. Send the same message at 9 a.m. but add a second push every afternoon so people cannot miss it.
B. Send each reminder at the time that user usually trains, name the workout plan they set, and let people choose how often they get reminders and snooze them.
C. Keep the 9 a.m. push but write it in capital letters so it stands out more.
D. Turn off reminders for everyone and send a weekly email summary instead.

**Answer:** B. The fix has two parts. Timing should follow each person's habit, so the reminder arrives when they can act. Relevance and control should follow, so the message names their own plan and they can adjust how often it comes. More messages or louder ones would add to the noise that made people switch off.

**Quick check:** A bill-paying app sends every user a push, an email, and a text on the morning a bill is due. Many users feel pestered, and some have deleted the app. Which change fits the lessons in this part of the course best?

A. Keep all three channels and repeat them every hour until the bill is paid.
B. Send one push a few days before the due date that opens the payment screen, and stop once the bill is paid.
C. Send only an email the day after the bill is due, with a warning in bold red text.
D. Remove the reminder and show a large red warning on the home screen all day.

**Answer:** B. A few days before the due date, the person still has time to act, and one message is enough. The push leads straight to the payment screen, which gives one clear next step. Stopping once the bill is paid respects the person's action. The other options either add noise, arrive too late, or keep the person in a constant state of alarm.

> **Tip:** Summary: a good reminder arrives when the person can act, uses the channel that fits its urgency, names what the person actually started, gives one clear next step, and gives the person control. When they act, it stops. When they keep ignoring it, it slows down.

## Sources

- [OneThing Design: 10 Best Practices for Push Notification UX Design](https://www.onething.design/post/best-practices-for-push-notification-ux-design)
- [SetProduct: Notifications UI design, why most apps annoy users](https://www.setproduct.com/blog/notifications-ui-design)
- [Figr: UI Notification Examples and UX Design Patterns](https://figr.design/blog/ui-notification-examples-ux-design)
- [AONMeetings: Reminder Notifications, The Practical Guide for 2026](https://aonmeetings.com/reminder-notifications/)
- [Techgenyz: Notification UX, Reduce Fatigue and Improve Engagement](https://techgenyz.com/notification-ux-best-practices/)
- [ExtPower: Push Notifications That Users Don't Turn Off](https://extpower.dev/blog/push-notifications-that-users-don-t-turn-off)
- [PLOS ONE study via PMC: Effect of Timing and Frequency of Push Notifications on a Stress Management App](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5207732/)
- [Apple Developer: Human Interface Guidelines, Notifications](https://developer.apple.com/design/human-interface-guidelines/components/system-experiences/notifications/)
- [Apple HIG v15 summary: Managing notifications](https://developerguidelines.com/human-interface-guidelines/version/15/managing-notifications/)
- [Apple HIG v15 summary: Notifications](https://developerguidelines.com/human-interface-guidelines/version/15/notifications/)
- [Apple WWDC17: Rich Notifications talk](https://developer.apple.com/videos/play/wwdc2017/817)
- [OneSignal: Apple Push Notification Best Practices](https://onesignal.com/blog/apple-push-notification-best-practices/)
- [Deconstructor of Fun: Duolingo Push Notifications teardown](https://duolingo.deconstructoroffun.com/mechanics/notifications)
- [Deconstructor of Fun: Duolingo Streaks teardown](https://duolingo.deconstructoroffun.com/mechanics/streaks)
- [Duolingo: Push promotional page with sample messages](https://www.push.duolingo.com/)
- [DontSnooze: A Teardown of Duolingo's Streak Notifications](https://dontsnooze.io/blog/duolingo-guilt-notification-teardown/)
- [PushPilot: Breaking Down Duolingo's Push Notification Strategy](https://pushpilot.ai/blog/duolingo-push-notification-strategy-teardown)
- [Apptitude: App Teardown, How Duolingo's Streak Mechanic Actually Works](https://apptitude.io/blog/how-duolingos-streak-mechanic-actually-works/)
- [Medium: The UX of Notifications, Helpful or Harmful?](https://medium.com/@blessingokpala/the-ux-of-notifications-helpful-or-harmful-cf9b1fe8e4fe)
