Hello Apple Community,
I'm seeking guidance on a Car Play app rejection from the apple team. My mobile-only app was approved, but the version that includes the Car play app is consistently being rejected, and I'm trying to understand the reasons for the same.
I'm hoping to get insights from developers who have successfully published Car Play apps, especially those involving voice interaction.
About the App
My ios app is an AI-powered voice agent for drivers, designed to provide a hands-free, conversational experience.
The app's features include:
Information & Navigation
- Live weather updates.
- Turn-by-turn navigation for single or multiple destinations, which opens Google Maps.
- Real-time data lookups (flight status, stock prices, news, sports scores).
Media & Entertainment
- Playing songs via Spotify and YouTube Music.
Productivity
-
Setting time-based reminders.
-
Making phone calls.
Vehicle Integration
- Remote commands for the vehicle (e.g., "lock the doors," "open the trunk").
- Accessing vehicle data (fuel level, tire pressure, etc.).
The Problem: Car Play Rejection
When I remove the Car Play code and manifest declaration, the app gets approved for mobile. However, as soon as I include the Car Play implementation, the app update is rejected.
This leads me to believe the issue is not with the app's core functionality but specifically with how it presents itself on Car Play.
My Core Question for the Community
Is the rejection likely because Car Play does not permit third-party, general-purpose voice assistants as a primary app interface? The platform seems to reserve core voice control for the integrated Siri and third-party apps are expected to fit into specific categories (Media, Navigation, IoT, etc.) using the Car App Library templates.
My app acts as a single, all-in-one assistant, which is not one of the listed categories.
What is the correct path to bring my app's features to Car Play?
- Is it against policy to have a custom voice assistant, even if its capabilities fall into supported functions like navigation and media?
- Should I fundamentally change my approach? For example, should I break the app down and submit it as a Navigation or IoT app that uses the official Car App Library templates, and then offer my voice capabilities within that compliant structure?
- Has anyone successfully integrated a third-party voice service into a Car play app, and what was the approved architecture?
- Or any other path you suggest based on your experience.
I've reviewed the "Car app quality" guidelines but am looking for practical interpretation and advice from those with experience. Any insights you can share would be incredibly helpful.
Thank you
