Quick answer: build for both
UK device share is roughly 50% iOS, 50% Android, closer than the US and far closer than markets like India. Picking one wallet means ignoring half your customer base. The good news: launching on both rarely doubles the work if your platform supports it natively.Where Apple Wallet leads
Apple Wallet is the more mature product, and it shows.- Lock screen push notifications with deep customisation.
- Tighter visual control colour, logo, strip imagery, back-of-pass fields.
- Pass relevance – Apple surfaces pass automatically based on time and location.
- Higher engagement benchmarks push open rates on Apple Wallet consistently outperform email and SMS for UK retailers.
Where Google Wallet leads
Google Wallet caught up fast and now offers parity for most retail use cases.- Geo-triggered notifications that fire when a customer is near your shop.
- Smart Tap support for NFC redemption in physical retail.
- Tighter integration with Google services useful if you’re already running Google Ads or Performance Max.
- Larger addressable audience in some UK segments. Convenience retail, value fashion, and out-of-London markets skew Android.
UK device split: what the numbers say
The national average sits roughly even, but it shifts by category:| Segment | iOS share (approx.) | Android share (approx.) |
|---|---|---|
| Premium fashion / urban | 60% | 40% |
| Coffee & QSR | 50% | 50% |
| Convenience & value retail | 45% | 55% |
| Regions outside London | 45% | 55% |
Feature comparison
| Feature | Apple Wallet | Google Wallet |
|---|---|---|
| Push notifications | Yes – lock screen | Yes – lock screen |
| Geo-triggers | Yes | Yes |
| NFC at till | Limited | Smart Tap supported |
| Brand visual control | High | High |
| Real-time pass updates | Yes | Yes |
| Default on device | iOS | Android |
How to launch on both without double the work
The trick is choosing a platform that issues passes to both wallets from a single setup. With Litecard, one pass design and one integration push to Apple Wallet and Google Wallet simultaneously. Your team builds once, your customers tap once, and the pass lives wherever they need it. That’s the bit most teams underestimate. The wallet decision isn’t really Apple vs Google. It’s whether you’re issuing passes in a way that lets you support both from day one – or locking yourself into one and re-platforming twelve months later.The takeaway
Pick the wallet your customers carry. For UK brands, that’s almost always both. The platforms have converged enough that the meaningful differentiator now is how quickly and cleanly you can ship and how much of your customer base you actually reach when you do.Frequently Asked Questions
Apple Wallet is built into iOS and runs only on iPhones and Apple Watches. Google Wallet runs on Android devices. Both support digital passes, loyalty cards, tickets, and payments, with broadly similar feature parity for retail use cases. The main practical difference is the operating system they run on.
Most UK businesses should build for both. UK device share is roughly 50% iOS and 50% Android, so supporting only one wallet leaves around half of customers on legacy channels. Modern wallet platforms issue passes to both from a single setup, so the work is rarely doubled.
Across the UK, market share is close to 50/50 between iOS and Android. The split varies by retail segment: premium fashion and urban audiences skew 60% iOS, while convenience retail and regions outside London skew 55% Android.
Yes. Modern digital wallet platforms like Litecard issue a single pass design to both Apple Wallet and Google Wallet from one integration. This avoids duplicate development work and keeps the customer experience consistent across iOS and Android.
Both Apple Wallet and Google Wallet support lock screen push notifications with high open rates compared to email. Apple Wallet has slightly more mature pass relevance and visual controls, while Google Wallet offers stronger geo-triggers and Smart Tap NFC support for in-store redemption.
