iOS 27 adds a native QR-scan or build-from-scratch pass creator to Wallet with three templates, no developer account or certificate required.
Key Takeaways
Three templates: Standard (orange), Membership (blue), Event (purple); color also drives visual sorting in the Wallet stack.
No Apple Developer account, no Pass Type ID, no certificate signing – the entire gap that third-party tools like Pass2U and WalletWallet filled for 14 years.
PassKit launched with iOS 6 in 2012; adoption stalled at airlines and big-box retailers because the developer barrier killed the long tail (gyms, libraries, cafes).
Open questions before WWDC June 8: iCloud sync across devices, .pkpass export for sharing, barcode format support beyond QR, and location/time lock-screen behavior.
Google Wallet already supports user-created passes with any barcode; this brings iOS to parity rather than leading the category.
Hacker News Comment Review
Commenters broadly confirmed the pain was real – many relied on photo libraries, sharpie labels, or third-party apps like Pass2U just to store a library card barcode.
Several noted Apple could have solved the supply-side problem 14 years earlier by offering a no-code pass portal for small venues; the delay is framed as an Apple product strategy failure, not developer inaction.
Technical skepticism centers on unknowns: barcode format support (Code 128, PDF417, Aztec) and whether user-created passes get lock-screen/NFC behavior on par with developer-issued passes.
Notable Comments
@Liquid_Fire: Points out Google Wallet has supported user-created passes with any barcode for years, questioning what is actually new here.
@noio: A friend built “Pass Creator” to do this in 2012; Apple pulled the functionality shortly after – this feature has been blocked before.
