Request the correct CarPlay entitlement for a navigation or EV-charging app and design its template hierarchy within Apple's depth limits
domain: developer.apple.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the single CarPlay app category the app belongs to (audio, communication, driving task, EV charging, fueling, navigation, parking, or quick food ordering)
Request the matching entitlement (e.g. the navigation-specific entitlement) since the entitlement determines which template set is usable
Design the CarPlay UI within that category's template stack depth limit
Submit the entitlement request through Apple's developer program before building CarPlay-specific UI
Test the CarPlay experience using Xcode's CarPlay simulator
Known gotchas
CarPlay apps must be single-category; templates from two different entitlement categories cannot be mixed in one app
Template stack depth limits vary by category (e.g. navigation and audio allow deeper template stacks than driving-task or quick-food-ordering apps), and these limits have changed across iOS versions
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?