Abstract:
In some implementations, a computing device can send a priming command to a media application to cause the media application to load media items and media item metadata into memory associated with the media application. The computing device can predict a media application that is likely to be invoked by a user. The computing device can launch the media application. The computing device can send the priming command to the media application to cause the media application to prepare media items for playback or presentation to the user. After the media application loads the media items, the computing device can receive metadata associated with the loaded media items and present the metadata and appropriate media application controls on a display of the computing device.
Abstract:
A media process may receive, from a client application, a request for media information about a range of media items in a queue of a media application, the request being sent while the media application is executing. The queue includes a previous set of media items that have been played by the media application, a current item (e.g., currently playing), and a future set of items that are to be played The request may specify the range to include the current item and at least one item from the previous set and/or future set. The daemon sends a request to the media application and receives media information from the application. The received media information may include an order of media items and an identifier for each item in the range of items. The received information may be sent to the client application for displaying information about the range of items.
Abstract:
A media process may receive, from a client application, a request for media information about a range of media items in a queue of a media application, the request being sent while the media application is executing. The queue includes a previous set of media items that have been played by the media application, a current item (e.g., currently playing), and a future set of items that are to be played The request may specify the range to include the current item and at least one item from the previous set and/or future set. The daemon sends a request to the media application and receives media information from the application. The received media information may include an order of media items and an identifier for each item in the range of items. The received information may be sent to the client application for displaying information about the range of items.
Abstract:
Third-party apps on a mobile device can expose their content, such as audio content, video content, music stations, audio books, and so forth, to an in-vehicle computing device via a standardized format for content items that is decoupled from the user interfaces of the third-party apps. In this way, the in-vehicle computing device can display the content items in an in-vehicle user interface without granting providers of the content items access to the in-vehicle user interface. This system can present the content items in a different, independent user interface, even though the content items are associated with a third-party app having its own user interface. Content items encapsulate metadata describing the media, such as a title, subtitle, artwork, playback progress, a content item type, whether the content item is playable, whether the content item is a container item, and so forth.
Abstract:
Third-party apps on a mobile device can expose their content, such as audio content, video content, music stations, audio books, and so forth, to an in-vehicle computing device via a standardized format for content items that is decoupled from the user interfaces of the third-party apps. In this way, the in-vehicle computing device can display the content items in an in-vehicle user interface without granting providers of the content items access to the in-vehicle user interface. This system can present the content items in a different, independent user interface, even though the content items are associated with a third-party app having its own user interface. Content items encapsulate metadata describing the media, such as a title, subtitle, artwork, playback progress, a content item type, whether the content item is playable, whether the content item is a container item, and so forth.
Abstract:
Third-party apps on a mobile device can expose their content, such as audio content, video content, music stations, audio books, and so forth, to an in-vehicle computing device via a standardized format for content items that is decoupled from the user interfaces of the third-party apps. In this way, the in-vehicle computing device can display the content items in an in-vehicle user interface without granting providers of the content items access to the in-vehicle user interface. This system can present the content items in a different, independent user interface, even though the content items are associated with a third-party app having its own user interface. Content items encapsulate metadata describing the media, such as a title, subtitle, artwork, playback progress, a content item type, whether the content item is playable, whether the content item is a container item, and so forth.