在设计应用时，请注意应用的使用体验在一定程度上取决于用户是在 Android Auto 还是 Google 内置（可由汽车制造商自定义）上运行应用。本部分介绍的流程适用于 Android for Cars 系统（Android Auto 和 AAOS），但在另有说明的情况下除外（例如，对于搭载 Google 产品的汽车）。
应用的合作伙伴角色
多方合作伙伴共同打造 Android for Cars 中的应用体验：应用开发者、Google 和汽车制造商。
应用开发者、Google 和汽车制造商通力合作，共同打造 Android for Cars 中的应用体验。每位合作伙伴的设计责任取决于他们开发的应用类型。虽然使用 Android for Cars 应用库 (CAL) 模板创建的应用遵循特定的合作伙伴模式，但界面较不灵活的应用或专为停车状态和乘客使用而设计的应用遵循不同的模式。
[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eAndroid for Cars app design varies based on usage (driving vs.parked) and app type.\u003c/p\u003e\n"],["\u003cp\u003eTemplates are available for creating navigation, POI, IoT, and weather apps for Cars.\u003c/p\u003e\n"],["\u003cp\u003eMedia apps require adapting content and actions to a driving-optimized UI.\u003c/p\u003e\n"],["\u003cp\u003eExisting video apps can be adapted for parked/passenger experiences in cars with Google built-in.\u003c/p\u003e\n"],["\u003cp\u003eUser experience can differ between Android Auto and AAOS versions of an app.\u003c/p\u003e\n"]]],[],null,["# Design process\n\n\u003cbr /\u003e\n\nThe type of app and its use case --- whether it's for use while driving or parked\n--- determines the design process for *Android for Cars* apps.\n\nSome apps are built on templates that work for both driving and parked\nscenarios. Others apps, like media apps, need to have app content and actions\nthat are optimized for a driving UI.\n\nIf the car has Google built-in, you can adapt an existing app for the car\nscreen to deliver parked and passenger experiences.\n\nIn-car app experience\n---------------------\n\nUsers can experience Android apps in cars through two ways:\nAndroid Auto (projected from phones) or Android Automotive OS with\nGoogle built-in. \n**Projected from phones (Android Auto)**\n\n\n\u003cbr /\u003e\n\nAndroid Auto users can access compatible applications on their in-car\nscreen,right from their phones. The app's interface is projected from the\nuser's mobile phone to the in-car screen, either through a wireless or USB\nconnection.\n\n\n\u003cbr /\u003e\n\n\nThe visual presentation of the app, including color schemes and styling,\nremain consistent across all compatible cars.\n\n**Downloaded into cars (Google built-in)**\n\n\n\u003cbr /\u003e\n\nCars with AAOS provide users with the capability to install apps\ndirectly from the Google Play Store within the car's infotainment system,\nwithout the need to connect a mobile phone.\n\n\nCar makers (OEMs) can modify color palettes and styling of installed\napps to align to their brand's visual identity.\n\n\n\u003cbr /\u003e\n\nWhen your app is downloaded into cars, vehicle OEMs can adjust colors and\n[customize styling](/cars/design/create-apps/apps-for-drivers/customize-app) to fit specific vehicle models.\n\n\u003cbr /\u003e\n\nAs you design your app, keep in mind that the experience of using it can\ndepend partly on whether users are running the app on *Android Auto* or on\n*Google built-in*\n(which is customizable by car makers). The processes described in this section\nwork for both Android for Cars systems\n([Android Auto](/cars/design/android-auto) and\n[AAOS](/cars/design/automotive-os)) except where otherwise noted - for example,\nfor cars with Google built-in.\n\nPartner roles for apps\n----------------------\n\nMultiple partners contribute to the app experience in Android for Cars: app\ndevelopers, Google, and car makers.\n\nApp developers, Google, and car makers collaborate to create the app experience\nin Android for Cars. Each partner's design responsibilities depend on the type\nof app they are developing. While apps created using Android for\nCars App Library (CAL) templates follow a specific partnership model,\nthose with less flexible UIs or those designed for parked and passenger\nuse follow a different model.\n\nFor more details about some of these partnership models, refer to\nthe following table.\n\n| Type of app | Discussions of partner roles in app design |\n|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Apps created with the Android for Cars App Library | - [Who handles what](/cars/design/create-apps/apps-for-drivers/build-with-templates#who) - [Visual design customization](/cars/design/create-apps/apps-for-drivers/customize-app#visual) |\n| Media apps | - [Partner roles for media](/cars/design/create-apps/media-apps/overview#roles) |\n\nFor an overview of partner roles for the overall AAOS experience, including\nsystem UI, see\n[Partner roles](/cars/design/automotive-os/product-experience/partner-roles).\n[](/cars/design/create-apps/apps-for-drivers/build-with-templates) [Build apps with templates\n-------------------------](/cars/design/create-apps/apps-for-drivers/build-with-templates)\n\nUse the templates in the Android for Cars App Library to create apps in\nthese categories: navigation, point-of-interest, Internet of Things (IoT), and\nweather\n[](/cars/design/create-apps/media-apps/overview) [Create media apps\n-----------------](/cars/design/create-apps/media-apps/overview)\n\nCreate a version of your audio-content app for the Android for Cars UI \n[](/cars/design/create-apps/parked-passenger-apps/overview) [Adapt parked apps\n-----------------](/cars/design/create-apps/parked-passenger-apps/overview)\n\nDownload guidelines for adapting existing parked apps to work in cars with\nGoogle built-in\n\n\u003cbr /\u003e"]]
