Tim Cook Wiped a Tear, Siri Got a Google Brain, and Apple Shipped a Transparency Slider. WWDC 2026, Honestly.
You know the end of a movie where the mentor character gives one last speech, the music swells, and the whole theater pretends they’re not crying? That was the WWDC 2026 keynote yesterday. Except the mentor was Tim Cook, the speech was about Apple Intelligence, and instead of riding into the sunset he handed the keys to a hardware guy and walked off stage while an arena full of developers lost it.
Then Apple announced that Siri’s brain now runs on Google.
Wild day.
Tim Cook’s Curtain Call
Let’s start here because it colored everything else. Tim Cook confirmed he’s stepping down as CEO on September 1. John Ternus — the SVP of Hardware Engineering, the guy who presented every Mac and iPhone for the last five years — takes over.
Cook’s voice cracked during the closing. He wiped a tear. The crowd gave him a standing ovation that lasted long enough to feel genuine and not performative. Say what you want about Cook’s era — the privacy stance, the services pivot, the Apple Intelligence delays — but the man ran the most valuable company on Earth for 15 years without a scandal and without losing his mind on social media. That alone deserves a slow clap in 2026.
For developers, the CEO change matters less than you’d think. Ternus is a product person, not a strategy pivot. Your Xcode project won’t notice.
Siri AI: The Google Brain Transplant
The part we all saw coming but still hit weird.
Siri is now “Siri AI” — rebuilt on a custom 1.2-trillion-parameter Gemini model that Apple is calling “Apple Foundation Models v10” internally. The ~$1 billion/year deal with Google is official. Siri queries now flow through a three-tier privacy stack: on-device first (Apple Silicon Neural Engine), then Private Cloud Compute (Apple’s servers), then Google Cloud (Nvidia B200 GPUs) for the heavy stuff. Google is contractually barred from using the data to train Gemini.
The actual product changes: Siri gets a standalone app. Persistent conversation history synced via iCloud. Multi-step commands that actually work. You can attach images and documents. It lives in the Dynamic Island as a “Search or Ask” prompt.
Is it good? The demo was impressive. But WWDC demos are always impressive. We’ve been burned before — remember WWDC 2024’s Siri promises that took 18 months to half-ship? The developer beta is available now, so we’ll know within days whether this is real or another IOU.
What matters for your app: If you followed our preflight checklist and migrated from SiriKit to App Intents, you’re already positioned. Your intents become tools that Siri AI can invoke. If you’re still on SiriKit, the deprecation clock is now officially ticking.
iOS 27 AI Extensions: The Plot Twist
This is the announcement that made me put my coffee down.
Apple is opening Siri, Writing Tools, and Image Playground to third-party AI models via a new Extensions framework. There’s a dedicated App Store marketplace for AI extensions. Users can go into Settings and swap Siri’s default AI brain from Gemini to Claude, ChatGPT, or Grok. Third-party voices too.
Apple — the company that spent a decade building walled gardens so locked down you needed a passcode to change your default browser — just let users choose their AI provider like picking a wallpaper.
The single-provider ChatGPT arrangement from iOS 18? Dead. This is an open competitive marketplace.
For developers, this is massive. You can build AI Extensions that plug into system-level intelligence features. If you’ve been building anything with Foundation Models or custom AI workflows, the distribution story just changed completely. Your model, running inside Apple’s system UI, on 1.5 billion devices.
For those of us building AI-powered tools like PromptKit — where users already manage and customize their AI interactions — this Extensions framework is basically Apple validating that users want control over their AI experience. The era of one-size-fits-all AI is ending.
Core AI Replaces Core ML
After nine years, Core ML is deprecated. Its successor, Core AI, targets the same inference hardware (Neural Engine, GPU, CPU) but is built for the generative AI era — LLMs, diffusion models, third-party model routing.
The good news: migration isn’t forced in year one. Core ML and Core AI coexist, same way UIKit and SwiftUI have cohabited for seven years. But new capabilities ship only in Core AI. The writing’s on the wall.
Core AI also includes a standardized plugin mechanism for external models, with MCP as the connector interface. This means your on-device model pipeline can talk to the same tooling ecosystem that Xcode, Siri, and every AI agent on the platform already speaks.
If you’re running classification, image recognition, or NLP models through Core ML today, start reading the migration guides this week. Not because it’s urgent, but because the migration guides are always clearest when nobody else is reading them yet.
Liquid Glass: Apple Heard You. Kind of.
Remember when we wrote about the developer community being split right down the middle on Liquid Glass? Remember the readability complaints?
Apple added a transparency slider in Settings. Users can adjust from ultra-clear to fully opaque. The refraction is more uniform, contrast is improved, icons are sharper. Sidebars expand edge-to-edge with the glass effect continuing beneath.
It’s the design equivalent of your landlord finally fixing the leaky faucet after you’ve put seventeen buckets under it and written four passive-aggressive emails.
Is the slider enough? For most apps, yes. Your Liquid Glass migration work stays valid, but now users who hate the transparency can dial it down without you writing custom escape hatches. If you followed our migration guide, you’re fine. If you used UIDesignRequiresCompatibility as a permanent crutch, this is your sign to actually migrate.
Xcode 27: Your IDE Speaks MCP Now
Xcode 27 ships with dual AI engines — a local Apple Silicon model for code and documentation suggestions, plus cloud offloading to OpenAI and Anthropic models out of the box. Twenty tools exposed via a new mcpbridge binary. Claude and Codex agents can create files, trigger builds, run tests, capture Xcode Previews screenshots, and pull Apple documentation — all through MCP.
This is what we predicted when Apple announced MCP support, but the execution is more aggressive than expected. Xcode isn’t just adding AI features — it’s becoming an MCP server that any compliant agent can drive.
The developer tools wars are getting interesting. Cursor and Claude Code aren’t competing with Xcode anymore. They’re plugging into it.
homeOS: The Surprise
Apple previewed homeOS — a new operating system for the upcoming HomePad, a 7-inch display with an A18 chip designed as a smart home hub. FaceTime without an iPhone. Expanded HomeKit and Matter APIs. The OS ships before the hardware so developers can build now.
Nobody predicted this as a keynote-worthy announcement. But if you build anything in the home automation space, you just got a new platform to target.
The Bottom Line for Your Codebase
Here’s the honest punch list from yesterday, sorted by urgency:
- Download the iOS 27 beta today. Test your app. Liquid Glass slider means fewer visual surprises, but test anyway.
- Finish your SiriKit → App Intents migration. The deprecation is official. Your intents are now Siri AI tools.
- Read the Core AI migration guide. Not urgent, but the window of low competition for early adoption is now.
- Explore AI Extensions. If your app has any AI-powered feature, the Extensions framework might be a distribution channel you didn’t know you needed.
- Check your MCP surface area. Between Xcode 27 and system-wide MCP, your tooling integrations are about to multiply.
And if you haven’t yet, go through our SwiftUI and iOS development courses — the Foundation Models, App Intents, and concurrency modules map directly to what just became official at WWDC.
Yesterday was a lot. Tim Cook said goodbye, Siri learned to think, and Apple admitted that maybe — just maybe — a transparency slider would’ve been nice from the start.
Now go download that beta before the servers melt.
Share this post
Comments
Leave a comment
NativeFirst Team
EditorialThe NativeFirst team — engineers and designers building native Apple apps and writing the courses we wish we had when we started.