Why Restaurant Apps Are Quietly Dying
A decade after every chain in America launched its own ordering app, app installs are flat, daily-active rates are tiny, and the channel that’s eating the share isn’t another app. It’s your messages thread.
Photo by Rob Hampson on Unsplash
Look at your phone’s home screen. Now count the restaurant apps. The honest answer for most people in 2026 is between zero and two — and one of them is probably Starbucks, because of the rewards. The rest of the stuff you order from, you order from in some other way: a website, a delivery aggregator, a Google Maps button, or, increasingly, a text message thread.
This is a quiet collapse. Ten years ago every restaurant chain with more than fifty locations was building an app. Now most of those apps still exist — they’re just not where customers are spending their time. Why? A handful of reasons that are obvious in retrospect.
The home screen is a finite resource
The average smartphone user has somewhere between 30 and 80 apps installed. Of those, a small minority get opened weekly. The home screen — the small set of apps a user actually sees — is bounded by physical geometry. You can’t put twenty restaurants on it. You can put one or two, and even those compete with banking, calendar, social, photos, and your kid’s school portal.
This was always going to be a problem for restaurants. A consumer might love your food, but if your app is on screen 4 of their phone, behind a folder labeled “misc,” you’ve effectively lost them.
Logins are friction, and friction compounds
The average restaurant app makes a customer:
- Download a 60–200 MB app.
- Create an account with email or phone.
- Verify the account via a code.
- Add a payment method.
- Allow notifications. (Or decline, and lose the rewards.)
- Set a default location.
- Re-log in three months later when the session expires.
Every step is small. The product of all of them is large. By the time a customer has done all of that, they have made a substantial cognitive investment — and the next time they want a sandwich, they will almost always reach for whatever requires the least of that investment.
The replacement is asynchronous and channel-agnostic
What is replacing restaurant apps isn’t one channel. It’s the absence of channel — the customer orders through whatever surface they’re already using. A reply to an Instagram story. A text. A click on a Google Maps button. A QR code at the table. A voice assistant. The common thread: they don’t require the customer to install or open anything new.
This is what people mean by “conversational commerce” even though that phrase makes everybody’s skin crawl. It’s ordering that happens inside surfaces customers already inhabit. The surface that’s growing fastest is SMS, because SMS is unique among messaging channels in that it works on every phone without an app, without a network, and without the customer doing anything except sending a message.
What this means for chains
Chain restaurant apps aren’t going away. Starbucks is going to keep being good. Chipotle is going to keep being good. The rewards programs that big chains have built are real switching costs and they will continue to justify a dedicated app.
But the next layer down — the regional chains, the ten-location concepts, the single-location independents — they should not be building apps in 2026. They should be on every channel a customer might use to find them, with a back end that funnels every order into the same kitchen ticket. The mistake is to think of this as a technology problem; it’s a customer-behavior problem, and the customers have decided.
Cons of the channel-less approach (because there are some)
It would be dishonest to make this sound effortless. Going channel-less has costs:
- Discovery is harder. Apps gave restaurants a captive audience to push promotions to. Text and web don’t. You have to push promotions through other channels — email, social, Google.
- Personalization is shallower. An app knows what you’ve ordered before because it’s a logged-in environment. SMS can do this too, but the data is less rich. The trade-off favors privacy.
- Push notifications are gone. SMS marketing exists, but the rules and the carrier filtering mean it’s a worse loudspeaker than push. Probably this is good for everyone.
- Rewards programs are awkward. They work, but the UI for “you have 600 points” is harder to design in a chat thread than in a dedicated app.
These are real. None of them are reasons to build an app in 2026. They’re reasons to build a slightly smarter messaging layer.
The honest forecast
Restaurant apps don’t go to zero. The top hundred chains keep theirs and they will be fine. The middle of the market — and the long tail — will move to channel-less ordering over the next 3–5 years. The reason will be obvious in retrospect: customers are voting with their thumbs, and their thumbs are tired of typing passwords.
