A client asks for an app. What they actually want is for customers to book, order, or pay without friction.
Those are not the same request, and conflating them is one of the most expensive mistakes a business can make. Because "build an app" quietly includes: an install step, an App Store review cycle, a Play Store listing, push-notification permissions, two platforms to maintain, and the deep and abiding indifference of a customer who is not going to install anything for a business they use once a month.
For a large class of products — bookings, orders, reorders, support, status updates, payments — the messaging app already on the phone is the better surface. In much of Southeast Asia, the UAE, and Latin America, that's WhatsApp, and it isn't close.
The install cliff is the whole argument
Every step between intent and action loses people. A native app front-loads the worst possible step: stop what you're doing, go to a store, download 80MB, create an account.
A WhatsApp flow starts with a message. Zero install, zero password, identity already verified by the phone number, notifications already permitted and actually read. For a customer who interacts with you a few times a month, that difference is not a small optimization. It's the difference between a product they use and a product they meant to try.
What WhatsApp-native actually means
Not a chatbot that says "Sorry, I didn't understand that." A real product surface, built on the Business API:
- Structured flows, not free-text guessing — lists, buttons, and forms for the parts where the customer is choosing, and language understanding only where it genuinely helps.
- A real backend behind it. Inventory, availability, and payments live in your system; WhatsApp is the interface, not the database.
- Payments in-thread where the market supports it, or a single-tap link where it doesn't.
- Human handover that works. When the conversation needs a person, the person gets full context, in the same thread the customer is already in.
- A web app for the operator side. The business still needs a proper dashboard. That's a browser, not a phone.
That last point matters: WhatsApp-native usually means one surface fewer, not zero surfaces. The customer gets messaging, the business gets a web console.
When a native app is still right
Be honest about this — WhatsApp is wrong when:
- Usage is daily and habitual. Fitness, finance, logistics, anything with an icon worth a home-screen slot.
- You need device capabilities. Camera pipelines, background location, offline-first, Bluetooth, health data.
- The interface is the product. Rich, stateful UI that a message thread can't express.
- You need to own the relationship end to end, including the notification channel and the analytics.
If two or more of those are true, build the app. If none are, you're about to spend six figures and three months to add an install screen between you and your revenue.
Distribution beats interface. The best interface nobody installs loses to a decent one that's already open.
The pragmatic default
Our default for service businesses: web app for the operator, WhatsApp for the customer, native app only when the usage pattern earns it. Ship the messaging layer in weeks, learn from real conversations, and let the data — not the pitch deck — tell you whether an app is justified.
The pattern shows up across our own products: Radius runs restaurant operations in a browser while diners stay in the channel they already use. Same principle, different vertical.
The point isn't that apps are dead. It's that "we need an app" is an answer, and most businesses haven't yet asked the question.
Weighing app vs messaging for your business? Send us the use case — we'll tell you straight which one you actually need.