iOS 27 turns the iPhone into an agent platform you can build for in an afternoon: expose your data as App Intents + Spotlight entities, let new Siri / Apple Intelligence act on it, and run private LLM reasoning on-device with the Foundation Models framework — no server, no per-token cloud bill.
Apple's pitch for iOS 27 is that you stop building screens and start building structured access to data + actions. A thin native app that (1) pulls a data source you care about, (2) declares it as App Entities into the Spotlight semantic index, and (3) exposes App Intents for actions, becomes something new Siri and Apple Intelligence can reason over and operate — conversationally, on-screen, hands-free.
For a solo builder using Claude Code as the executor, this collapses the cost of "I wish my phone could just do X with my data" from a project to an afternoon. The catch (per the field reports below): Siri's source selection is still brittle — getting the entity/intent descriptions and indexing right is the actual work, not the Swift.
The second catch — surfaced by the Kris Puckett tweet below — is the ingestion layer: most of the data you'd want to expose lives behind a messy API, or behind no API at all. That's where Printing Press (printingpress.dev) fits: it prints a token-efficient agent-native CLI / skill / MCP server (often backed by a local SQLite mirror) for an arbitrary API, app, or site. So the full pattern is connector → adapter → assistant: Printing Press makes the data reachable, Claude Code wires it into App Intents + Spotlight, and iOS 27 turns it into a Siri/Spotlight surface.
How this pack was built, so the reasoning is auditable.
Two Apple dev features were flagged: the Foundation Models framework and App Intents. Used as the entry point for what to dig into.
Read Apple's own developer docs and "What's new" pages (Apple Intelligence, Foundation Models, App Intents, Image Playground, Visual Intelligence, ML, iOS, SwiftUI). These set the factual floor.
Max Weinbach's thread + replies on "vibe-building a Siri adapter app." Adds a practitioner's read on what actually works today and where it's brittle.
Crossed the new capabilities against Ananth's real surfaces (Tesla, Mission Control, health, SMB/sales, finance) to produce ranked, buildable ideas.
Eight capability shifts, each grounded in an Apple page. The first two are the engine of the whole "adapter" pattern.
A native Swift API giving direct access to Apple Foundation Models — on-device and in Private Cloud Compute — plus any provider that ships a Swift package conforming to the LanguageModel protocol.
Includes: multimodal prompts; on-device Vision tools so the model reasons about images alongside text; Dynamic Profiles to swap models/tools/instructions mid-session; and an Evaluations framework to test reliability across conditions.
Why it matters: private inference with no per-token cloud bill, and a clean way to plug in your own/3rd-party models behind one API.
Connects your app to Apple Intelligence and Siri through schemas. Entity schemas contribute your content to the Spotlight semantic index for personal-context understanding; intent schemas let people act on that content in natural language — no fixed trigger phrases, no code changes as Siri's language model evolves.
Also feeds Shortcuts, widgets, controls, Live Activities, the Action button and Apple Pencil. This is the mechanism the X thread is built on.
Maps your SwiftUI/UIKit views to entities so people can reference and act on what's literally on screen conversationally ("send this one to…", "remind me about that"). Extends App Intents from "your data" to "your data, in context."
Why it matters: turns any list/detail screen into something Siri can point at and operate.
The Evaluations framework checks Foundation Models features behave across dynamic conditions. App Intents Testing (beta) lets you test the Siri / Spotlight / Shortcuts pathways directly — no fragile UI automation.
Why it matters: the brittle part of the adapter pattern (does Siri pick the right source?) becomes something you can actually regression-test.
Generate high-quality images in many styles incl. photorealistic, transform a user's own photos via natural-language descriptions, and edit by description or touch. Runs on Private Cloud Compute (photos never stored/shared) and is available through an API for your apps.
Why it matters: in-app image gen/edit without standing up an image model or a cloud bill.
Apps can supply matching content for what's in front of the user — Camera on iPhone, on-screen content on Mac/iPad, real objects on Vision Pro — and launch into your app for richer detail or actions.
Why it matters: "point camera → my app's relevant data appears" becomes a supported flow. Strong for inventory / catalog / field use.
A new on-device framework for running your own custom models on Apple Silicon via a Swift API — with model specialization, ahead-of-time compilation, explicit memory control, zero-copy, and stateful execution.
Why it matters: for cases where the system foundation model isn't enough, you can ship a specialized model locally with serious performance control.
Standard text views get proofread / rewrite / summarize / compose for free (custom text views can adopt the APIs). Shortcuts assembles multi-step automations from natural-language descriptions. Widgets are now customizable through App Intents.
Plus iOS 27 adds a Music Understanding framework and NowPlaying framework; SwiftUI gains a Document API, AsyncImage HTTP caching, and a @State macro with lazy init.
Two tweets, read together. Max Weinbach (@mweinbach), 2026-06-09 — the "build the app yourself" claim. Kris Puckett (@krispuckett), 2026-06-10 — quote-tweets Max to add the missing ingestion layer (Printing Press).
What's nice about Fable 5 and new Siri is I can basically just tell Claude Code to create an app that pulls in the data I want (codex app-server, Tesla) via APIs then make sure App Intents and Spotlight indexing are properly done.
Why wait for devs if I can do it in an afternoon
@altryne: connect the dots for me? is the new siri finally doing the thing they promised 2 years ago with app intents? It pulls info out? — Max: yup!
@afc_timio: Tried this with fable. Spotlight can see the index data, Siri still has problems deciding where to pull the data you ask for from so it misses a lot of times. This is a hard problem to solve without instructions. — Max: I'm trying to see if there's a good way to add better descriptions to the App Intents or if index + app intents help on similar or the same data.
The new "promised two years ago" Siri behaviour — pulling info out of apps and acting on it — is now real because of App Intents + Spotlight indexing. So instead of waiting for some company to build the app you want, you point Claude Code at an API (Tesla, a personal data server, etc.), have it generate a thin native app that fetches that data, and — critically — wire up the App Intents and the Spotlight entity index correctly. Then Siri/Apple Intelligence can talk to your data as if it were a first-party feature.
The shift: the hard, valuable part isn't the UI anymore — it's modelling your data as entities + intents the system can reason over.
Have to imagine this is even more useful with @mvanhorn · printingpress.dev
@mvanhorn (Matt Van Horn, maker of Printing Press): yes. will add a lot of magic auto-magically
Max assumes you can already get the data — point Claude Code at "the Tesla API" or "a codex app-server" and it fetches. Kris's point: the reachability of that data is itself the bottleneck. Real sources are messy APIs, rate-limited endpoints, or sites with no public API at all. Printing Press closes that gap — from one prompt it prints an agent-native CLI (plus a Claude Code skill, an OpenClaw skill, and an MCP server) for any API/app/site, baking in the playbook that a local SQLite mirror beats a remote call and compound commands beat ten round trips.
So the two tweets stack into one pipeline: Printing Press prints the connector → Claude Code builds the iOS adapter → iOS 27 exposes it to Siri. Matt Van Horn's reply ("will add a lot of magic auto-magically") is the maker confirming the connector layer is meant to slot in exactly here.
Layering Kris Puckett's tweet onto Max's turns "build one app" into "run a factory for Siri adapters." Five stages, each owned by a different tool — the first two are the new part.
Tesla, a codex app-server, Linear, a CRM export, FPL, Google Workspace, WhatsApp exports, a niche website with no public API.
One prompt → token-efficient Go CLI + Claude Code skill + OpenClaw skill + MCP server, often over a local SQLite mirror. Makes messy/no-API data reliably reachable.
Uses the connector to fetch, then writes the Swift app + App Intents + Spotlight entity schema + App Intents tests. The "afternoon" Max describes.
App contributes entities to the Spotlight semantic index, declares intents for actions, and maps on-screen views via View Annotations.
Apple Intelligence becomes the front-end: ask, act, point the camera — no custom UI required for the core loop.
Once stages 2–3 are scripted, every new source is mostly "run Printing Press, then re-run the Claude Code adapter scaffold against the new connector." That's what makes a fleet of personal/business Siri adapters feasible for one builder: Tesla today, Mission Control tomorrow, a CRM the week after — same loop, different connector.
Printing Press's own framing ("every API has a secret identity") matters for the entity schema: the adapter should expose the source's useful shape (Linear as a "team behaviour observatory," not just issues) — which is exactly the rich-description work the field reports say Siri's source selection depends on.
Each card: why iOS 27 makes it better, the Apple APIs you'd touch, an MVP path, and the main risk. Prioritised toward Ananth's real surfaces. Filter, star, and jot notes — your picks are saved locally in this browser.
VehicleEntity + intents (precondition, set charge limit). Test via App Intents Testing.brain.json / the inbox (local SQLite mirror) gives the app and Dab the same agent-native interface to query/append.brain.json (synced) → NoticeItemEntity + a Capture intent that appends to inbox. Mirrors the existing WhatsApp capture flow.ArticleEntity. "Read next" intent ranks by topic/length.contact-goat et al.) — print one for your CRM and the app reads a uniform interface.PersonEntity with lastContact/nextStep. Intents: log interaction, draft follow-up.TransactionEntity → category + query intents. Keep inference strictly on-device.MealEntity; "how did I eat today?" intent over HealthKit + logs.eu-tenders, conduyt-crm) so account data is one query away.AccountEntity + "log visit" / "next best action" intents over a CRM/Sheet export.GarmentEntity → "what to wear for X" intent.ChoreEntity + allowance intents; start without deep Screen Time hooks.Build-now = high personal payoff, APIs are GA-ish, and you own both ends of the data. Wait/watch = depends on framework maturity, accuracy you can't yet verify, or weaker tie to your priorities.
| Idea | Lane | Why iOS 27 helps | Main risk |
|---|---|---|---|
| Tesla / car ops adapter | Build now | Live car state + voice actions via App Intents/Spotlight | Tesla API auth; Siri source ambiguity |
| Mission Control iOS companion | Build now | Voice capture + on-screen actions on your own board | Repo sync; keep render pipeline canonical |
| Read / learning queue | Build now | Private on-device summaries; "read next" intent | Summary quality; dedupe with Read lane |
| Personal CRM adapter | Build now | People as entities; on-screen follow-up drafts | Note privacy; messy contacts |
| Finance / spend tracker | Build now | On-device money Q&A — real privacy win | Bank data ingestion; categorisation |
| Health / nutrition coach | Build now | Multimodal meal logging; local HealthKit Q&A | Estimate accuracy; don't over-claim |
| Field-sales / SMB assistant | Build now | Voice logging + Visual Intelligence; free PCC at small scale | CRM depth; field offline reliability |
| Generic any-API → Siri kit | Build now | Reusable Claude-Code scaffold for the whole pattern | Generalisation + per-API auth |
| Adapter Factory (Printing Press × Claude Code) | Build now | Connector→adapter loop; new source = re-run, not rebuild | Full loop unproven; per-source auth + Siri tuning |
| Wardrobe / personal-brand | Wait / watch | Image Playground + Visual Intelligence cataloguing | High cataloguing friction; novelty payoff |
| Family / time-allowances | Wait / watch | Could expose chores/allowances to Siri | Time Allowances API depth unconfirmed |
| AI employees / business ops | Wait / watch | iOS as voice front-door to server agents | Scope creep; flaky trigger for high stakes |
| Music-understanding tool | Wait / watch | New Music Understanding / NowPlaying frameworks | Maturity unknown; weak priority fit |
| Visual-intelligence inventory | Wait / watch | Camera → matched catalog entity | Match accuracy; needs real catalog |
| On-device "ask my docs" | Wait / watch | Fully private doc Q&A via Foundation Models/Core AI | On-device capability ceiling |
| Image-Playground content helper | Wait / watch | In-app image gen with no model bill | Controllability; crowded space |
Ordered to de-risk the brittle part (Siri source selection) early, on data you fully control, before investing in anything user-facing.
Goal: run the full Kris+Max stack once — Printing Press connector → Claude Code iOS adapter → Siri — and confirm Siri can reliably read and act on the data via App Intents + Spotlight. This is the go/no-go for the whole factory thesis.
VehicleEntity (range, charge %, location) and contribute it to the Spotlight index; add two intents: "precondition the car" and "set charge limit".Goal: test whether the on-device Foundation Model is good enough to be useful on your own structured data, with zero data leaving the phone.
TransactionEntity objects (no bank integration yet — keep it a fixture).Goal: ship something you'll actually use daily, and learn the View Annotations / on-screen-awareness flow on a board you already understand.
brain.json; expose items as NoticeItemEntity in Spotlight.Apple developer pages (dated Jun 2026, iOS 27 / Xcode 27 beta cycle) and the originating X thread. Claims above trace to these; anything not directly supported is labelled Speculative.
projects/ios27-ai-app-opportunities.html · Compiled 2026-06-11 · Mission Control / Notice Board · Edits via Dab/Claude only. Star/note state is stored locally in your browser and never transmitted.