On September 14, iOS 27 shipped with Featured Actions enabled for every pass type in Apple Wallet — coupons, store cards, museum memberships — not just the event tickets that got them first. Three weeks later, the top link on Hacker News this morning is Apple’s documentation for Pass Designer, the macOS app announced at WWDC 2026 that lets you draw a Wallet pass visually instead of hand-editing JSON. Five hundred and thirty-eight points, 320 comments, and most of the argument is about whether it should have been a web app.

That is not the argument. The argument is being avoided, politely, by the only people with real money on the line.

The Moat Was Never the Renderer

Consider the pipeline Apple now owns end to end. Design: Pass Designer, a WYSIWYG editor with a true-to-iOS rendering, in beta on macOS 27. Signing and distribution: Pass Builder, a new Swift-on-server package that turns a template into a signed, personalized pass. Display: the iOS 27 Featured Actions expansion, which puts action tiles on everything, declared at the top level of pass.json. The second-generation event ticket arrived back in iOS 18; as of last month, the whole format got the upgrade.

Now read the incumbents’ response. Passcreator, a pass-platform vendor, told its own customers it would “develop an import function for this in Passcreator.” PassKit, a competitor, wrote that Pass Designer “sends an important signal to organisations evaluating their digital wallet strategy.” These are roadmap notes. They are also, functionally, surrender documents written in the tone of a support article. Nobody is angry, which is the whole story.

Here is why nobody is angry. Designing a pass was never a business. It was a feature: a zip file of signed JSON, a logo, a background image, and a key. The actual money in that market lived one layer up — the campaign calendar, the segmentation rules, the CRM sync, the analytics dashboard a marketing director opens on a Tuesday morning and never closes. Apple took the cheap layer and, conspicuously, left the expensive one alone.

That is a more disciplined Sherlock than the one the industry usually gets. This time Apple didn’t touch customer data, integrations, or service contracts. It took the part of the stack where the margin was already thin and the support tickets were already thick.

A product manager at a rival pass vendor, waiting out a delay at a gate in Terminal B, put it more bluntly than any press release would: “We’re all just building a nicer PDF now. The renewals are what we’re actually defending.”

Everyone is fixating on the editor. The editor is cosmetic. The consequential change is that a pass is no longer a document.

A boarding pass, a loyalty card, and a 20-percent-off coupon now render on the same surface, with the same action tiles, under the same signing authority, looking equally official. Apple spent a decade training people to trust that surface — to keep a boarding pass there because it is the one thing on the phone that cannot be a phishing link. Handing every merchant the same visual authority is a decision about credibility, and credibility is the asset.

So the design tool is not a convenience. It is the on-ramp. Once design is free and distribution is a Swift package, the only remaining question for a mid-size retailer is why they would pay a vendor for the renderer at all. The answer, increasingly, is that they wouldn’t — and the vendors know it, which is why their public statements are aimed at retention rather than at Apple.

The comfortable right-of-center reflex here is that Apple built the platform, so Apple may build the tools. Fine. But a platform’s value is the trust embedded in it, and Apple is spending that trust on behalf of every pizza chain with a marketing budget and a template. You can defend the property right and still notice the bill is being paid by the thing that made the property valuable.

The Fight Was Over the Wrong Door

For years, the loudest regulatory argument about the iPhone and mobile payments concerned whether rival wallets could reach the NFC chip. That fight assumed the gate was the hardware. It wasn’t.

The pass format is already open. It is a documented, signed bundle that anyone can generate, and Apple has never seriously pretended otherwise. There is almost nothing to regulate in the renderer, which is precisely why this is interesting: the competitive advantage was never the specification. It was the surface, the signing chain, and a decade of developer muscle memory about which tool to open first. A regulator can pry open a door. It cannot make anyone walk through it.

So who has to revise their priors? Three groups.

First, the pass-platform vendors, who spent a decade describing themselves as design-and-delivery companies when they were customer-data companies with a renderer bolted on — and whose own blog posts just admitted it in the passive voice.

Second, the antitrust crowd, which litigated a gate that Apple has now routed around with a free app and a server-side package. Opening a door is a strange win when the tenant has already moved to a different floor.

Third — and this is the one that should sting a little — anyone who believed a beautifully branded loyalty pass was a moat. It was a template. Apple just gave the template away, and the branding was never the hard part.

The consolation for the vendors is that a real business remains. It is the boring one: campaigns, compliance, integrations, the renewal call, the ugly dashboard nobody screenshots. Apple didn’t take it. Apple just made sure nobody could charge a premium for the part in front of it.

That is what a platform looks like when it finishes a decade-long project. The last mile is always the one that looks like a convenience.

Sources