How can you turn app users into brand advocates on social media?

A user who tells their friends about your app is worth more than any paid acquisition campaign. They arrive with trust already built, convert at higher rates, and tend to stay longer. The problem is that apps typically treat advocacy as a marketing question rather than a design question, and so they try to bolt it on after the fact with referral codes and share buttons. Those mechanics rarely work on their own. Advocacy is a by-product of how the product makes people feel, and it grows from the inside out.

The gap between a satisfied user and an advocating user is almost entirely emotional by design.

The apps people genuinely talk about are the ones that give them something worth saying. That something is almost always emotional. It is a moment of surprise, a feeling of being understood, a small win that lands at exactly the right time. According to Harvard Business Review, 2015, emotionally connected customers deliver 25% to 100% greater value in revenue and profitability compared to those who are merely satisfied. The gap between a satisfied user and an advocating user is almost entirely emotional, and emotion is something you design for.

This is what we work on at WAA. Not referral schemes, not gamified share prompts, but the underlying product experience that makes someone pick up their phone and say to a friend: you need to try this. The chapters that follow lay out how that happens, what gets in the way, and what to build instead.

What does brand advocacy actually mean for apps?

Brand advocacy is when a real person, without being paid or prompted, tells someone else that your product is worth their time. For an app, that almost always happens on social media or in person, and it carries far more weight than anything your marketing team produces. Nielsen, 2024 found that 92% of consumers trust user-generated content more than branded content. That number makes sense when you think about what peer recommendation actually means: someone you know, with their reputation attached, staking a small claim on your behalf.

Advocacy vs. referrals

A referral is transactional. The user gets a discount or a free month, and they pass on a link. The friend arrives via incentive rather than genuine enthusiasm. Advocacy is different. It happens because the product created an experience the user wanted to share, and it travels as a story or a feeling rather than a promotional code. The distinction matters because referral mechanics are easy to copy and easy to ignore, while genuine advocacy is much harder to manufacture and much harder to ignore.

What advocacy looks like in practice

An advocate does not usually post a glowing review unprompted. More often they share a screenshot of a milestone, mention the app in a conversation, or post something the app helped them create or discover. The product becomes a prop in their own story. That is the design goal: build something that fits naturally into the stories people already want to tell about themselves, and they will bring your product along for the ride.

Why apps so often fail to generate word-of-mouth

The most common failure is designing for retention without designing for feeling. An app can keep users coming back through habit loops and push notifications, and those users can still feel nothing particularly positive about the experience. They use it because it is useful, not because it moves them. Useful things get used. Meaningful things get shared.

A second failure is placing the ask for advocacy in the wrong moment. Share prompts that appear right after a frustrating interaction, or rating requests that interrupt a user mid-task, associate the act of sharing with a negative emotional state. The user dismisses them and moves on. The timing of any request for engagement is as important as the request itself.

There is also a structural problem in how apps tend to think about community. They add social features as a layer on top of the core product rather than building the social dimension into the product's logic. The result is a feed or a leaderboard that nobody uses, sitting off to one side of the experience that users actually came for. Social behaviour does not grow from a dedicated social tab. It grows from shared experiences that happen to have a social context around them.

The products that generate the most word-of-mouth tend to have something in common: they make users feel something specific and positive at a moment they did not expect. That surprise is what gets repeated in conversation.

The emotional triggers that make people share

People share things that say something about who they are. This is the most reliable rule in social behaviour, and it applies directly to apps. When a user posts a running milestone, a reading streak, or a recipe they made, they are performing identity. The product is the evidence for a story they want to tell about themselves, and your job is to give them evidence worth sharing.

Pride is one of the strongest triggers. A visible achievement, a number that has moved in the right direction, a skill that has grown, all of these create a natural impulse to show someone. Closely behind pride is belonging. When an app makes a user feel part of something real, they talk about it in the same way people talk about clubs, sports teams, or local places they love. The social dimension of the experience becomes something to bring others into.

When an app makes a user feel part of something real, they talk about it the way people talk about places they love.

Surprise also drives sharing. An interaction that behaves in an unexpected, delightful way gets described to other people precisely because it broke a pattern. The user wants to recreate the moment for someone else. This is why micro-interactions and small details of craft matter: they are disproportionately likely to be the things someone mentions.

What does not tend to drive sharing is functional satisfaction. A user whose bank app processes a payment correctly does not post about it. Expectation met produces nothing shareable. Expectation exceeded, or unexpectedly met in a way that felt personal, produces the thing people repeat.

Map the emotional state of your users at each stage of their journey through the product. A user who completes an onboarding step feeling confident is in a completely different emotional place to one who finishes feeling relieved. Those two states produce very different sharing behaviours.

Designing moments worth talking about

Designing for shareability starts before any feature brief is written. It starts with understanding what your users want to feel and what they want others to know about them. The documents we produce after research debriefs include emotional arcs, maps of how users feel at each stage of their journey through a feature or product experience. These sit alongside brand personality documents to make sure that whatever is built next will feel coherent with how the brand already speaks to people. Without that foundation, shareable moments tend to be accidental rather than designed.

On the genetics wellness app, the thing that moved the needle on retention and engagement was restoring the storytelling layer. The product had been presenting data, but users were not feeling seen. When the narrative came back, when the product started speaking to users as individuals with a specific story rather than a set of data points, the experience became something people wanted to talk about. The data had not changed. The emotional register of how it was delivered had.

On the fitness social network we redesigned the location-sharing flow, we found that sequencing conversation before location disclosure, and using approximate proximity rather than precise location, changed the conversion from sign-up to successfully meeting another user from around 20% to roughly 60 to 70%. That single flow change created a fundamentally different experience of the product. Users who successfully met someone became the product's most vocal advocates, because the meeting itself was a story worth telling.

