일반적으로 android.intent.category.CAR_LAUNCHER 카테고리 요소는 android.intent.category.LAUNCHER 요소와 동일한 인텐트 필터에 배치할 수 있지만 원하는 경우 다른 인텐트 필터에 배치할 수도 있습니다.
카테고리별 매니페스트 항목
게임에는 위의 요구사항 외에도 추가 요구사항이 있습니다.
앱을 게임으로 표시를 참고하세요.
일반적인 Android Auto 화면 크기 지원
최상의 사용자 환경을 제공하려면 앱을 다양한 화면 크기에 완전히 적응하도록 만드는 것이 좋습니다. Android Auto를 지원하는 다양한 자동차에서 최소한 높은 품질의 환경을 보장하려면 DO-2 자동차 앱 품질 가이드라인에 설명된 대로 가로 모드 화면에서 앱이 상당히 필러박스 처리되어서는 안 됩니다.
예를 들어 앱이 가로 모드 화면에서 필러박스 처리가 적용된 세로 모드 가로세로 비율로 실행되면 Play 스토어 검토 중에 거부됩니다. 가로 모드 화면에서 최소한의 필러박스 처리가 적용된 가로 모드 가로세로 비율로 실행되는 앱은 허용됩니다. 세로 모드 화면에서 레터박스 처리가 적용된 가로 모드 가로세로 비율로 실행되는 앱도 마찬가지입니다.
표준 화면 크기에 맞게 테스트
Android Auto용 앱을 빌드하고 테스트할 때 다음 데스크톱 헤드 단위 (DHU) 구성을 사용하여 앱이 위의 요구사항을 충족하는지 확인할 수 있습니다.
이 페이지에 나와 있는 콘텐츠와 코드 샘플에는 콘텐츠 라이선스에서 설명하는 라이선스가 적용됩니다. 자바 및 OpenJDK는 Oracle 및 Oracle 계열사의 상표 또는 등록 상표입니다.
최종 업데이트: 2025-08-08(UTC)
[null,null,["최종 업데이트: 2025-08-08(UTC)"],[],[],null,["# Add support for Android Auto to your parked app\n\nOn devices running Android 15 or higher, Android Auto supports running\napps in [supported parked app categories](/training/cars#parked) directly on the head unit. See\n[Parked apps](/training/cars/platforms/android-auto#parked-apps) for more information about the parked app user experience on\nAndroid Auto.\n\nDeclare Android Auto support\n----------------------------\n\nTo declare that your app supports Android Auto, you must include the following\n`\u003ccategory\u003e` element in the intent filter of an activity in your app's manifest: \n\n \u003cactivity ...\u003e\n \u003cintent-filter\u003e\n \u003caction android:name=\"android.intent.action.MAIN\" /\u003e\n ...\n \u003ccategory android:name=\"android.intent.category.CAR_LAUNCHER\" /\u003e\n \u003c/intent-filter\u003e\n \u003c/activity\u003e\n\nGenerally, the `android.intent.category.CAR_LAUNCHER` category element can\nbe placed in the same intent filter as the `android.intent.category.LAUNCHER`\nelement, but it can be in a different one if preferred.\n| **Caution:** Be careful not to promote builds that support Android Auto to track types other than those listed in [Supported app categories](/training/cars#parked), or your submission will be rejected [during review](/training/cars/distribute#understand-review).\n\n### Category-specific manifest entries\n\nIn addition to the preceding requirement, games have an additional requirement.\nSee [Mark your app as a game](/training/cars/parked/games#mark-game).\n| **Important:** Games are the only parked app category supported by Android Auto at this time.\n\nSupport common Android Auto screen sizes\n----------------------------------------\n\nFor the best user experience, we recommend making your app [fully adaptive](/develop/ui/compose/build-adaptive-apps)\nto different screen sizes. At the minimum, to ensure a high quality experience\nin the variety of cars that support Android Auto, apps **must not** be\nsignificantly pillarboxed on landscape screens, as captured by the [`DO-2`](/docs/quality-guidelines/car-app-quality#DO-2)\ncar app quality guideline.\n\nFor example, if an app runs in a portrait aspect ratio with pillarboxing on a\nlandscape screen, it will be rejected during Play Store review. An app running\nin a landscape aspect ratio with minimal pillarboxing on a landscape screen is\nacceptable, as is an app running in a landscape aspect ratio with letterboxing\non a portrait screen.\n| **Tip:** See [Support large screen resizability](/games/develop/multiplatform/support-large-screen-resizability) for game-specific guidance on adapting to different screen sizes.\n\n### Test against canonical screen sizes\n\nWhen building and testing your app for Android Auto, you can use the following\n[Desktop Head Unit (DHU) configurations](/training/cars/testing/dhu#configure-dhu) to verify that your app meets the\npreceding requirements: \n\n### Small Landscape\n\n [general]\n resolution = 800x480\n dpi = 160\n ...\n\n| **Tip:** This is the default configuration used when running the DHU, and represents the most common configuration for cars that support Android Auto.\n\n### Wide Landscape\n\n [general]\n resolution = 1920x1080\n dpi = 160\n marginheight = 596\n normalizedpi = true\n cropmargins = true\n ...\n\n### Portrait\n\n [general]\n resolution = 1920x1080\n dpi = 160\n marginwidth = 878\n normalizedpi = true\n cropmargins = true\n ...\n\nDetect usage on Android Auto\n----------------------------\n\nIf you'd like to detect when your app is being used through Android Auto (such\nas for analytics purposes), you can look at two signals:\n\n- The connection state reported by the [`CarConnection`](/training/cars/apps#car-connection) API. When Android Auto is connected, this will be [`CONNECTION_TYPE_PROJECTION`](/reference/androidx/car/app/connection/CarConnection#CONNECTION_TYPE_PROJECTION).\n- The display ID of the active display. When your app is running on a display other than a built-in screen, such as when used through Android Auto, this is a value other than [`DEFAULT_DISPLAY`](/reference/android/view/Display#DEFAULT_DISPLAY).\n\nThe following snippet shows how to combine these signals to detect usage through\nAndroid Auto: \n\n val connectionType = ...\n val displayId = context.display.displayId\n isRunningOnAndroidAuto = connectionType == CONNECTION_TYPE_PROJECTION and displayId != DEFAULT_DISPLAY\n\n| **Caution:** This method might not always be accurate. A device could be connected to both Android Auto and another display, and your app might be running on that other display."]]
