Apple adds 'Create a Pass'
- Apple is reportedly adding a “Create a Pass” tool to Wallet in iOS 27, letting iPhone users build their own digital tickets and memberships. (bloomberg.com) - The key detail is that Wallet would accept a scanned QR code or manual entry, then wrap it in Apple-styled pass templates. (macworld.com) - That matters because Wallet has long depended on merchant integrations, leaving many gyms, venues, and local businesses outside the system. (developer.apple.com)
Apple Wallet looks like it’s getting a lot less picky. The reported new feature is called “Create a Pass,” and the idea is simple — if a business gives (bloomberg.com)a bigger shift than it sounds. Wallet has spent years being useful mainly when a company did the integration work first. (blo([macworld.com)passes-in-wallet-app)) ### What is Apple adding? Apple is preparing a Wallet feature that would let users create custom digital passes for thi(developer.apple.com)en described as a new option inside Wallet’s add-card flow, with support for scanning a QR code or building a pass from entered details. (bloomberg.com) ### Why is that a real change? Wallet already handles a lot of things well — boarding passes, event tickets, payment cards, keys. But it usually (bloomberg.com)enues, school passes, punch cards, and all the random QR-based systems that never became proper Wallet items. (developer.apple.com) ### How would it actually work? The reported flow is pretty direct. You tap to add something in Wallet, choose the new pass-creation option, then (bloomberg.com)rt ticket and a gym card do not need the same layout or fields. (macworld.com) ### Why does the QR code part matter so much? Because QR codes are the fallback system of modern commerce. Tons of businesses already issue them for entry, check-in, rewards, or redemption, but they stop there. They do(developer.apple.com)at dead-end QR code into something native-feeling on the iPhone. (digitaltrends.com) ### What problem is Apple really solving? The gap is merchant adoption. Apple launched Passbook back in 2012, and the underlying PassKit framework ha(macworld.com)ets. But the long tail of businesses never implemented it. So Wallet became polished, but uneven — great for airlines and major brands, spotty everywhere else. (developer.apple.com) ### Does this replace existing Wallet integrations? Probably not. Official passes still do more. They can update live, refl(digitaltrends.com)pper — useful, cleaner, and easier to find than a screenshot, but not the same as a deeply integrated ticketing system. That last part is an inference from how Wallet passes already work and from the feature’s reported focus on unsupported businesses. (developer.apple.com) ### Why should developers and merchants care(developer.apple.com)o Wallet. But bigger merchants may need to offer more than “here’s a QR code” if they want their passes to feel premium. In other words, the baseline experience rises, and official integrations have to justify themselves with updates, branding, and automation. (passkit.com) ### So what’s the bottom line? This looks like Apple admitting that Wallet’s biggest weakness was never design — it was dependency. “Create a Pass” would let Apple fill the gaps itself, one user-made pass at a time. If i(developer.apple.com)you actually use. (bloomberg.com)