Designing for the time between sessions
By Imran Sheikh · 2026-11-12 · Product design · 4 min read
Key points
- The gap between sessions is part of the product.
- Earn each notification with something the user can use now.
- Design the return screen for someone who forgot where they were.
We design screens as if the user is always looking at them. In reality a person spends a few minutes in an app and many hours somewhere else. The time between sessions is where they decide whether to come back.
That gap deserves design attention. It includes the home screen icon, the notification, the widget and the first ten seconds of the next visit. Here is how we approach each.
Map what happens while the app is closed
Draw a timeline of one user’s week. Mark each time they open the app and each time something from the app reaches them without opening it. Most products find the second group nearly empty, or filled with generic reminders.
Then ask what the user’s life is doing in the gaps. A prayer-times app lives in the rhythm of a day. A cozy puzzle game lives in spare minutes on a couch. An arcade game lives in the wait for a bus. A health companion lives next to meals, sleep and appointments. The product should meet people where their time already runs.
This map tells you which touchpoints to build and which to skip. Not every app needs a notification. Some need only a good icon and a clear first screen.
Talk to a few real users about their day. Ask when they last thought of your app without opening it. The answers will surprise you and will give you better ideas than a brainstorm in a meeting room.
Earn every notification
A notification borrows attention. Spend it only when you can hand something back. The test is simple. Would the user be glad they received it, right now, if they read it once?
- Tie it to a time or event the user cares about.
- Say the useful thing in the first line, not a teaser.
- Let the user choose which kinds they get.
- Stop sending when the user stops responding.
- Never use it to report that you miss them.
Give users fine control. Separate settings for each kind of message cost little to build and prevent the all-or-nothing choice that ends with the whole channel switched off. Provide a quiet period as a default for anything that could arrive at night.
Write notification copy the way you would write a message to a friend. Short, specific and calm. Put the name or the number in the first words. A message that says your next prayer time is at 5:42 is more useful than one that says time to check in.
Put value where the user already looks
The best touchpoint between sessions needs no app launch. A widget, a lock screen element or a live activity can give the answer straight away. A user who sees the next prayer time, the current streak or today’s plan at a glance has used your product without opening it.
Design these surfaces as small, finished products. One idea each. Readable at a glance in bright light. Tap targets that open the app to the right place instead of the front door. A widget that opens the home screen of the app wastes the best moment it earned.
Remember that a widget lives next to many others. It competes with the weather, the calendar and the user’s photos. Give it a clear purpose and a quiet visual style, and let the content carry it. Test it in both themes and at every size you support, since a layout that fits a medium widget can break in a small one.
The best reminder is the answer, shown at the moment the question comes up.
Design the return screen for someone who forgot
The user who returns after three days is not the user who left. They have forgotten where they were. They may not remember what the app does in detail. The first screen should orient them quickly.
Show the state of things in plain words. What is new since last time. What is waiting. What they were in the middle of. Offer one clear way to continue, and put the rest one tap away. Restore their place, because making someone find their position again is the most common reason a return visit ends early.
Handle long absences gracefully. After a few weeks, a welcome back screen with a short summary and a fresh start option is kinder than a pile of overdue tasks. Do not shame the user for the gap.
Return paths include links as well. A notification, a widget tap and a shared link should each land on the right screen, with the app already in the right state. A broken deep link wastes the entire effort that got the user there.
Respect the cost of re-entry
Every time the user returns, they pay a small cost to get back into context. Lower that cost where you can. Keep launch fast. Keep state when the system closes the app in the background. Avoid sign-in prompts and update banners at the door.
Test this the way a real person lives. Open the app after a night’s sleep, on a bad connection, with a notification as the entry point. Many bugs and rough edges appear only in these paths, and they are where retention is won or lost.
Measure the gap, not just the session
Standard analytics focus on what happens inside a session. Add a few signals about the gap. How long between visits. Which entry point brought the user back. Which touchpoints are switched off. Use the answers to decide what to build next, and keep the product respectful of a person’s time.