iOS 27 adds a native Wallet pass builder with QR scan or scratch editor, three templates, no developer account or certificate required.
Key Takeaways
Three color-coded templates: Standard (orange), Membership (blue), Event (purple); template color drives visual sorting in the Wallet stack.
The flow bypasses PassKit’s 14-year barrier: no Apple Developer account, no Pass Type ID, no certificate signing.
Apple previews iOS 27 at WWDC June 8; public release September 2026.
Open questions include iCloud sync across devices, .pkpass export, barcode format support (Code 128, PDF417, Aztec), and whether merchant co-signing is possible.
Third-party tools like WalletWallet and Pass2U retain an edge on Google Wallet pass generation, cross-device sharing, and API-pulled metadata passes.
Hacker News Comment Review
Commenters broadly see this as parity with Google Wallet, which has supported user-created barcode passes for years via a native UI flow.
There is real frustration that Apple frames this as innovation after 14 years; the consensus is the supply-side gap was Apple’s UX failure, not developer inaction.
Proximity and time-based lock-screen notifications, a key PassKit feature, are unconfirmed for user-created passes and seen as a likely missing capability at launch.
Notable Comments
@mosburger: Questions whether user-created passes will support proximity/time-triggered home-screen notifications, a feature dependent on PassKit infrastructure Apple has not confirmed here.
@lxgr: Flags a real operational pain point: airlines often set incorrect UTC/local expiry times, causing passes to auto-archive before departure.
