apple-dev-mcp/content/universal/carplay.md

Complete Apple development guidance: Human Interface Guidelines (design) + Technical Documentation for iOS, macOS, watchOS, tvOS, and visionOS

---
title: Carplay
platform: universal
category: technologies
url: https://developer.apple.com/design/human-interface-guidelines/carplay
quality_score: 0.49
content_length: 7684
last_updated: 2025-07-20T03:45:10.008Z
keywords: ["carplay","universal","technologies","icons","design","interface","system","navigation","layout","input","controls","motion","selection","visual","color","images"]
has_code_examples: false
has_images: false
is_fallback: false
---

Car Play Car Play lets people get directions, make calls, send and receive messages, listen to music, and more from their car’s built-in display, all while staying focused on the road. People download Car Play apps from the App Store and install them on i Phone like any other app. When people connect their i Phone with their vehicle, app icons for installed Car Play apps appear on the Car Play Home screen. Car Play is designed for drivers to use while they’re driving. Keep this context in mind as you design your Car Play app, providing features that help people perform tasks quickly and with minimal interaction. To create the interface of your Car Play app, you use the system-defined templates that are appropriate for the type of app you’re developing, such as audio, communication, navigation, or fueling. For each template, your app provides the content and i OS renders it in Car Play. Because the system displays UI components and handles the interface with the vehicle, you don’t need to adjust your layout for different screen resolutions, or manage input from different types of hardware like touchscreens, knobs, or touch pads. To learn how to create various types of Car Play apps and use the system-provided templates, see Car Play App Programming Guide. The general design guidelines below apply to all types of Car Play apps.i Phone interactions Car Play shows compatible apps from the connected i Phone on the car’s built-in display, applying simplified interfaces that are optimized for use while driving. Eliminate app interactions on i Phone when Car Play is active. Interactions with your app need to occur using the car’s built-in controls and display. If your app requires setup on i Phone, make sure people perform it before the vehicle is in motion. Never lock people out of Car Play because the connected i Phone requires input. Your app needs to function when i Phone is inaccessible — for example, when people put it in a bag or in the trunk while driving. If people must resolve a problem on the connected i Phone, let them do so after the vehicle stops. Make sure your app works without requiring people to unlock i Phone. Most people use Car Play while their i Phone is locked, so ensure that the features you provide in your Car Play app work as expected in this scenario. Audio In Car Play, keep in mind that your app coexists with other audio sources, such as the car’s own built-in radio and voice prompts from the navigation system. Regardless of whether audio is a primary aspect of your app’s experience, you need to know how people expect audio to behave so you can meet those expectations. Let people choose when to start playback. In general, avoid beginning playback automatically unless your app’s purpose is to play a single source of audio, or your app is resuming previously interrupted audio. Also, avoid starting an audio session until you’re ready to actually play audio because starting a session silences other audio sources, like the car’s built-in radio. Start playback as soon as audio has sufficiently loaded. After people make a selection, it may take several seconds for audio to begin playing, depending on buffering and network conditions. The system keeps the selection highlighted and displays a spinning activity indicator until your app signals that the audio is ready to play. Display the Now Playing screen when audio is ready to play. Don’t delay playback until descriptive information completes loading. If necessary, continue loading such information in the background, and show it when it’s available. Resume audio playback after an interruption only when it’s appropriate. For example, your app can resume audio after a temporary interruption like a phone call. Permanent interruptions, such as a music playlist initiated by Siri, are nonresumable. When a resumable interruption occurs, your app needs to resume playback when the interruption ends if audio was actively playing when the interruption started. When necessary, automatically adjust audio levels, but don’t change the overall volume. Although your app can adjust relative, independent volume levels to achieve a great mix of audio, people need to control the final output volume. Layout Car Play supports a wide range of display resolutions with varying pixel densities and aspect rat iOS. The system automatically scales app icons and interfaces based on the resolution of the display, so they always appear onscreen at roughly the same size. Some common screen sizes are listed in the table below. Dimensions (pixels)Aspect ratio 800 x 4805:3960 x 54016:91280 x 72016:91920 x 7208:3 Provide useful, high-value information in a clean layout that’s easy to scan from the driver’s seat. Don’t clutter the screen with nonessential details and unnecessary visual embellishments. Maintain an overall consistent appearance throughout your app. In general, ensure that elements with similar functions look similar. Ensure that primary content stands out and feels actionable. Large items tend to appear more important than smaller ones and are easier for people to tap. In general, place the most important content and controls in the upper half of the screen. Color Color can indicate interactivity, impart vitality, and provide visual continuity. In general, prefer a limited color palette that coordinates with your app logo. Subtle use of color is a great way to communicate your brand. Avoid using the same color for interactive and noninteractive elements. If interactive and noninteractive elements have the same color, it’s hard for people to know where to tap. Test your app’s color scheme under a variety of lighting conditions in an actual car. Lighting varies significantly based on time of day, weather, window tinting, and more. Colors you see on your computer at design time won’t always look the same when your app is used in the real world. Consider how color brightness might affect the experience of driving at night, and how low-contrast colors can wash out in direct sunlight. If necessary, make adjustments to provide the best possible viewing experience in the majority of use cases. Ensure your app looks great in both dark and light environments. Car Play supports both light and dark appearances, and may automatically adjust the current appearance based on lighting conditions. Choose colors that help you communicate effectively with everyone. Different people see and interpret colors differently. For guidance on using colors in ways that people appreciate, see Inclusive color. Icons and images Car Play supports both landscape and portrait displays and both @2 x (low resolution) and @3 x (high resolution) scale factors. Supply high-resolution images with scale factors of @2 x and @3 x for all Car Play artwork in your app. The system automatically shows the correct images and scales them appropriately, based on the resolution and size of the car’s display. Mirror your i Phone app icon. A well-designed app icon works well in Car Play and on i Phone, without the need for a second design. Don’t use black for your icon’s background. Lighten a black background or add a border so the icon doesn’t blend into the display background. Create your Car Play app icon in the following sizes:@2 x (pixels)@3 x (pixels)120 x 120180 x 180 Error handling A Car Play app needs to handle errors gracefully and report them to people only when absolutely necessary. Report errors in Car Play, not on the connected i Phone. If you must notify people of a problem, do so clearly in Car Play. Never direct people to pick up their i Phone to read or resolve an error. Not supported in i Pad OS, mac OS, tv OS, vision OS, or watch OS.