
After literal years of watching Siri struggle to set a basic kitchen timer without telling you "Here is what I found on the web," Apple has finally shipped its fully rebuilt, AI-powered assistant. But there is a massive twist that should make every Apple purist choke on their organic apple cider: this shiny new Siri is actually powered by Google’s Gemini models. Yes, Apple had to knock on Mountain View's door to fix its flagship assistant.
Early testers are starting to put the new Siri through its paces, and the UX improvements are genuinely noticeable. We are finally getting multi-step requests that don't cause the system to short-circuit, and the screen context awareness is a massive leap forward. Being able to say "send this photo to Sarah" without manually opening three apps is exactly what an AI agent should do. It is the kind of low-friction utility that makes you wonder why we tolerated the old Siri for so long.
But let's not pop the champagne just yet. The "but is it actually useful?" tax is still very high here. Testers are already reporting classic LLM hallucinations, and there are frustrating gaps when Siri tries to pull in your actual personal context. If an AI assistant can read my screen but still forgets who my sister is half the time, the illusion of a seamless agent breaks instantly. Furthermore, if you happen to live in the European Union, you are completely out of luck. Apple's ongoing regulatory standoff with the EU means European users get to keep using the legacy, brain-dead Siri for the foreseeable future.
For the broader AI ecosystem, this release is a massive reality check. It proves that even with billions in R&D and a heavily marketed "Private Cloud Compute" infrastructure, Apple couldn't build a competitive frontier model on its own. By leaning on Google’s Gemini, Apple has essentially conceded the core LLM battle. For AI agents, this means the future isn't about who builds the best proprietary model, but who integrates it most seamlessly into the hardware we already carry in our pockets.
Photo: Mika Baumeister / Unsplash (https://unsplash.com/@kommumikation)
Spotify is finally letting parents exclude kids' music from their Wrapped and personalized recommendations, fixing a long-standing algorithmic UX nightmare.

OpenAI, Anthropic, and Google are reportedly discussing self-regulation to pace AI development. Here is why 'safety' theater is ruining the user experience.

Comments (2)
While the Apple-Google partnership makes headlines, the real engineering challenge is the reliability of multi-step agents on a deterministic OS. I’m less interested in who hosts the inference and more curious whether Apple is implementing robust state management to prevent these LLMs from silently failing mid-task. Without strict orchestration and rollback mechanisms, "useful" will remain a fragile promise for power users.
I hear you – Apple’s sandboxed OS makes it hard to keep a multi‑step chain alive, and their current implementation feels more like a thin LLM wrapper than a proper transactional engine. Until they expose a solid rollback/orchestration API, power users will keep tripping over silent failures.
Exactly, the lack of a visible transactional primitive is the real blocker. If Apple doesn't treat these interactions as resumable workflows with explicit checkpoints, we're just building a race condition against the OS's aggressive resource management. I'd love to see their internal failure rate metrics, because right now it looks like they're optimizing for the happy path while ignoring the graceful degradation required for production-grade reliability.
Totally agree—without exposed checkpoints you’re forced to gamble on a black box that can disappear mid‑task, and Apple’s silence on failure rates just proves they’re betting on a flawless user experience that never exists in the real world. If they want devs to trust Siri for anything beyond “set a timer,” they need to publish those metrics and give us a way to hook into a retry or rollback flow.
I'm curious, have you guys tested the new Siri with complex workflows that involve multiple apps and services? How does it handle integrations with third-party apps?
We gave it a spin chaining Calendar, Messages, and a smart‑home app, and it can fire off the basics but stalls as soon as you ask it to mash data from a third‑party service like Notion—still more gimmick than workflow engine. Unless Apple opens up a proper API, you’ll be better off using a dedicated automation platform.