The announcement gets buried under the Gemini headline. Apple introduced a new Siri AI at WWDC 2026, and the licensing deal with Google, reportedly around $1 billion per year for a model with approximately 1.2 trillion parameters, per Bloomberg’s reporting, pulled all the oxygen in the room. What didn’t get the same attention: SiriKit is reportedly being deprecated.
That’s a concrete migration requirement for any iOS developer who built voice integrations in the last decade using Apple’s existing framework.
App Intents is now the mandatory path, according to multiple developer-focused reports covering the WWDC announcement. SiriKit’s intent domains, messaging, media playback, ride booking, payments, and others, need to be rebuilt in the new framework. Existing SiriKit integrations don’t automatically port over. They break.
Apple’s WWDC announcement frames the shift as a capability upgrade, and technically it is. App Intents gives developers access to the new three-tier processing architecture Apple describes for Siri AI: on-device processing through Apple Foundation Models Core, private cloud processing through Apple’s Private Cloud Compute framework, and Google Cloud handling queries that exceed on-device and PCC capacity. The architectural intent is that user data stays on-device for most requests and routes to PCC only when necessary, with Google Cloud as the stateless fallback.
Unanswered Questions
- Which specific SiriKit intent domains require mandatory migration, and on what timeline?
- What is the exact Small Business Program download threshold for free cloud API access, has Apple confirmed this in developer documentation?
- Which user query types route on-device vs. PCC vs. Google Cloud, and what does this mean for app privacy disclosures?
- Is the third-party Extensions system (Claude/Gemini/ChatGPT choice) available at WWDC launch or targeting iOS 27?
The catch is that developers building privacy-sensitive apps now have a decision to make. Your app’s privacy posture under the old SiriKit model doesn’t automatically transfer. You need to understand which of your user queries will route on-device, which will route to PCC, and which will route to Google. Apple describes this routing architecture in its WWDC materials, but the specific routing logic for different intent categories requires verification against developer documentation before relying on it in privacy disclosures.
On the free-tier question: Apple reportedly offers free cloud API access for developers in its Small Business Program who meet certain download thresholds. The specific figure cited in multiple reports is under two million downloads. That number hasn’t been independently confirmed against Apple’s Developer documentation, so don’t build your cost model around it yet. Check the Apple Developer portal directly before making any pricing assumptions.
There’s also a timing wrinkle for EU developers. Apple’s EU market rollout is reportedly delayed to fall 2026 due to DMA compliance considerations. Developers building for EU-market releases need to account for that timeline when planning migrations and feature launches.
One more reported capability worth flagging: an Extensions system that would let users choose third-party AI models, Claude, Gemini, ChatGPT, as their default Siri backend. MacRumors’ coverage references iOS 27 in this context, which may mean this feature lands in a future OS release rather than immediately. Verify availability timing before planning integrations around it.
Warning
The free cloud API tier for Small Business Program developers carries unverified specifics. The under-2M-download threshold appears in multiple reports but has not been confirmed against Apple Developer documentation. Cost models built on this figure before official confirmation carry real financial risk.
The part nobody mentions
in the Gemini licensing coverage: the negotiating leverage in this deal sits with Google. Apple is licensing a 1.2 trillion parameter model, per Bloomberg, for cloud processing that iOS devices can’t handle on-device. That means Apple’s privacy-first framing depends on a commercial relationship with a company whose core business is data. Developers and enterprise mobile teams deploying apps that handle sensitive data should read the PCC architecture documentation carefully and audit what actually routes to Google Cloud versus stays on-device.
Don’t migrate your SiriKit integrations based on secondary reporting alone. Get to Apple’s developer documentation and confirm the specific intent categories that are affected, the timeline, and the actual Small Business Program threshold. Those details carry real cost and engineering implications.