Source: Apple Inc. Canonical content at https://developer.apple.com/design/human-interface-guidelines/homekit. This file is a structured index of that content, snapshot 2025-02-02. Apple HIG text and imagery are © Apple Inc.; this repository provides organization and cross-referencing for AI agent consumption only.
HomeKit
Help people set up, name, and organize their accessories
Allow fine-grained accessory configuration and control
Provide access to custom accessory features
Show people how to create powerful, hands-free automations
Provide support
Terminology and layout
Acknowledge the hierarchical model that HomeKit uses.
Make it easy for people to find an accessory’s related HomeKit details.
Recognize that people can have more than one home.
Don’t present duplicate home settings.
Setup
Use the system-provided setup flow to give people a familiar experience.
Provide context to explain why you need access to people’s Home data.
Don’t require people to create an account or supply personal information.
Honor people’s setup choices.
Carefully consider how and when to provide a custom accessory setup experience.
Help people choose useful names
Suggest service names that suit your accessory.
Check that the names people provide follow HomeKit naming rules.
Use only alphanumeric, space, and apostrophe characters.
Start and end with an alphabetic or numeric character.
Don’t include emojis.
Help people avoid creating names that include location information.
Siri interactions
Present example voice commands to demonstrate using Siri to control accessories during setup.
After setup, consider teaching people about more complex Siri commands.
Recommend that people create zones and service groups, if they make sense for your accessory.
Offer shortcuts only for accessory-specific functionality that HomeKit doesn’t support.
If your app supports both HomeKit and shortcuts, help people understand the difference between these types of voice control.
Custom functionality
Be clear about what people can do in your app and when they might want to use the Home app.
Defer to HomeKit if your database differs from the HomeKit database.
Ask permission to update the HomeKit database when people make changes in your app.
Cameras
Don’t block camera images.
Show a microphone button only if the camera supports bidirectional audio.
Using HomeKit icons
Use only Apple-provided icons.
Styles
Custom color HomeKit icon
Position the HomeKit icon consistently with other technology icons.
Use the HomeKit icon noninteractively.
Don’t use the HomeKit icon within text or as a replacement for the word HomeKit.
Pair the icon with the name HomeKit correctly.
Referring to HomeKit
Emphasize your app over HomeKit.
Adhere to Apple’s trademark guidelines.
Use Apple product names in singular form only; do not make Apple product names possessive.
Don’t translate Apple, Apple Home, HomeKit, or any other Apple trademark.
Don’t use category descriptors. For example, say iPad, not tablet.
Don’t indicate any kind of sponsorship, partnership, or endorsement from Apple.
Attribute Apple, HomeKit, and all other Apple trademarks with the correct credit lines wherever legal information appears within your app.
Refer to Apple devices and operating systems only in technical specifications or compatibility descriptions.
Referencing HomeKit and the Home app
Use correct capitalization when using the term HomeKit.
Don’t use the name HomeKit as a descriptor.
Don’t suggest that HomeKit is performing an action or function.
Use the name Apple with the name HomeKit , if desired.
Use the name HomeKit for setup, configuration, and instructions, if desired.
Use the app name Apple Home whenever referring specifically to the app.
<!-- hig-doctor:canonical-footer -->
For the complete guidance, including worked examples and illustrations, see the canonical page: https://developer.apple.com/design/human-interface-guidelines/homekit