CarPlay Q&A

We've observed inconsistent behavior when users interact with CarPlay via physical hardware controls (rotary knobs, d-pads, and physical buttons) on various head units: Focus navigation through grid and list items can behave unpredictably when using the rotary encoder, particularly when scrolling through sections with mixed item types or transitioning between sections. Selection via the physical button/knob press sometimes does not register on the expected item, especially after rapid scrolling. Hardware back/menu button behavior doesn't always align with the template navigation stack in certain edge cases. Are there known issues with hardware control input handling in the current CarPlay SDK, particularly with grid templates? Are there best practices we should be implementing to improve hardware control responsiveness?

Can Siri’s conversational features in CarPlay invoke third-party App Intents without the user opening that app’s CarPlay tile? e.g. “Hey Siri, ask [App Name] …”?

What does Apple look for when approving carplay-voice-based-conversation for a vertical, task-focused assistant (not a general AI chatbot)? Are there specific driving-safety expectations, and can subscription-gated actions be enforced inside perform()?

The current limit of 24 items per grid section forces us to split large collections (e.g., user playlists) across multiple sections, leading to layout inconsistencies across different screen sizes. List templates allow up to 200 items. Is there a plan to increase the grid item limit, or is there a recommended pattern for presenting larger collections in grid layouts?

What's the simplest way to programmatically detect the iPhone is connected to CarPlay? (not necessarily having your app launched)

Condensed grid sections currently use a fixed two-column layout. On larger or higher-resolution head units, this underutilizes the available screen real estate. Is there support (or planned support) for adaptive breakpoints that expand to three or more columns on wider displays?

With the restrictions on conversational apps in iOS 26.4... are there any suggestions on how to integrate location services with iOS 27?

For a domain-specific voice assistant (not navigation, not general-purpose chat), should we integrate via the CarPlay voice-based conversational entitlement, Siri + App Intents/App Schemas, or a hybrid? What does Apple recommend?

What should be the .mode and .options ?

When using trailing scroll arrows in grid layouts with multi-row sections, scrolling does not consistently behave as expected. In some cases, scrolling becomes stuck or moves in the reverse direction. We've been able to reproduce this across multiple apps. Has this been addressed or is a fix planned?