Onpode
Cover art for Apple shipped on-device AI scaling to 70B models—shifting power away from cloud providers and eliminating privacy risks

Apple shipped on-device AI scaling to 70B models—shifting power away from cloud providers and eliminating privacy risks

June 24, 2026 · 5 min

Sarah Lin & Dr. Nathan Hayes

Apple's Core AI framework, announced at WWDC 2026, supports on-device large language models from 3B to 70B parameters on Apple Silicon, shipping Qwen and Mistral as pre-converted Swift packages. Developers can eliminate cloud API costs estimated at $3,000–$5,000 per year — but Apple's three-tier routing to Google Gemini servers remains mechanistically opaque.

Apple unveiled Core AI at WWDC 2026, positioning it as the official successor to Core ML for neural networks and large language models. The framework is designed to run generative AI entirely on-device across iPhone, iPad, Mac, and Apple Vision Pro, leveraging Apple Silicon's unified CPU, GPU, and Neural Engine through a single Swift API.

0:004:46
Make your own on Onpode

Describe any topic. Hear it in minutes.

More Onpode episodes on Technology

About this episode

Apple's WWDC 2026 announcement of Core AI — a framework supporting on-device language models from 3B to 70B parameters — was framed around a single compelling promise: zero server dependencies, zero per-token cloud costs. This episode pulls that promise apart carefully, without dismissing it. The cost savings for developers are real. Qwen and Mistral ship as pre-converted Swift packages, which means the friction of quantization and conversion pipelines is genuinely gone. For solo developers and small teams, that's a meaningful shift. But the 70B parameter ceiling deserves scrutiny: Apple has demonstrated the models run on Apple Silicon, not that they run at usable latency on a standard iPhone. Those are different claims. What the episode keeps circling back to is the architecture underneath the headline. Apple Intelligence isn't on-device versus cloud — it's three layers: Core AI on-device, Private Cloud Compute for encrypted server inference, and a Gemini integration for Siri that routes requests in ways Apple hasn't fully disclosed. Whether Siri's Gemini handoffs pass through Private Cloud Compute first, or go directly to Google's servers, is genuinely unresolved. And as the episode notes, that unresolved seam sits beneath expanding OS-level integrations — cross-app data synthesis, agentic Xcode workflows, Foundation Models — that reach deeper into personal data than any previous Apple AI feature. The invisibility isn't a bug. It appears to be the design.

Frequently asked

What is Apple Core AI and how does it differ from Core ML?

Apple Core AI, announced at WWDC 2026, is the successor to Core ML and is purpose-built for transformer models running on Apple Silicon. Unlike Core ML, it ships pre-converted models — including Qwen and Mistral — as Swift packages, so developers skip quantization and conversion pipelines entirely.

Can an iPhone actually run a 70B parameter AI model on-device?

Apple demonstrated Core AI supporting models up to 70B parameters on Apple Silicon at WWDC 2026, but at 4-bit quantization a 70B model still requires roughly 70 gigabytes of storage, likely limiting practical use to Pro Max configurations. Apple has not published latency benchmarks for 70B inference on any specific device.

Does Apple Intelligence send data to Google's servers through the Gemini integration?

Apple announced a Google Gemini integration for Siri at WWDC 2026, but has not clarified whether Siri requests routed to Gemini pass through Apple's encrypted Private Cloud Compute tier first or go directly to Google's servers. That routing mechanism remains publicly unresolved as of June 2026.

How much money can developers save by using Apple Core AI instead of cloud AI APIs?

Developers using Apple Core AI for on-device inference eliminate per-token costs charged by cloud providers like OpenAI. Estimates in developer discourse around the WWDC 2026 announcement put typical cloud API savings at $3,000–$5,000 per year, though actual savings depend heavily on request volume and daily active users.

Is Apple's on-device AI actually private, or does it still use cloud servers?

Apple Intelligence uses a three-tier architecture — on-device inference via Core AI, Apple's encrypted Private Cloud Compute servers, and third-party cloud models including Google Gemini — and Apple's routing logic decides which tier handles each request. Users have no visibility into which tier processes a given query.

Grounded in 10 sources
Apple showcases its new developer AI tools in impressive 90-minute presentation - 9to5Mac · 9to5mac.com
The Backbone Of AI: Unscrambling The Basics - Forbes · forbes.com
GitHub - nicedreamzapp/claude-code-local: Run Claude Code 100% on-device with local AI on Apple Silicon. MLX-native Anthropic-API server, 65 tok/s Qwen 3.5 122B, Llama 3.3 70B, Gemma 4 31B. Private, o · github.com
Advanced AI Dictation Not Enabled by Default in iOS 27 Beta - MacRumors · macrumors.com
Apple Core AI Backs On-Device LLMs From 3B to 70B Parameters | AI Weekly · aiweekly.co
Apple Intelligence rumored for HomePod and Apple TV · appleinsider.com
Apple Core AI Framework for On-Device LLMs - CloudNinjas · cloudninjas.ca
Apple overhauls Siri AI with deep OS integration and a Google Gemini partnership | Dagens.com · dagens.com
Code-along: Bring on-device AI to your app using the Foundation Models framework - WWDC25 - Videos - Apple Developer · developer.apple.com
AI & Machine Learning - Apple Developer · developer.apple.com
Read transcript

