CPListTemplateDetailsHeader — Number of Action Buttons

CPListTemplateDetailsHeader supports action buttons for entity pages (e.g., playlist or album detail views). Currently, it appears that the header supports a limited number of trailing action buttons.

  • What is the officially supported maximum number of action buttons on CPListTemplateDetailsHeader?
  • If currently limited to one, is there a plan to support two action buttons to cover common media patterns like Play + Shuffle?
  • Are there alternative patterns the team recommends for presenting multiple primary actions on entity pages within the current template constraints?
Answered by Frameworks Engineer in 891313022

Hi,

We have API to tell you the max number of action buttons.

Hopefully this helps.

Rico
CarPlayFrameworks Engineer

Accepted Answer

Hi,

We have API to tell you the max number of action buttons.

Hopefully this helps.

Rico
CarPlayFrameworks Engineer

Thanks Rico. We're aware of the API.

What we're trying to understand is what app developers should design for in practice. Is there a guaranteed minimum number of supported action buttons? What are the most common scenarios across the CarPlay ecosystem, and what factors cause the value to vary?

For example, should we generally expect only a single primary action, or is supporting two actions (such as Play + Shuffle) a realistic design target on most systems?

CPListTemplateDetailsHeader — Number of Action Buttons
 
 
Q