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?

Thanks for the response. One thing I struggle with is that grid-based presentation of large content collections has become a very common pattern across media and content apps. Users are increasingly accustomed to browsing libraries, playlists, albums, podcasts, and other collections in grid layouts, often even preferring them over lists for visual discovery. Because of that, the current limit of 24 items feels somewhat arbitrary when compared to the 200-item limit available in list templates. In practice, it means developers often end up choosing a presentation style based on API constraints rather than on what provides the best user experience for their content and users. Unless there's a technical or safety consideration we're overlooking, it would be great to understand why the same scale isn't supported for grid layouts. We'll definitely file an enhancement request, as the current limitation makes it difficult to provide a consistent and intuitive browsing experience for larger collections.