WWDC 2026 was today. Tim Cook's last as CEO, Craig Federighi on stage talking about platform improvements, trust, and safety — and somewhere between the homeOS preview and the AI announcements, iOS 27 confirmed what became obvious pretty early in the 26.x saga: the Liquid Glass slider is real, it's coming, and it arrives in the same release that removes the ability to opt out of Liquid Glass entirely.
I wrote in April that you'd get the knob to turn it down at the exact moment they took away the switch to turn it off. That post went up fourteen weeks ago. Today Apple confirmed it on stage. Verbatim.
For anyone who's lost track of the version history: 26.1 brought a toggle — Clear or Tinted, that was the full extent of your control. 26.2, 26.3, nothing. 26.4 buried two more options in Accessibility menus. 26.5 shipped. No slider. Apple's official explanation was "engineering challenges," which is accurate in the specific sense that they built Liquid Glass so deeply into the OS rendering pipeline that threading a simple intensity variable through thousands of UI components without breaking things took the better part of a year. I'd already built a glassmorphism slider in Flutter on the evening of August 11th — well before the toggle even landed in October — and had been waiting to become redundant ever since. The challenge was never the slider. It was the architecture underneath it.
That same rendering pipeline has been doing other things while we waited. In April I wrote about what happened to the háček character — quietly dropped from the lock screen keyboard somewhere between iOS 18 and 26.4, locking at least one user out of his device after an update. His passcode had it. He updated. The character was gone. That regression survived every internal QA gate, every beta, every point release — right up until a 21-year-old's Reddit post caught what Apple's entire review process didn't, and a fix arrived nine days later. Same root cause as the slider: a visual overhaul whose architectural debt kept surfacing in places nobody thought to check.
The slider is genuinely welcome and the opt-out going away was always inevitable once Apple held that developer workshop in New York and made clear the design wasn't going anywhere. iOS 27 as a stability-focused release is the right call. None of that changes what it took to get here, or what's leaving with it.
Then there's the other thread WWDC closed today, which I ended a post on four days ago with "I'll be watching what they say — and more importantly, what they don't."
The new Gemini-powered Siri — now with a standalone app, a new swipe-down interface, Visual Intelligence baked in, and multi-step task execution — runs on a three-tier routing system: simple requests stay on-device on Apple's own models, mid-complexity queries go to Apple's Private Cloud Compute on Apple Silicon, and the heaviest reasoning tasks route to Nvidia Blackwell B200 GPUs on Google Cloud — something I reported on May 19th that today stopped being a rumor. Apple didn't specify on stage exactly what lands where, which means you're trusting a routing decision you can't see to determine when your queries leave Apple's infrastructure entirely. Craig Federighi said in 2024 that it was "essential for privacy and security" that Apple Intelligence use only Apple servers. He was on stage this morning talking about trust and safety. The 2024 quote didn't come up.
iOS 27 also introduces Extensions — a third-party AI marketplace letting you set Claude, ChatGPT, Gemini, Grok, or Perplexity as your default across Siri, Writing Tools, and Image Playground. It's genuinely more user choice than Apple has historically offered, and probably not coincidentally a tidy answer to the EU's ongoing questions about lock-in. But the architecture questions Apple didn't answer today are the ones that actually matter. Does a request go straight to your chosen provider, or does it still route through PCC — and potentially Gemini — before being handed off? What's the capability scope: does an extension get full App Intents access to your email, calendar, and device state, or does it receive a query and return a response, which is a very different product that mostly competes with opening a browser tab? If an extension does get elevated system access, what does the install prompt actually tell you in plain language, and does granting that access mean Apple's local-first routing logic gets bypassed entirely — the scenario where the privacy-conscious choice ironically becomes the less private one? Someone who specifically chose Claude or Perplexity to stay out of Google's infrastructure would probably like to know whether their non-trivial requests are still hitting Gemini anyway before getting handed off somewhere else.
And that's before the longer-term question of whether AI providers will build these extensions in any meaningful depth at all. Apple Watch had a gold rush moment that most developers quietly walked back once the economics didn't hold up — the design constraints, the separate testing matrix, the limited ceiling of what the thing could actually do. Extensions add their own version of that calculus: App Intents declarations that have to stay current, privacy manifests that keep expanding their required scope, permissions models that shift with every major release, entitlements that can change in a point update and silently degrade your integration if you haven't kept up. And today Apple formally deprecated SiriKit — the Siri integration framework that's been in place since 2016 — giving developers two to three years to migrate their existing voice features to App Intents before they stop working. Worth sitting with: SiriKit dying means every meaningful app-level Siri interaction routes through the new pipeline, and that pipeline has hardware requirements. Devices without Apple Intelligence support don't get the new pipeline in any real sense. If Apple's Watch purge is any precedent — four generations dropped at once, no warning, no explanation — the question of when we see a similar reckoning on iPhone isn't really an if. It's a when. So developers aren't just deciding whether to invest in a new Extension; they're simultaneously being asked to rebuild their existing Siri integration from the ground up on the same framework, on the same timeline. That's two migration costs landing at once, for a surface that — if the capability ceiling is "answer general questions" — isn't moving the needle on anyone's actual business metrics. The AI companies with their own standalone iOS apps have a specific reason to underinvest here that Watch developers didn't even have: a deep capable extension that lets users do everything without opening the standalone app is actively against their interests.
By the way — Apple also announced that Siri AI won't be available in the EU on iPhone or iPad at launch, citing DMA requirements that would force them to give third-party AI systems nearly unlimited device access, which Apple characterized as a security risk. It will be available on Mac and Watch in the EU, because those platforms aren't designated DMA gatekeepers — so the regulatory argument is at least internally consistent there. What isn't consistent: Extensions gives third-party AI systems device access with user permission on the same iPhone Apple says can't do that safely under DMA terms. Either Extensions are more capable than implied, which directly contradicts the EU security argument; or Extensions are more limited than implied, which means "pick your AI" is mostly cosmetic and Siri's Google Cloud dependency is the only path to anything that actually matters. Apple hasn't specified which. At this point that's almost an answer.
Here's the part that didn't make the keynote slides. The most powerful on-device Siri model — the one that keeps your heaviest queries local rather than pushing them up the tier chain — requires 12GB of unified memory. That means iPhone 17 Pro and Air minimum. The base iPhone 17 ships with 8GB and doesn't make the cut. Neither does anything in the 16 series. Neither does the 15 Pro.
This is the third time Apple has moved the goalpost on the same promise to the same customers. WWDC 2024: private, on-device AI is coming, and it's going to be different. iPhone 15 Pro launch: this is the Apple Intelligence phone, A17 Pro required, here's your entry ticket. iOS 27: actually the most capable on-device model requires 12GB, and the 15 Pro owner who bought in specifically for Apple Intelligence is now on the cloud-dependent tier they thought they'd cleared. The 16 Pro owner who thought they had runway left is there too. The ratchet moves, the previous top tier becomes the new lower tier, and the goalposts are always exactly one hardware generation ahead. Whether the 12GB threshold is a genuine technical requirement or a line that maps conveniently onto the product tier Apple wanted to differentiate is a question only Apple can answer honestly. What's not a question is what it means in practice: the people who bought for privacy got more cloud.
The new Siri also arrives free — with daily usage limits. Heavier features have caps, iCloud+ unlocks more usage, and iCloud+ now also gates AI features for your compatible Home security cameras. The subscription is right there one tap away at the exact moment of maximum enthusiasm and minimum skepticism, for people who've been waiting two years for this and are finally holding the download button. That's not a coincidence. That's a conversion funnel positioned at the emotional peak of "I finally have the thing."
Speaking of which: the developer beta dropped today. Siri AI is technically in it — as a waitlist button. Open Settings, find the new Siri menu, tap Join Waitlist, wait for Apple to notify you. The new app is there. The swipe gesture works. The Dynamic Island has its new animation. And where the actual intelligence should be, there's a queue. Apple will likely open that queue broadly to all compatible devices — but getting in probably means the new interface running over a conservative initial capability set while Apple watches how the system behaves at scale. Gemini-powered personal context access means reading emails, calendar, messages, taking cross-app actions — there are a lot of ways that goes sideways fast. One viral screenshot of Siri confidently hallucinating something from someone's personal data, or autonomously taking an action someone didn't intend, and the narrative Apple spent this morning building collapses immediately. They have a settlement in the background as an expensive reminder of what happens when AI promises get ahead of AI reality, the EU is watching every move, and Federighi listed trust and safety as a top three priority this morning for a reason. The real capability expansion is probably a slow dial turning up through 27.1 and 27.2 as each piece proves stable at scale. The responsible way to do it. Just not the way it was sold.
One more thing that slipped by without much scrutiny: Apple Intelligence can now autonomously navigate to websites and change your compromised passwords for you, saving the new credentials to the Passwords app. On the surface, genuinely useful. Underneath it, a fairly clean example of how agentic AI creates its own security risks. The most documented attack vector for AI agents doing autonomous web browsing is prompt injection — malicious content on a webpage that hijacks the agent's instructions mid-task. An AI navigating to change your password and encountering content designed to manipulate it mid-action is not a theoretical concern, it's a known category of attack that security researchers have been writing about for two years. And that's before the quieter problem: if you primarily live in Vaultwarden, LastPass, Dashlane, or any other third-party manager but have stale entries in Apple Passwords — an accidental save here, an iOS prompt you tapped through there — Apple Intelligence sees those as compromised passwords to fix. It changes them on the websites. Saves the new ones to Apple Passwords. Your actual vault now has wrong credentials and you find out when you get locked out. Whether the feature prompts you first or acts on behavior signals automatically, Apple hasn't clearly specified. Either way, the new password only goes back to Apple Passwords. If your real vault lives somewhere else, the "fix" just created a split that's on you to notice.
Oh — and while all of that was happening, watchOS 27 quietly dropped support for the SE 2, Series 6, Series 7, Series 8, and the original Ultra. No slide. No explanation. Craig didn't mention it. A compatibility page updated — initially with errors that had people believing even more devices were affected before Apple confirmed Series 9 and later are supported — and that was that. The SE 2, Series 8, and Ultra 1 are 2022 hardware, three years old, cut without technical justification and without advance warning. Just a webpage. Just a Monday.
Good faith. Still the phrase.
Find me on Mastodon at @ppb1701@ppb.social.