Case Study: Winning With Mobile Apps for Business
An illustrative 2012 scenario of a small retailer weighing a native app against a mobile website, and what justified the investment.
By 2012, smartphone ownership had reached the point where “should we build an app” had become a real question for small and mid-sized businesses, not just large brands. Development costs had come down and app stores had matured, but building an app still meant real time and money, and plenty of businesses built one that nobody downloaded. It’s worth walking through a realistic example of a business that got the decision right, and what specifically made it pay off.
The setup. Picture a regional chain of five sandwich shops, each with a loyal but geographically scattered customer base. The owner had already built a mobile-responsive website the previous year, and it worked fine for occasional visitors checking hours or a menu. What it didn’t do well was serve his repeat customers, who ordered from the same shop two or three times a week and were tired of navigating a full menu from scratch every time on a small screen.
The decision process. Rather than starting with “we need an app,” the owner started with the actual behavior: a large share of his revenue came from a relatively small group of frequent, repeat customers. That’s a specific pattern where a native app can add real value, quick reordering, saved payment details and push notifications for a lunch special, in a way a mobile website handles more awkwardly. If his business had instead relied on occasional, one-time visitors researching him for the first time, a well-built mobile website alone would likely have served that need just as well at a fraction of the cost.
What they built. The app itself was intentionally narrow: a simplified menu, one-tap reordering of a customer’s last order, a loyalty punch card replicated digitally and push notifications limited to time-sensitive offers, no more than one or two a month. They resisted early pressure to add more features before launch, reasoning correctly that a simple app people used beat a feature-rich one that felt cluttered.
What drove adoption. In-store signage and a modest discount for the first order placed through the app got the initial download numbers moving, but what kept people using it was the actual convenience: reordering a usual lunch took three taps instead of navigating a full menu. Within a few months, roughly a third of the chain’s repeat customers had downloaded it, and the app was handling a meaningful share of orders from that group specifically.
What didn’t work as well. An early attempt to push general marketing content, blog-style posts about the business, through the app got largely ignored; customers had downloaded it for the reordering convenience, not to read about the company. Dialing that content back and keeping notifications limited to the loyalty offers and time-sensitive specials improved both engagement and uninstall rates.
The lesson underneath it. The app worked because it solved a specific, real friction for a specific, high-value segment of existing customers, rather than trying to be a general marketing channel or a way to attract entirely new customers who’d never heard of the business. For a business without that kind of repeat, high-frequency customer base, the same investment likely would have produced a low-download, quickly-abandoned app instead.
The honest takeaway for any business weighing this in 2012 is that a native app earns its cost when it removes real, repeated friction for customers who are already coming back. When the actual need is discovery by first-time visitors, that budget is usually better spent making the mobile website excellent instead.
Keep exploring: browse more Marketing Strategy guides, see everything we published in 2012 or check out the Digital Business Marketing Awards.
