Wallet Passes vs Apps vs Websites

Daniel Baudino

Updated June 15, 2025

Overview

Apps invite exploration. Websites enable discovery. Wallet passes demand instant recognition.

Choose the wrong medium, and your experience fails — not because of bad design, but because you're fighting the platform's purpose.

The mistake most teams make

Teams build apps when they should build passes. They build passes when they should build apps.

An app that requires users to navigate three screens to show a QR code at checkout is fighting its own architecture. A wallet pass that tries to display a product catalog is ignoring what wallets do well.

The question is never "can we build this as a pass?" The question is "should this be a pass?"

What are the three surfaces and their different jobs

Apps, websites, and wallet passes each excel at different things. Understanding their strengths is more important than comparing features.

What are websites best at

Websites excel at discovery, onboarding, explanation, and broad access. They are ideal when users need to learn, compare, sign up, or explore options.

The limitation: websites require intentional access. They are rarely available at the exact moment of use.

What are apps best at

Apps excel at complex flows, personalization, configuration, and ongoing interaction. They shine when users need control, history, custom actions, or rich navigation.

The limitation: apps require installation, updates, and active engagement.

What are wallet passes best at

Wallet passes excel at instant access, one-step validation, system-level surfacing, and real-world moments. They are ideal when users need speed, certainty, minimal effort, and zero decision-making.

The limitation: wallet passes are not designed for exploration or configuration.

What is the key difference between these surfaces

Apps and websites rely on user intent. Wallet passes rely on system context.

Users decide when to open an app. The OS decides when to surface a pass.

This makes wallet passes uniquely powerful — and uniquely constrained.

When is a wallet pass the right choice

A wallet pass is usually the right tool when the interaction must be fast, the moment is predictable, the action is simple, and the user should not have to think.

Examples include entry and access, tickets and credentials, membership validation, and balances and entitlements.

Is validation always required

Validation is optional, but foundational. Not all wallet passes require validation. Some passes — such as insurance cards, health records, or reference credentials — exist to be shown, not scanned.

However, when a pass is used to grant access, redeem value, or enforce entitlement, validation via QR code or NFC becomes a core design requirement. In these cases, the pass is no longer informational — it is a credential, and must be designed as such.

When is a wallet pass not the right choice

A wallet pass is not the right tool when users must configure options, multiple steps are required, content must be browsed, or decisions must be made.

In these cases, an app or website should lead — with the pass acting as a companion, not a replacement.

How do the best experiences use multiple surfaces

The strongest products don't choose between surfaces — they assign them roles.

A common pattern: website for onboarding, app for management, wallet pass for execution. Each surface does what it does best.

The Decision

If users need to think, build an app. If users need to find, build a website. If users need to prove, build a pass.

Wallet passes win when the interaction is binary: show, scan, done. They lose when the interaction requires interpretation, navigation, or choice.