Think of your product's shareable moments as scenes in a story the user will retell. What did they do? What happened that surprised them? What did they discover about themselves? Design the scene deliberately, not as an afterthought.

How the words inside your app shape user behaviour

Copy is not decoration. The words your app uses to describe what it wants from a user shape whether the user feels like a participant or a subject. This difference has a direct effect on whether they engage generously with the product or comply minimally and move on.

The travel app reframe

We worked on a travel app where users were being asked to rate their holiday experiences. The original prompt read essentially as: rate this experience. The problem is that users psychologically assume a rating request benefits the company, so they ignore it unless they have had a negative experience and want to complain. We reframed the copy to ask: what would you tell other travellers about this? That single change shifted the user's mental model entirely. They were no longer giving feedback to a faceless business. They were helping people like themselves make better decisions. The same action, framed differently, produced a completely different emotional relationship to the task.

Words that invite versus words that extract

The principle generalises. Any moment in your app where you are asking a user to give something back, a review, a rating, a referral, a piece of content, the framing of that request determines whether the user feels like a contributor or a resource being mined. Contributor-framed copy produces more engagement and warmer sentiment. That warmth is what carries over into what users say about the product outside the app.

Audit every request your app makes of users. For each one, ask whether the copy frames the action as helping the product or helping other people. Where it is the former, try rewriting it as the latter and test whether engagement changes.

When the product should encourage people offline

Not every moment of community building happens inside an app, and designing as though it does creates a product that feels hollow. The most durable social networks in people's lives are built on knowing someone's name, recognising their face, understanding what matters to them. An app that tries to replicate all of that digitally often ends up replacing the human interaction it was meant to support.

On the concierge app we built for a property developer, the client came to us wanting both a full-service building management tool and a community platform. We ran focus groups with social housing tenants to understand what actually generates community, and the insight was clear: familiarity is what does it. People knowing each other's names, pets, children, and interests. You cannot automate that. So we pivoted the product's strategy: we put the mundane building management tasks inside the app and designed the product to actively encourage face-to-face conversations rather than replace them.

The social feed at the heart of the product let residents post content and ask neighbours for help, but the goal was always to be a bridge to real interaction rather than a substitute for it. The conversations that happened inside the app were designed to create the kind of familiarity that would make a resident stop in a corridor and say hello. That offline moment, that recognition, is the one that generates genuine community and, in turn, genuine advocacy.

Removing the mechanics that kill community

Some product decisions actively prevent advocacy from forming, and they are usually the ones borrowed without thought from platforms that use very different measures of success. Public like counts, dislike buttons, and leaderboards that rank users against each other are all mechanics that can corrode the sense of belonging they are supposed to create. They introduce social pressure, approval-seeking, and comparison into spaces where people were trying to connect.

The football app approach

We worked on a football social app built specifically to reduce online hate. The challenge was creating a space that felt like a genuine community rather than a passive content feed, while removing the mechanics that amplify toxicity. We replaced likes and dislikes with a favourites mechanic and limited comment functionality, deliberately removing the ability to publicly dislike content. The product still felt social because users could express positive reactions and follow content they cared about, but the absence of a dislike mechanism removed the specific behaviour pattern it would have encouraged.

What to remove and what to keep

The test for any social mechanic is whether it makes users feel seen and connected, or whether it makes them feel ranked and judged. These produce very different relationships to the product and very different relationships to other users within it. A community where people feel safe tends to generate advocacy naturally. A community that produces anxiety tends to generate either silence or the kind of conflict that drives users away.

• Remove public dislike or downvote mechanisms unless the context specifically requires them
• Be cautious with visible like counts that update in real time and reward compulsive checking
• Consider whether leaderboards pit users against each other or celebrate collective progress
• Favour mechanics that surface positive interactions over ones that surface negative ones

Measuring whether your app is creating advocates

The standard metrics for app health, daily active users, session length, retention curves, tell you whether people are using the product but not whether they feel anything about it. To understand whether you are building advocates, you need different signals.

Signals worth tracking

The most direct is Net Promoter Score measured at emotionally relevant moments rather than on a fixed schedule. A score collected right after a user completes something they care about tells you something real. The same question asked at a random interval tells you less. Alongside NPS, track unprompted sharing behaviour. How often are users sharing content, screenshots, or referral links without being prompted by an in-app modal? That rate is a cleaner signal of genuine advocacy than any prompted share figure.

Qualitative signals matter too. Reading what people actually write in app store reviews and social media posts about your product tells you the emotional language they use, which is the language your design needs to speak. A product that users describe as feeling like a friend is in a different category to one they describe as working well. Both are positive. Only one generates advocates.

Set up a simple search across social platforms for your app's name alongside emotional words. What people say without being asked is a more honest measure of advocacy than anything you can capture inside the product itself.

Conclusion

Advocacy does not come from asking users to share. It comes from giving them something worth sharing, and that is a product design question first and a marketing question second. The emotional quality of the experience, whether users feel seen, surprised, proud, or connected, is what determines whether the product travels beyond its existing audience.

The work we have described here is not about adding features. Removing the football app's dislike mechanic was a subtraction. Reframing the travel app's rating prompt was a single copy change. Redesigning the property concierge's product strategy meant pulling building management features out of the foreground rather than building more into it. In each case, the product got better for users by doing less of the wrong thing rather than more of anything.

The underlying principle is consistent. Users become advocates when the product treats them as people with an identity, a story, and relationships that matter, rather than as sessions to be retained and engagement to be extracted. That shift in how you think about your users changes everything downstream: the features you build, the copy you write, the moments you design for, and the metrics you choose to track.

If you are trying to work out where your product sits on that spectrum, or what it would take to move it, let's talk about your product.

Frequently Asked Questions