Brands Don’t Have an App Problem
They have a Behavior Design Problem
If you’re responsible for growth in any business today, the system you’re operating is becoming increasingly difficult to manage.
Acquisition costs have increased by more than 60% over the past five years, according to ProfitWell, but the signals that once made that spend intelligible are fading. Privacy changes and platform fragmentation have materially reduced attribution fidelity, as reported by AppsFlyer and Meta, making it harder to understand what is actually driving performance.
At the same time, customer expectations have shifted. People no longer experience brands through a single channel. They expect interactions to feel continuous, relevant, and immediate, regardless of where they happen.
Most retail organizations are still operating on a model that was built for a different environment. It is a model designed around discrete transactions, mediated by platforms that once offered both reach and clarity.
That model is no longer holding.
What is striking is not just the pressure itself, but how consistently companies respond to it. Rather than rethinking the system, they look for ways to extend it. And increasingly, that extension takes the form of a mobile app.
The Misunderstood Role of the App
The decision to build an app is rarely irrational. It is usually framed as a way to regain control. An app promises stronger loyalty, more repeat purchase, and better attribution. It appears to offer a direct relationship with the customer in a landscape where intermediaries are becoming more powerful.
But the promise of the app is often misunderstood.
An app is not, in itself, a solution to any of these problems. It is simply another surface through which a system operates. If the underlying system does not change, the outcomes will not change either.
This is why so many retail apps fail to deliver on their promise. Data from Adjust shows that more than 90% of users abandon an app within the first 30 days, which means the problem is not distribution but sustained relevance. They are built as extensions of the website, or as containers for existing programs, rather than as systems designed to influence behavior over time.
An app only becomes valuable when it becomes part of a customer’s routine. Without that, it remains inert. It may be downloaded, occasionally opened, and largely forgotten, in a landscape where attention is already concentrated in a small number of dominant apps, as consistently shown by data.ai.
The difference between those two outcomes is not the quality of the interface. It is the design of the system behind it.
Loyalty as an Outcome of the System
This becomes most visible in how retailers approach loyalty.
The instinct is to begin by embedding the loyalty program within the app. On the surface, this makes sense. If loyalty is the goal, then the program that represents loyalty should be central to the experience.
But this approach confuses representation with causation.
Loyalty programs do not create behavior. They record it. They provide a way to track and reward actions that have already occurred, but they do not, on their own, generate those actions. Research from Bond Brand Loyalty shows that more than half of loyalty program memberships are inactive, reinforcing how rarely these systems translate into ongoing engagement.
Customers return to products that consistently deliver value in moments that matter to them. That value has to feel timely, relevant, and easy to access. It has to align with the customer’s context, rather than forcing the customer to adapt to the product.
When that kind of value is present, behavior follows. When it is absent, no amount of points or rewards will compensate for it.
In that sense, loyalty is not something you build into the product. It is something that emerges from how the product behaves.
The System Behind Repeat Purchase
The same dynamic applies to repeat purchase.
Retail has historically been structured around acquisition. The system is designed to bring customers in, convert a percentage of them, and then begin the process again. Each visit is treated as an isolated event, and the relationship between brand and customer is largely reset after each transaction.
This model is effective, but it is also inherently fragile. It depends on continuous spend, and it does not accumulate knowledge or context about the customer in a way that meaningfully shapes future interactions. The economic implications are significant. According to Bain & Company, increasing retention by just five percent can increase profits by as much as ninety-five percent, while Invesp estimates that existing customers are up to five times more likely to convert than new ones.
An app introduces a different kind of system.
Instead of starting from zero with each interaction, the relationship persists. The customer is no longer anonymous. Their behavior unfolds over time, and the brand has the ability to respond to that behavior in a way that feels continuous rather than episodic.
At that point, the nature of the problem changes. Growth is no longer about capturing intent when it appears. It becomes about creating the conditions under which intent re-emerges.
Repeat purchase is not simply a reflection of customer preference. It is a function of how well the system is able to re-engage the customer at the right moment, with the right context, in a way that feels relevant rather than intrusive.
When that system is well designed, repeat behavior becomes more predictable. In practice, many ecommerce businesses already see a disproportionate share of revenue come from returning customers, often approaching forty percent according to RJMetrics. When it is not, it remains dependent on external triggers and continued spend.
Attribution and the Question of Control
What often appears, on the surface, to be an attribution problem is in fact a consequence of this deeper structural issue.
Retail marketers are operating inside environments where they do not control the underlying system. Data is fragmented across platforms, and visibility into behavior is partial at best. Surveys from Gartner show declining confidence in attribution models, while research from McKinsey & Company highlights how incomplete and fragmented customer journey data has become.
In that context, attribution becomes an attempt to reconstruct a system that is no longer fully observable.
An app changes that dynamic, but not because it solves attribution directly. It changes who owns the system in which behavior occurs.
Within an app, identity persists across interactions. Behavior can be observed as it unfolds. Engagement is not inferred from external signals but measured directly within the system itself. The loop between action and outcome becomes visible in a way that is increasingly difficult to achieve elsewhere.
The result is not just better measurement. It is a different way of making decisions. When behavior can be observed clearly, the need to rely on assumptions diminishes. The system begins to reveal what is actually working.
When this system is designed well, the performance difference becomes clear. Mobile apps consistently outperform mobile web experiences, with data from Criteo showing conversion rates that are often two to three times higher. Engagement follows a similar pattern, with Airship reporting significantly stronger retention among app users.
Over time, that clarity compounds into advantage.
What Building Outlook Mobile Actually Revealed
This dynamic is not unique to retail.
While building Outlook Mobile at Microsoft, we faced a different set of surface-level problems, but the underlying system was the same. The challenge was not simply to build a product that people could use, but to create a system that people would return to.
Growth did not come from adding features in isolation. It came from understanding how users moved through the product, identifying where they disengaged, and redesigning those moments to reduce friction and increase relevance.
Every return was the result of value being delivered in a way that aligned with the user’s context. Over time, those returns accumulated into habit.
What became clear through that process was that growth is not a function of what the product contains. It is a function of how the system behaves.
The Missing Discipline
This is the part that most retail strategies underestimate.
The difficulty is not in building an app. The difficulty is in designing and operating the system that gives the app meaning.
Creating a mobile experience that people return to requires a different kind of organizational capability. It requires instrumentation that captures behavior from the beginning. It requires continuous experimentation, not as a separate initiative, but as a core part of how the product evolves. It requires aligning teams around outcomes that are expressed in behavior, rather than outputs that are expressed in features.
Most retail organizations are not structured in this way. Their strengths lie in brand, merchandising, and supply chain. Those capabilities remain essential, but they do not, on their own, produce the kind of system required to shape customer behavior over time.
The result is a gap between intention and execution. The desire to create loyalty and repeat purchase is present, but the system required to produce those outcomes is not.
From Channels to Systems
What is happening here is part of a broader shift.
For a long time, growth was treated as a function of channel performance. The focus was on acquiring more traffic, improving conversion rates, and increasing efficiency within the funnel. The underlying assumption was that if the inputs could be optimized, the outputs would follow.
That assumption is becoming less reliable.
The companies that are succeeding in this environment are not simply optimizing channels. They are designing systems that shape behavior over time. They are creating environments in which customers return, engage, and deepen their relationship with the product without requiring constant re-acquisition.
This is a different way of thinking about growth. It is less about driving isolated events and more about creating continuous interaction.
In that model, the app is not the product. It is the interface through which the system operates.
The Strategic Shift
The distinction between web and mobile becomes clearer when viewed through this lens.
The web is well suited to capturing intent at the moment it arises. It performs effectively as a transactional surface, converting demand that already exists.
Mobile, when designed correctly, functions differently. It creates the conditions for that demand to reappear. It enables a relationship that persists between transactions, rather than resetting after each one.
As acquisition becomes more expensive and less predictable, this distinction becomes more important. More than seventy percent of consumers now expect personalized experiences, according to Salesforce, and companies that deliver on that expectation generate materially higher growth, as shown in research by McKinsey & Company. Brands that rely entirely on external platforms for discovery are increasingly dependent on systems they do not control.
The companies that win will be those that build systems of their own. Systems that allow them to maintain a direct, persistent relationship with their customers, and to shape behavior over time rather than simply reacting to it.
This is not a shift in channel strategy.
It is a shift in how the business operates.
At its core, growth in retail is no longer driven primarily by traffic. It is driven by behavior. And behavior, in turn, is a function of the system you design.
The brands that recognize this, and build accordingly, will not just perform better within the existing model.
They will define what the next model becomes.