Music/Audio App Development Guide
This guide explains the points you need to consider when developing an app in the Music/Audio category that runs on Pleos Connect. It guides the classification and segmentation criteria for Music/Audio category apps and policies to prevent user experience degradation when integrating with the media library. This guide is applied as a review criterion when registering with the Pleos App Market.
Music/Audio App Category
Category Definition
The Music/Audio category includes apps that provide the following audio-centric services:
- Music streaming and playback
- Podcasts, audiobooks, and radio content provision
- Audio platforms intended for in-vehicle media playback
Category Registration Criteria
To register an app in the Pleos App Market Music/Audio category, the following requirements must be met:
- Audio content playback must be the main function of the app
- Provide UI/UX suitable for the driving environment
- Support background playback and integration with vehicle media controls
Category Mismatch Policy
- If additional features (community, shopping, etc.) are included, the suitability of the category is determined based on whether audio playback is the core function.
- Apps that provide music as a mere auxiliary function will be immediately rejected in the review.
Media Library Integration
Category Segmentation Policy for Media Library Integration
In the vehicle environment, integration with the media library (system media browser, voice commands, steering wheel controls, etc.) is a key user experience element. For media library integration, Music/Audio apps need to be categorized into subcategories based on content type.
| Subcategory | Classification Principle |
|---|---|
| Music | Provides music content based on artist, album, and track Example: Music streaming service, local music player |
| Podcast | Provides voice content on an episode basis Includes subscription, latest episodes, and episode list structure |
| Audiobook | Book-based long-duration voice content Includes chapter-based navigation and playback position saving function |
| Radio | Real-time streaming or broadcast-based audio content Channel/station-centered navigation structure |
- If a single app corresponds to multiple subcategories, it is mandatory to separate exposure by content type in the media library.
- If the subcategory classification is unclear, it may be a reason for rejection in the review.
Media Library Integration Policy (Mandatory)
Music/Audio category apps must comply with the following policies:
- Provide a clear browsing structure by content type
- When integrating with the system media library, it is essential to deliver subcategory (Music/Podcast/Audiobook/Radio) information
- The method of mixing all content into a single list may be restricted
Implementation of Media Library Integration
Add category information to the manifest file. Set the android:appCategory attribute of the <application> element to "audio". For more information, refer to Add Android Automotive OS support to media apps.
<application
...
android:appCategory="audio" />
App development recommendations for Gleo AI feature support
Music/Audio apps running on Pleos Connect can use Gleo AI features.
Gleo AI is an AI agent that accompanies users on their journeys, communicates with them, and assists them. Using LLM-based AI and voice technologies, it understands the context of voice commands and conversations and provides the responses and actions needed to deliver a convenient and safe mobility experience.
When integrated with Gleo AI, the following capabilities are available:
- Voice features for track search and playback, such as “Play IU’s song in the Melon app.”
- In addition to track search, you can optionally provide about three to five additional voice features for other core app capabilities.
- Once the app passes review and is released on the Pleos App Market, users can start using those voice features right after installation.
To use Gleo AI voice search and control in your app, you must implement one of the following two approaches:
Gleo Interface
The Gleo Interface defines how Gleo AI and third-party apps interact with each other in the vehicle to process the user’s voice commands.
To use the Gleo Interface, your app must implement functions that Gleo AI can invoke, and you must register a schema that defines how Gleo AI calls those functions.
For detailed steps on implementing the Gleo Interface, see the Gleo AI Integration Guide.
Android standard media API implementation
In this approach, Gleo AI controls music apps through MediaAgent. MediaAgent controls media apps based on the Android standard Media3 stack.
For music apps built to comply with AndroidX Media3 and the standard AAOS media APIs, we are preparing a future update that will enable voice features without requiring you to implement a separate schema.
Minimum requirements for standard media compliance
To use Media3, the standard Android media control library, you must implement at least the following:
- Integrate
MediaSession/MediaLibraryService - Provide basic media control commands such as play, pause, next track, and previous track
- (When integrating
MediaLibraryService) provide search-related commands where possible
MediaBrowserService is also supported for compatibility, but we recommend adopting Media3 as the current standard.
Requirements for search-based voice features
To use voice features such as track search, you must implement search in MediaLibraryService according to Media3. If you only expose MediaSession, basic playback control may work, but search-based voice features will be limited.
Review and Operation Criteria
Review Criteria
The review criteria for registering apps in the Pleos App Market Music/Audio category are as follows:
- Verify that the category and subcategory definitions are clear.
- Verify that the media library integration structure is appropriate.
- Evaluate usability and safety in the vehicle environment.
Actions for Policy Violations
In case of policy violations, the following actions may be taken:
- Category mismatch: Request for modification or review rejection
- Undefined subcategory: Request for feature enhancement
- Repeated violations of the above: Restriction of app exposure or suspension of registration