Why Android is different from Apple
Apple ships App Intents — a rich, typed, on-device invocation API. Android has nothing equivalent. What it has is launcher shortcuts + verified deep links, and (in narrower cases) Assistant App Actions.
Product · Build Android Shortcuts
As your builder — the Android-surface role
Android has no App Intents peer. What it does have is verified App Links, static + dynamic shortcuts, and Assistant App Actions. The Builder scaffolds all three from a description of your app.
assetlinks.json
Digital Asset Links for verified App Links
shortcuts.xml
Static shortcuts + long-lived pinned shortcuts
Kotlin
ShortcutManagerCompat helper you can drop in
Launcher-scoped
Not a fake App Intents clone — see FAQ
Generates the assetlinks.json + intent-filter setup so deep links open your app instead of the browser.
shortcuts.xml for launcher long-press, plus a Kotlin helper for dynamic shortcuts you push at runtime.
Follows Google's shortcut and deep-link guidelines so you don't get flagged for spammy or misleading intents.
01 · Describe
Screens, actions, entities. The Builder maps those to launcher shortcuts and deep-link URIs.
02 · Generate
All three artifacts, matched to a consistent set of URIs and shortcut IDs.
03 · Verify
Steps for hosting assetlinks.json under /.well-known/ and confirming verification in the Play Console.
04 · Push shortcuts
A ready-made helper for pushing dynamic shortcuts based on user context — the ones Android actually surfaces.
You don't have to be an agent-optimization expert to use this. Here's the short version.
Apple ships App Intents — a rich, typed, on-device invocation API. Android has nothing equivalent. What it has is launcher shortcuts + verified deep links, and (in narrower cases) Assistant App Actions.
We don't generate Assistant App Actions for arbitrary domains — Google restricts those to a small set of built-in intents. We focus on launcher + deep-link surfaces that any app can use.
If you want ChatGPT, Claude, Perplexity or Gemini to invoke your product, use the MCP Builder. Android shortcuts help on-device — MCP handles the agent side.
No — Android doesn't have App Intents. This Builder ships the closest thing Android does support.
You'll need one to publish. The Builder itself works without one — you copy the generated files into your Android project.
Deep links and shortcuts work across Wear OS and Android Auto with the same manifest. Auto has additional templates we don't scaffold today.
Create a free account — explore every mode, then subscribe to start your trial. Or book a guided walkthrough.