The most expensive decision in a loyalty programme is made before a single customer joins: whether they have to install something. Everything else, reward size, mechanic, branding, is a rounding error next to it.
Why does requiring an app kill enrolment?
Requiring an app install collapses enrolment because it converts a five-second decision into a multi-step commitment made under social pressure at a counter. The customer must leave the conversation, open an app store, search, download, wait, open, and register, typically while someone waits behind them.
The economics also differ from what people assume. A chain with hundreds of locations can justify an app because a customer might use it daily across many sites. A single café is asking for permanent phone real estate in exchange for a free coffee every three weeks. Most customers decline, politely, by saying they will do it later.
What does a no-app loyalty programme use instead?
No-app loyalty programmes use wallet cards: digital cards stored in Apple Wallet or Google Wallet, both of which ship with the phone and cannot be uninstalled. A wallet card provides almost everything an app provides for loyalty purposes.
| Capability | Dedicated app | Wallet card |
|---|---|---|
| Card on the customer's phone | Yes | Yes |
| Updates without customer action | Yes | Yes |
| Push notifications | Yes | Yes, to the card |
| Shows on the lock screen near the shop | Sometimes | Yes |
| Requires an install | Yes | No |
| Requires account creation | Usually | No |
| Works on any modern phone | If you build both platforms | Yes |
Is a QR code enough to remove the friction?
A QR code removes the app install but not the customer's involvement, and the remaining friction is larger than most businesses expect. The customer still has to take out a phone, unlock it, open a camera, hold it steady on a code, and tap through a page.
In a quiet shop this is fine. During a morning rush, with the customer holding a bag in one hand, it is where enrolment silently stops happening. Staff learn quickly that offering the card slows the queue, so they stop offering it, and the programme fails for operational reasons rather than product ones.
What removes the friction completely?
Friction reaches zero when the customer is not required to do anything at the counter. That is possible if a staff member enrols them from a phone number alone: the customer says their number, the staff member types it, and the link arrives by text a few seconds later for the customer to open whenever convenient, on the walk out, on the bus, that evening.
This is how Loonine works, and it is the main reason the product exists. The enrolment moment demands nothing from the customer and about three seconds from your staff.
It does introduce an obligation. Because a staff member is entering someone else's number, consent has to be explicit and recorded at that moment rather than assumed: this matters under GDPR in the EU and under equivalent rules in the Gulf. Any platform offering this flow should be collecting and storing that consent; if it is not, that is a compliance problem you would inherit.
What do you give up without an app?
You give up three things, and for most small businesses none of them matter. There is no in-app ordering, no rich browsing interface, and no home-screen icon carrying your brand. If ordering-ahead is central to your business, an app may be justified, but it should be justified on ordering, not on loyalty.
What you keep is the part that drives retention: a card on the phone, visible progress, automatic updates, and a channel to reach customers who have stopped coming.
How much does each enrolment method cost you?
Enrolment method is the largest single variable in a loyalty programme's outcome, and the gap between methods is wide enough to decide whether the programme pays for itself. The figures below are the ranges Loonine sees and hears reported across independent venues; treat them as orders of magnitude rather than precise measurements, and measure your own.
| Method | What the customer must do | Typical join rate | Seconds at the counter |
|---|---|---|---|
| Install an app | Search, download, register | Very low | 60-180 |
| Scan a QR code | Unlock phone, open camera, tap through | Moderate | 20-40 |
| Type an email into a tablet | Unlock nothing, but type accurately | Moderate | 25-45 |
| Say a phone number | Nothing but speak | High | 3-8 |
The column that predicts failure is the last one. Any method costing more than about ten seconds at a counter will be quietly abandoned by staff during busy periods, and a programme offered only in quiet periods reaches the customers who matter least.
How does a wallet card work without an app?
A wallet card is a small signed file that the phone's built-in wallet stores and knows how to display, and it can be updated remotely because the wallet registers with the issuer for push updates. No third-party application is involved at any point.
Three properties follow from that design and explain why wallet loyalty behaves the way it does. The card is cryptographically signed, so a customer cannot edit their own stamp count. The wallet subscribes to updates, so the business can change what the card says at any time. And because the wallet is part of the operating system, the card appears on the lock screen near the shop without anything running in the background.
The limitation is equally structural: a card is a card, not a program. It cannot run logic, take payment or show an ordering interface. For loyalty specifically, none of that is needed.
Can I send notifications without an app?
Yes. Updating a wallet card pushes a notification to the customer's lock screen, so a business can reach every enrolled customer without owning an app and without paying per message. This is the feature businesses are most surprised by, and it is the one that makes the whole model viable.
The practical constraints are worth understanding. The notification is attached to a change in the card, so it suits messages tied to the card: a stamp added, a reward ready, an offer that appears on the card. It is not a free channel for arbitrary marketing, and treating it as one gets the card deleted.
A reasonable cadence for an independent business is no more than two or three pushes a month, each carrying something the customer would plausibly want. Loyalty cards have an unusually low removal rate when that restraint is observed, and an unusually high one when it is not.
What about customers with older phones?
Apple Wallet has been on every iPhone since iOS 6 in 2012, and Google Wallet cards work on Android 5.0 and later, so in practice any phone still in daily use supports wallet cards. The real exception is a feature phone with no smartphone operating system.
For those customers, keep a small stack of paper cards. A loyalty programme that refuses a customer because of their handset is worse than one that runs two formats, and the paper fallback will apply to a very small share of the base.
What does the staff side look like?
Staff need one screen and one action. On Loonine, a staff member opens the app, types the customer's phone number, and taps send: the card arrives by text a few seconds later and the customer opens it whenever they like. Adding a stamp on a later visit is a single tap on that customer's record.
This matters more than it sounds. Loyalty programmes usually fail at the staff layer rather than the customer layer: a flow that takes three taps gets used every shift, and one that takes eight gets used in the first week and then quietly dropped. When you evaluate platforms, watch your least enthusiastic staff member use it during a rush.
How do I get consent right without an app?
When a staff member enters a customer's phone number on their behalf, consent must be asked for out loud and recorded at that moment: you cannot rely on a checkbox the customer never saw. This is a real obligation under GDPR in the EU and under comparable rules in the UAE and the wider Gulf.
In practice it takes one sentence: "Can I text you your loyalty card?" A yes is consent, and the system should store that it was given, when, and by whom it was recorded. Loonine captures this at enrolment automatically, and the record carries a timestamp, though it is not exportable by the business.
Two rules keep the rest simple. Use the number for the loyalty programme and nothing else unless the customer separately agrees, and make opting out work immediately, in one step. A programme that is difficult to leave generates complaints that cost far more than the customers it retains.
Which businesses still need an app?
An app is justified when the customer needs to do something between visits that a card cannot express: ordering ahead, booking, browsing a catalogue, or managing an account. If that is your business, build the app for that reason and let loyalty ride along inside it.
It is not justified by loyalty alone, at any size of independent business. The test is simple: if the only thing the app would do is show a stamp count, the wallet already does it, for free, on a phone the customer will never uninstall.