Platforms
Apple Wallet and Google Wallet, from one template.
They work differently under the hood - how updates deliver, how they're authenticated, how notifications land. Pocket handles both natively, so you design once and ship to every phone.
See pass types
AAurora Coffee
WalletPass
Gold member
Tier
Gold
Access
Full
AAurora Coffee
GooglePass
Gold member
Tier
Gold
Access
Full
Under the hood
How the two wallets actually differ.
You don't need to know any of this to use Pocket - but if you're curious, here's what happens behind each platform.
| Apple Wallet | Google Wallet | |
|---|---|---|
| Update delivery | Push notification (APNs) tells the device to re-fetch the pass | Direct REST update - the object is patched in place |
| Authentication for updates | Mutual TLS using your pass-signing certificate | Service-account credentials over the Google Wallet API |
| Lock-screen notification | Native wallet notification on update | Native wallet notification via the addMessage API |
| Barcode formats | QR, PDF417, Aztec, Code 128 | QR, PDF417, Aztec, Code 128 |
| NFC | Supported on compatible devices | Supported on compatible devices |
| Design surface | Header, primary, secondary, auxiliary, and back fields | Header and body text modules, mapped from the same template |
| One template, both wallets | Yes - a single Pocket template maps to both | Yes - a single Pocket template maps to both |
One template. Zero platform-specific work.
Design a template once in Pocket and it maps to both platforms automatically - fields, colours, barcode, and NFC. Push an update and both wallets receive it, each the way that platform expects.