The half of your queue that isn't on iPhone
Walk any UAE food court and the queue is a mix: iPhones, Samsungs, Pixels, Huaweis and a long tail of Androids. A loyalty program that only works beautifully on one platform writes off a large share of your regulars on day one. Google Wallet is how the Android half gets the same one-tap experience — it ships preinstalled on Android phones sold in the UAE, sits a swipe away from the home screen, and holds passes exactly the way Apple Wallet does on iPhone.
Perkfull issues your loyalty card as a native Google Wallet pass: branded, live-updating, and delivered from the same QR code your iPhone customers scan.
One QR code, both wallets
There is no "Android QR" and "iPhone QR" taped side by side on your counter. The single code opens a smart link that detects the phone: iPhones are offered the Apple Wallet pass, Android phones the Add to Google Wallet button. The customer never chooses a platform, never sees the wrong button, and never types anything. Ten seconds later your card is in their wallet — whichever wallet that is.
What the Google Wallet pass does
- Live balances. Stamps, points and tier are printed on the pass and update within seconds of the staff scanner — the customer watches the grid fill in while they're still at the till.
- Notifications. Messages attached to the pass surface as Google Wallet notifications — reward alerts, birthday wishes, campaign broadcasts. One send from the dashboard reaches your Apple and Google passes together.
- Your brand on the card. Logo, brand colour, hero image and the live fields you choose, laid out in Google Wallet's pass format so it reads as native on Android rather than a port from somewhere else.
- The customer's QR. The pass carries their code for staff to scan — same flow, same scanner page, same activity ledger as every other customer.
Two wallets, one design, honest differences
Apple and Google lay passes out differently — field positions, colour handling and notification styling all have platform conventions. Perkfull generates both formats from the one design you build in the Pass Designer, keeping your brand identical while letting each pass follow its platform's conventions. The differences that remain are cosmetic; everything that matters is at parity:
| Capability | Apple Wallet | Google Wallet |
|---|---|---|
| One-tap add from QR | Yes | Yes |
| Live stamp / points / tier updates | Yes | Yes |
| Push messages to the pass | Yes | Yes |
| Branded design from one template | Yes | Yes |
| Works with the same staff scanner | Yes | Yes |
One program behind both
Platform is a delivery detail, not a database split. Your dashboard shows one customer list; segments (VIP, at-risk, new), automations and insights treat an Android regular and an iPhone regular identically; a broadcast goes out once. You never think about who's on which wallet unless you're curious — and if you are, the data's there.
The setup you skip
Issuing Google Wallet passes directly means a Google Cloud project, the Wallet API, issuer onboarding, pass-class definitions and a signing pipeline — before the first card reaches a phone. On Perkfull that entire stack is already running. You design the card, print the QR, and the first Android customer who scans it is enrolled the same afternoon — from AED 149/month, unlimited customers, both platforms included. Your iPhone side is covered on the Apple Wallet page.