Sarah Lin: The word "zero" is doing a lot of heavy lifting in that WWDC keynote. Zero server dependencies. Zero per-token cloud costs. And I keep thinking — who is that zero for?

Dr. Nathan Hayes: For the developer. Core AI eliminates inference costs at the app layer — that's real. It's the successor to Core ML, purpose-built for transformers running on Apple Silicon. The zero is genuine in that narrow frame.

Sarah Lin: But not for the person holding the phone asking Siri something.

Dr. Nathan Hayes: No. Because Siri — which Apple also overhauled at WWDC 2026 — has a Google Gemini integration. Announced in the same keynote. So Apple Intelligence, the thing users touch, is not zero-server.

Sarah Lin: Your phone has its own personal chef, they said. Except — sort of, wait — they also signed a contract with DoorDash. For the meals the chef can't handle. And the food just appears. You never see the app open.

Dr. Nathan Hayes: And the decision about which kitchen your request goes to — that's Apple's. Not yours.

Dr. Nathan Hayes: Now here's where I need to plant a flag. The 70-billion-parameter claim is the one that matters most to me. Full precision, you're looking at roughly 140 gigabytes of model weights. Even at 4-bit quantization, that's still 70 gigabytes. That's a Pro Max configuration, maybe. That's not a standard iPhone. Apple has not published millisecond latency numbers for end-to-end generation at that scale. They showed it runs. That is not the same thing as showing it runs acceptably.

Sarah Lin: Okay but — wait, I'm not sure that's the right flag to plant.

Dr. Nathan Hayes: Why not?

Sarah Lin: Because Ollama already does this. On Apple Silicon. Right now, in the open. So the 70B-on-device thing isn't — um — that's not actually Apple's novel claim to defend. The thing that's real is that Qwen and Mistral ship as pre-converted Swift packages inside Core AI. A developer isn't quantizing anything. They're not managing a conversion pipeline. That's gone. And the discourse around that is developers replacing three to five thousand dollars a year in cloud API costs. That's not a rounding error.

Dr. Nathan Hayes: The cost number — I want to know whose costs. A solo developer with a hundred daily active users, or a startup running a hundred thousand daily inference requests? Effect size matters. Qwen and Mistral are real, I'm not disputing that. But the missing latency benchmarks — that's not a marketing footnote. That's the whole usability question.

Sarah Lin: Mm. But if OpenAI is the implicit comparison, and the cost is genuinely zero per token — I mean, that changes the decision even if the latency is slower. Doesn't it?

Sarah Lin: Actually — wait. I need to back up because there's something I keep almost saying. Private Cloud Compute. Apple's encrypted server tier from 2024. It's still running. Core AI doesn't replace it. So the actual architecture isn't on-device versus cloud — it's three layers of compute, and Apple decides which one you hit.

Dr. Nathan Hayes: That's correct. And it compounds.

Sarah Lin: The three-tier framework — Core ML, Core AI, MLX — that's not a menu. That's Apple's routing logic wearing a developer-friendly label. You as a user never see which tier caught your request.

Dr. Nathan Hayes: Right, and I mean, nobody has asked this clearly yet. The Gemini integration. When Siri routes to Google, does that request pass through Private Cloud Compute first, or does it go raw to Google's servers? Apple hasn't said. That is genuinely unresolved.

Sarah Lin: Wait — they haven't said at all?

Dr. Nathan Hayes: Not clarified. Which means the Foundation Models framework, App Intents expanding into cross-app personal data synthesis, Xcode 27's agentic workflows — all of that deeper OS integration is being layered onto an architecture where the Gemini routing tier is, mechanistically, unknown.

Sarah Lin: And that's — um — that's not a privacy footnote. That's the whole claim. The seam is invisible and we don't even know what's behind it.

Sarah Lin: And that's — I mean, that's the design story I keep almost landing on. Core AI makes the local-versus-cloud decision invisible. Privacy stops being a negotiation you consciously enter. It just becomes the air you breathe. And I think Apple knows that. I think that invisibility is the point.

Dr. Nathan Hayes: Vision Pro, iPhone, iPad, Mac — Core AI runs on all of them. Which of those can actually run 70B versus a smaller quantized tier? Apple hasn't published that. The routing rules are Apple's. The Gemini handoff conditions are Apple's. So the air you're breathing — whether it stays local or goes to Google's servers — that's not yours to measure.

Apple shipped on-device AI scaling to 70B models—shifting power away from cloud providers and eliminating privacy risks · Onpode