HIGH PRIORITYTrack a migraineNo Siri or Shortcut action
→App review
See what your app already does—and what Siri and AI tools still can’t.
Capability Studio reviews your app’s screens, code, data, App Intents, and tests. You get a clear list of useful actions and what needs attention next.
Request an auditIn development · Starting with App Intents
Review queue4 unresolved
REVIEWCheck migraine riskExists · needs review
→OPPORTUNITYExport symptom historyUseful app task
→SELECTED FINDINGSource-observed
Track a migraine
The app already tracks migraines. It does not yet have a reviewed App Intent.
- App data
- Migraine session
- Working app code
- Found
- Where it appears
- Not confirmed
A practical app review
Leave with a clear list of useful app actions.
Audit starts with the app you already have. It follows important user tasks through your screens, data, working code, App Intents, and tests.
It does not treat every method, button, or screen as a useful action. A person reviews the findings first.
What you get
From app code to a plan your team can review.
What already exists
The screens, data, code, tests, and App Intents behind each useful task.
What your app can do
Useful tasks, missing connections, conflicts, and open questions.
Agreed action details
For each action: its name, inputs, result, permissions, owner, and supported places.
What to do next
A ranked list of actions to add, skip, research, or build.
Where each action works
See what works in the app, Siri, Shortcuts, and AI tools.
Compare what already works in the app with what appears elsewhere. Missing means there is work to do. Unknown stays unknown until someone checks it.
ILLUSTRATIVE AUDITAURALOG · APP-ACTION COVERAGE
App actionAppShortcutsSiriAI tool
Track a migraineObservedMissingUnknownMissing
Check migraine riskObservedReviewUnknownMissing
Export symptom historyObservedMissingMissingMissing
Clear proof
Know what was checked—and what was not.
Reading code can show how an app is built. It cannot prove the action appears in the right app target, works in Siri, stays reliable after release, or gets used. Audit keeps those checks separate.
- 01
Code found
We found the working code in the app project.
- 02
Details reviewed
A person approved what the action does and where it belongs.
- 03
Build passed
The exact app target compiled and passed focused tests.
- 04
Tried in the real app
Someone checked the action in Siri, Shortcuts, Spotlight, or another real feature.
- 05
Seen in production
Real use is tied to the exact released version.
From finding to release
Make the next decision obvious.
Pick one finding and review what supports it. Then add it to the plan, skip it, or research it further. The same action can move through Build, Preview, Ship, and Measure.
Start with one user task
Find the best action to work on next.
Bring one important app task into Capability Studio. Leave with a clear list of what exists, what is missing, and what to do next.