HomeKit App Review checklist
HomeKit apps control real homes. Review readiness depends on a safe path through no-home, simulated-home, accessory, permission, and role states.
Enable HomeKit only for a user-facing home automation task, and provide a review route that does not require a real home full of accessories. Apple says HomeKit coordinates and controls home automation accessories, and Apple provides HomeKit capability setup and accessory simulator guidance. AppReviewReady interpretation: create a simulated-home review path before submission.
Define the home automation purpose
Name the home task: control lights, manage locks, monitor sensors, coordinate scenes, configure accessories, or automate routines. Avoid requesting HomeKit access merely to display a decorative smart-home badge.
A smart-home app should be useful in no-home, empty-home, and configured-home states. The first run should explain what users need before the app asks for access.
Test home roles and accessory states
- Owner, resident, guest, and no-permission states should be understandable.
- Accessory offline, unreachable, updating, and removed states need clear messaging.
- Automations should not create unsafe actions without user intent.
- Locks, doors, cameras, alarms, and sensors require stricter privacy and safety review.
- Support should explain whether issues are app, accessory, network, or HomeKit configuration.
Build a reviewable simulated home
Apple's HomeKit Accessory Simulator can help test accessories that are not physically available. Use it to create a deterministic path for review and QA, while still testing real hardware before release where safety matters.
AppReviewReady interpretation: the simulated home should reflect the product's main value, not only prove the app launches. Include at least one accessory, one action, one error state, and one privacy-sensitive boundary.
Protect household context
- Check privacy labels for home names, room names, accessory data, presence, camera, and automation history.
- Test sign-out, account deletion, home removal, and revoked Home access.
- Avoid logging sensitive home events unless necessary and disclosed.
- Verify widgets, notifications, and Live Activities do not reveal unsafe household details.
- Retest after adding accessory categories or automation templates.
Give review a HomeKit test route
The reviewer should not need a physical accessory to understand the app. If real hardware is essential, provide video, demo mode, or a simulated subset for the core UI.
After launch, treat new accessory categories as review-impacting changes. Adding locks, cameras, alarms, or presence sensors can change privacy and safety risk even if the HomeKit code path already exists.
If the app supports multiple homes, test switching homes and removing a home. The app should not keep showing stale accessory state from a household the user no longer controls.
Role changes should immediately affect controls for locks, cameras, and alarms.
Automation templates should explain consequences before enabling scenes that run unattended.
HomeKit review route: Primary home task: [task] Accessory setup: [simulated or real] Role needed: [owner/resident] How to trigger: [steps] No-home behavior: [message] Privacy-sensitive data: [fields] Automation safety: [guardrail]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check HomeKit readiness
Review HomeKit roles, accessories, simulator path, and privacy before submission.
Open the tool