Designing for the return visit: the principle every product should start from

The first visit to a digital product is the easiest to design for. You have the user's full attention, expectations are low, and curiosity carries the experience. The second visit is where most products start to lose people. The third visit determines whether you've built a product or a curiosity.

At Livewall, we start every digital product and loyalty experience with the same question: why would someone come back here? Not because of a push notification, a discount, or a habit they already had. On their own initiative, because the product delivers something they can't find anywhere else.

That's a different design question from the one most teams ask themselves. Most attention goes to onboarding, activation, and conversion. The return visit, the repeating behavior, is usually treated as the outcome of good content or solid CRM. But it's a design decision first.

Three reasons people come back

We see three patterns in practice that explain repeating visits. They're not mutually exclusive, and the strongest products always combine at least two of them.

1. New information or a changed state The user expects something has changed. A leaderboard, a new episode, a result that wasn't there yesterday. This is the principle behind daily games, advent calendars, and progress tracking. For Rituals The Advent Diorama 2025 we built an experience that was new every day, even if the user had already visited the day before. The rhythm of return was built into the structure itself.

2. Unfinished tasks and open loops People return to things they haven't completed. Not because of discipline but because of the mental tension of an open loop. A level almost beaten, a collection nearly complete, a challenge just out of reach. HEMA Stapelgek used this principle by connecting purchases to a visual collecting mechanic. Visiting the app became part of the habit around buying, not separate from it.

3. Social connection and shared context When a product connects you to others, returning stops being a choice and becomes a social pull. That's why people open WhatsApp, LinkedIn, or their sports app every day. The platform for Sportvisunie worked because it connected anglers to a community that only existed there. The knowledge, the stories, the reactions were unavailable anywhere else.

Design starts with the behavior, not the feature

The most common mistake we see: teams design a feature and then hope users find a reason to come back. It rarely works. The return visit must be designed first, not as an afterthought.

In practice, that means naming the behavior before you start designing. Not "users should return regularly" but "users open the app every Friday to check their weekly results" or "users come back after a purchase to place their stamp".

Once that behavior is clear, you can design backwards from it. What information needs to be ready for them? What progress should be visible? What social signals trigger the return?

For Decathlon's always-on loyalty program, the entire experience is built around daily movement. The return visit wasn't conceived as a program feature. It's the core of the value proposition. People come back because the product reflects their activity pattern, not because they want a reward.

Loyalty is a design problem, not a marketing problem

Most brands treat retention as a CRM challenge. Send an email when someone's been away for two weeks. Offer a discount when they're about to lapse. Set a reminder.

That works temporarily. But it treats the symptom, not the cause. The cause is almost always that the product itself gives no reason to return.

Gamified loyalty works not because people love games, but because game mechanics build return behavior into the structure of the product. A daily challenge, a progress bar nearly full, a collection waiting to be completed. These aren't tricks. They're design decisions that create a reason.

The same applies to the loyalty platforms we build. The technical architecture isn't the point. The question is: what does a user see when they come back after three days? Is there something new? Something they missed? Something that reflects their behavior?

UX that removes friction versus UX that pulls people back

There's a difference between UX that removes friction and UX that actively pulls people back. Most UX/UI design work focuses on the former. Eliminate friction, optimise flow, increase conversion. That's valuable. But a frictionless experience with no reason to return is just a fast exit.

UX that pulls people back gives users a sense of progress, of unfinished business, of something waiting for them. It doesn't have to be large. An unread notification, a profile nearly complete, a leaderboard updated every week. Small signals that communicate: there is a reason to come back.

This is also why at Livewall we always start with one question: what is the reason for the second visit? Not the hundredth, not the fifteenth. The second. Because once you have that answer, the rest follows from it.