What does a loyalty app have to do?
A loyalty app has five jobs. Each one maps to a moment in the member's week.
- Identify the member at checkout. A barcode, QR code or NFC tap tells the till or the website who is buying. That scan is what earns the points.
- Show where the member stands. Balance, tier and progress to the next reward have to match the platform's ledger at the moment the member looks.
- Deliver offers. Personal offers and member prices give members a reason to open the app before they shop.
- Redeem. The member spends points or applies a reward in the app, at the till or in the online cart.
- Run the account. Profile, consent, linked cards, missing points claims and account deletion all live here.
Published programs show these jobs in practice. Lidl Plus applies member prices at checkout when the shopper scans the app. It also carries personalized coupons and digital receipts. Starbucks lets Rewards members earn Stars when they pay with cash, cards or selected mobile wallets. Its app also has Mobile Order and Pay, which takes orders ahead for pickup at participating stores.
Where should the loyalty app live?
There are three places to put a program on a member's phone. The right one depends on how often members visit and what the brand already ships.
Inside the brand's main app
If members already open a brand app for other reasons, loyalty can be one part of it. Deutsche Telekom puts Magenta Moments inside MeinMagenta, the app its customers sign in to with a Telekom login. The offers sit behind a heart in the menu bar. Telekom says several million customers have used them in the app since the 2022 launch.
The case for this model is reach. The member has the app installed and is signed in, so loyalty rides on habits the brand already built. The cost is shared space. The loyalty team competes with every other product team for screens and release slots.
A standalone app
A separate app suits a program that does a different job from the core brand app. Emirates runs Skywards Everyday as its own app for earning Skywards Miles on daily spending. Members sign in with their Emirates Skywards login and link up to five Visa or Mastercard cards. They earn Miles when they pay with a linked card at partner outlets listed in the app. The trade-off is reach. Every member has to find and install one more app.
A wallet pass
A digital wallet pass puts the membership card in Apple Wallet or Google Wallet with no app to install. Apple's design guidance says the store card style is for loyalty cards, points cards and gift cards. When an account carries a balance, the pass usually displays it. Apple's pass format accepts up to 10 locations that the phone uses to show a relevant pass. In Google Wallet, people can search for a program and start to join or sign in from Wallet. They finish on the brand's mobile site, then add the card.
Passes are light, and their limits are real. Google allows at most 3 messages with a push alert in any 24-hour period. A pass also has no room for longer journeys such as browsing a catalog or ordering ahead.
| Option | Fits best when | What the member does first | Main limit |
|---|---|---|---|
| Loyalty inside the main app | Members already open the brand app to order, pay, book or manage an account | Nothing new if they are signed in | Loyalty shares screens and release slots with other teams |
| Standalone loyalty app | The program does a distinct job, such as earning at partner outlets | Install the app and sign in | Every member has to install one more app |
| Wallet pass only | The main need is a fast ID at checkout and a balance at a glance | Add the pass from a link, email or receipt | Few screens and capped alerts |
| Wallet pass plus an app | The brand wants a fast ID at the till and a fuller app for offers and the account | Either path | Two surfaces to keep in step with the ledger |
Should you build the app, white label it or use a platform SDK?
There are three build paths. They differ in who owns the roadmap and how fast the first version ships.
Build on the platform's APIs
The brand's own team builds the front end and calls the loyalty platform's APIs for every balance, offer and redemption. This is the headless loyalty model. The brand controls the design and the release plan, and it staffs a mobile team for the life of the app. It fits best when loyalty lives inside an existing brand app, which already has a team and a release train.
Use a white-label app
A white-label loyalty app is a vendor's ready-made app, dressed in the brand's name, colors and content. It is the fastest route to a standalone app. Read the store rules before you sign. Apple's App Review Guideline 4.2.6 rejects apps made from a commercialized template unless the provider of the app's content submits them. So the brand, as the content provider, publishes the app from its own developer account. Apple's Guideline 1.5 adds that Wallet passes are signed with a certificate assigned to the brand or trademark owner.
Add the platform's SDK to your own app
An SDK is a code library the platform vendor ships for iOS or Android. It packages standard loyalty screens and calls, such as the card, balance, offers and history. The brand's developers drop those modules into their own app. The brand keeps its app and its store listing, and it skips rebuilding screens every program needs. Ask how the SDK takes on the brand's design and how often it updates. Then ask what breaks in your app when the SDK version changes.
Native, cross-platform or web app?
For a loyalty app, the deciding factor is access to the phone itself. A native or cross-platform app can use the wallet, push alerts and the camera for scanning. A web app ships through the browser with no store review. On iPhone, web push arrived in iOS and iPadOS 16.4 for web apps the member adds to the Home Screen.
Apple also sets a floor for apps in its store. Guideline 4.2 says an app should include features, content and UI that take it beyond a repackaged website. A thin wrapper around the loyalty web page fails that test.
Which loyalty app features do members use most?
Few brands publish how members use each app feature. So treat any ranked list of top features with care. The public numbers come from company filings and press releases.
- McDonald's counts sales to loyalty members who identify themselves when they buy. It reported nearly 220 million 90-day active loyalty users across 70 markets at the end of June 2026. Sales to loyalty members over the trailing twelve months rose more than 20% to $40 billion.
- Chipotle says digital sales were 38.3% of food and beverage revenue in the second quarter of 2026. That share counts its app, its website and third-party delivery.
- Lidl says more than 120 million customers use Lidl Plus worldwide. Its features include points and member prices that apply when the app is scanned at checkout. It also has personal coupons and digital receipts.
- Telekom says several million customers have used Magenta Moments in its app since it began in 2022. Members get a gift each day, plus contests and partner perks.
Read together, these disclosures center on the transaction. Members want to be recognized, order fast and get a member price. Build the first release around that moment. Then measure your own feature use before adding more.
For illustration, take a program with 4 million members who bought something in the last 90 days. If 1.6 million of them scanned the app at checkout at least once, the app's checkout reach is 40%. If 600,000 activated an offer in the app, offer reach is 15% of active members. Work out the same ratio for each feature, from balance views to wallet pass adds. The ranking shows which features earn their place in the next release.
What does the app need from the loyalty platform?
Agree on what the app needs from the platform before design starts. Put each need in the build plan.
- Live balance and tier. Every read comes from the platform's ledger through an API, so the app, the till and the website show the same number.
- Offer rules on the server. Eligibility and offer content come from the platform. Marketing changes an offer there, and the app shows it on its next refresh.
- One member ID. The app login, the web account and the store lookup all point to the same member. Emirates, for example, has Skywards Everyday members sign in with the Skywards login they already have.
- Events for messaging. Earn, redeem, tier change and expiry events flow to the push and email tools, so each message fires on real activity.
- Wallet pass updates. When a balance changes, the platform triggers the pass update. In Apple's flow, the brand's server sends a push notification and the device then fetches the changed pass.
- Safe posting and reversal. A retried request must credit points once, and a refund has to reverse the right amount.
- Account deletion. Apple requires apps that support account creation to offer account deletion inside the app. Google Play requires an in-app path plus a web link where users can ask for deletion. Each request has to reach the loyalty platform, where the program's terms decide what happens to the balance.
Security belongs in the same contract. A fixed barcode can be screenshotted and shared. Google Wallet supports rotating barcodes that change about once a minute, and the reader accepts only the latest one. Account takeover is the bigger risk, because the app holds a balance with cash value. The loyalty fraud prevention guide covers the controls.
Accessibility is a legal duty in the EU. The European Accessibility Act covers e-commerce services provided to consumers after June 28, 2025. Its definition takes in services run through websites and mobile apps. A loyalty app that sells a paid plan or goods to EU shoppers fits that test. Check the scope with your lawyers and test the member screens.
How do you develop a loyalty app, step by step?
- Pick the home. Choose the main app, a standalone app, a wallet pass or a pass with an app.
- Pick the build path. Build on APIs, license a white-label app or add an SDK. Confirm whose account submits the app to the stores.
- Write the platform contract. List every call and event the app needs, with a response target and error handling for each.
- Design the checkout moment first. Time how fast a member can show the code on a weak signal, at a real till.
- Add the wallet pass. Issue it in the app, in emails and on receipts. Keep it updated from the ledger.
- Clear the store rules. Build in-app account deletion. If the app offers a social login, Apple's Guideline 4.8 also requires an equal option that limits data collection to name and email.
- Track every feature. Log scans, offer adds, redemptions and balance views for each active member.
- Pilot, then scale. Launch in one market or segment and compare app users with members who shop without the app. Then roll out.
Buyer's checklist for a loyalty app and its platform
Use this table in vendor demos. Ask each vendor to run every test live, on a test account.
| Criterion | Why it matters | What to ask in a demo |
|---|---|---|
| Live balance and tier API | Members stop trusting an app that disagrees with the receipt | Post a purchase at a test till. How soon does the app show it? |
| Offer rules on the server | Waiting for an app release slows every offer change | Change an offer live. Does it appear with no app update? |
| How the member is scanned | The scan is what earns points and records the sale | Show the barcode, QR and NFC options. Do the codes rotate? |
| Wallet pass support | Members who never install the app still need a card | Issue Apple and Google passes. How do balance updates reach them? |
| One login per member | Two accounts for one person split the points and the history | Sign in with an existing web account. How are duplicates merged? |
| SDK and API reach | Each gap turns into code your team must keep up | Which screens does the SDK ship? Which features are API only? |
| Who owns the store listing | Apple turns down template apps unless the brand that owns the content submits them | Whose store account will publish the app and sign the passes? |
| Account deletion and consent | Both app stores require a deletion path | Delete a test account. What happens to its points and data? |
| Fraud controls | The app holds value an attacker can spend | Show login risk checks and redemption limits. |
| Data on each feature | Feature rankings need clean event data | Which app events stream to our data warehouse? |
| Uptime and support | A loyalty outage at peak backs up the checkout line | What is the uptime SLA, and who answers a priority one incident at peak? |
How GRAVTY handles the loyalty app layer
GRAVTY is the loyalty platform behind the app. Its APIs and SDKs support end-to-end Android loyalty apps, per the integrations page. GRAVTY issues and updates Apple Wallet passes and connects to push services such as Apple Push and Firebase. It also supports a WhatsApp channel where members check balances and offers, and members can sign in with their Apple ID.
The platform runs 500M+ members in production. It has 150+ system integrations and a 99.99% uptime SLA. See the technology page for how it is built. Deutsche Telekom runs one program on GRAVTY across 9 countries. Its technical delivery manager says the program is "really part of the everyday life that customers are having with the app."
Frequently asked questions
Do members need an app to join a loyalty program?
No. A wallet pass, a phone number at the till or a web account can identify a member. Google Wallet even lets people search for a program and start to sign up from Wallet, then add the card. An app earns its place when members need offers, ordering or account tools on the go.
Is a white-label loyalty app allowed on the App Store?
Yes, when the brand submits it from its own developer account. Apple's Guideline 4.2.6 rejects template-built apps that the template provider submits for a client. Apple also asks that Wallet passes be signed with a certificate assigned to the brand.
What happens to points when a member deletes their app account?
The program's terms decide, so write that rule before launch. Apple and Google Play both require an in-app path to delete an account, and Google also requires a web link. The request has to reach the loyalty platform, where the balance and history live.
How is a loyalty app different from a loyalty platform?
The app is the member's front end, and the platform is the back end that holds the ledger, rules, offers and member records. One platform can feed a brand app, a standalone app, wallet passes, the website and store tills at once. Replacing the app leaves the points untouched.
Can a loyalty app work without a signal?
Partly. An app can keep the member code on the phone so it shows with no signal. A Google Wallet pass link also works offline when the Wallet app is installed. Balance updates, offer adds and redemption need a live call to the platform, so design the checkout screen for a weak signal.
How many notifications can a loyalty wallet pass send?
Google Wallet allows at most 3 messages with a push alert in any 24-hour period. Apple pass updates go from the brand's server through Apple's push service when pass data changes. Save alerts for balance changes and offers the member cares about.

