[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-25(UTC)"],[[["\u003cp\u003eDesign task flows with 5 steps or fewer to minimize driver distraction, utilizing subflows and shortcuts when necessary.\u003c/p\u003e\n"],["\u003cp\u003eUnderstand how steps are counted, including template transitions and content refreshes, to stay within the step limit.\u003c/p\u003e\n"],["\u003cp\u003eLeverage the Adaptive task limits feature, when available, to allow longer task flows while parked and benefit from throttled refreshes.\u003c/p\u003e\n"],["\u003cp\u003eAvoid specific template sequences, like ending with List or Grid templates in 5-step flows or having 5 list-based templates in a row.\u003c/p\u003e\n"],["\u003cp\u003eUtilize interactive map features in navigation apps to enhance user experience without impacting the step count.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\nAs you sequence templates into task flows, choose the templates that will best\nfit each task and strategize to keep task flows short.\n\nWhile the [templates](/cars/design/create-apps/apps-for-drivers/templates/overview)\nin the app library are designed for usability while driving (except those that\nare \"parked only\"), it's also important to\n[keep task flows short](#short). Keeping task flows to 5 steps or fewer helps\ndrivers to keep their attention on the road.\n\nAs you design your flows, make sure you understand how to:\n\n- **Count steps** ([Step counts and refreshes](#steps-refreshes).)\n- **Sequence templates appropriately** ([Template order in task flows](#order), [Add subflows](#add_subflows))\n- **Gain flexibility in task length** via [Adaptive task limits](#task-limits), a feature that allows task flows greater than 5 steps under certain circumstances\n- **Use template features that promote task efficiency** , such as [interactive maps](#maps) (features are detailed in the [Templates](/cars/design/create-apps/apps-for-drivers/templates/overview) section)\n\nKeeping task flows short\n\nTo minimize driver distraction, keep task flows as short as possible.\nSample task flow with a subflow\n\nA new task starts when the user performs any of the following actions:\n\n- Lands on (or returns to) the app's landing template\n- Chooses an action that opens another app\n- Lands on the [Navigation template](/cars/design/create-apps/apps-for-drivers/templates/navigation-template) (in navigation apps)\n\nTo minimize required driver attention, keep task flows to 3 steps or fewer when\npossible (4 steps or fewer for\n[flows involving purchases](/cars/design/create-apps/sample-flows/purchase-with-existing-method)).\nWhen flows are longer than 3 or 4 steps, consider providing shortcuts back to\nearlier steps.\n\nExcept as noted in [Step counts and refreshes](#steps-refreshes), the limit is 5\nsteps, including the starting and ending steps.\n| **Note:** Exceeding 5 steps for a task is possible only if the [Adaptive task limits](#task-limits) feature is enabled.\n\nTemplate order in task flows\n\nWhen creating task flows, keep the following template ordering considerations\nin mind:\n\n- **Avoid List and Grid templates for step 5.** If the flow involves 5 steps, the final step must not be a list- or grid-based template (examples of acceptable templates include [Navigation](/cars/design/create-apps/apps-for-drivers/templates/navigation-template), [Message](/cars/design/create-apps/apps-for-drivers/templates/message-template), and [Pane](/cars/design/create-apps/apps-for-drivers/templates/pane-template)).\n- **Don't put 5 Lists or Grids in a row.** Apps should not create flows with 5 list-based or grid-based templates in a row, even if one of those templates is in a subflow.\n\nStep counts and refreshes\n\nTo design task flows that don't exceed the 5-step limit, it's important to\nunderstand how steps are counted for each flow.\n\nThe step count is **incremented** whenever one of the following occurs:\n\n- A new template is shown\n- The same template is shown with new content -- unless the new content is a refresh of existing content, as defined in [What is a refresh?](#refresh)\n\nThe step count **decreases by 1** if the task returns to the previous view with\nthe same content.\nIn both of these examples, a step is added as the user browses and selects a place from the Place List.\n\nFor more examples of how step counts would be incremented in specific task\nflows, see [Sample flows](/cars/design/create-apps/sample-flows/overview).\n\nWhat is a refresh?\n\nRefreshes are updates to a template's content that don't increment the step\ncount. Refreshes are almost always app-initiated. The only exception is when a\nuser [refreshes a list with the refresh button](/cars/design/create-apps/sample-flows/refresh-with-button)\non the Place List template.\n\nWhat qualifies as a refresh depends on the template and whether the\n[Adaptive task limits](#task-limits) feature is enabled. If this feature is\nenabled, the definition of what qualifies as a refresh is widened for some\ntemplates (see the following table), because the refreshes are throttled during\ndrives to minimize distraction.\n\nFor example, with the feature enabled, updates that change the number of rows on\nlist- or grid-based templates can be considered a refresh, as long as the title\nand any section names stay the same. If the feature is not enabled, changing the\nnumber of rows is a step count.\n\nFor examples of refreshes, see\n[Refresh vs step count example](#example) and [Sample flows](/cars/design/create-apps/sample-flows/overview).\n\n| Template type | What qualifies as a refresh | What qualifies as a refresh when Adaptive task limits feature is enabled |\n|----------------------------------------------------------------------------------------------|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| Navigation, Sign-in\\*, Long Message\\* | Any content update | Any content update |\n| List, Grid, Map, Pane, Place List (map), Place List (navigation), Route Preview, Search, Tab | See the template restrictions for each template | All updates where the layout stays the same, meaning: - Same title or tabs at the top And (on List template): \u003c!-- --\u003e - Same section names |\n| Message | Only updates that don't change the title and message (for example, adding a button) ||\n\n| **Note:** \\*For parked-only templates, the term refresh is typically not used, but steps are not limited, since the car is parked.\n\nRefresh vs. step count example\n\nIn this example, the [Adaptive task limits](#task-limits) feature is enabled, so\nany update with the same title qualifies as a refresh.\n\nBecause only the rows updated on one path, this would be considered a refresh.\nIf Adaptive task limits isn't enabled, this will count as a step. On the other\npath, the title changed, which increments the step count.\n\nAdaptive task limits\n\n**Adaptive task limits** is a feature that lets apps have task flows with more\nthan 5 steps under certain controlled circumstances, such as when parked or when\nrefreshes are being throttled while driving. Availability depends on location\nand discretion of vehicle OEMs (see note at right).\n\nWhen this feature is **enabled**:\n\n- **Task flows \\\u003e 5 steps are allowed while parked** (if driving, they will be paused after the 5th step and can be resumed when parked)\n- **Refreshes are throttled** during drives to be less distracting, so the definition of refresh is expanded to include more types of updates (see [What is a refresh?](#refresh)).\n\nWhen the feature is **not enabled**:\n\n- **Task flows must not exceed 5 steps**, or the app will crash\n- **Refreshes are not throttled during drives** so the definition of refresh is not expanded\n\n| **Note:** Keep in mind that this feature is not available for Japanese Automobile Manufacturers Association (JAMA)-affiliated Android Auto vehicles. Also, for AAOS, vehicle OEMs can selectively enable or disable this feature by app category. Before running any tasks that are longer than 5 steps, be sure to have your code check that this feature is enabled for the OEM and vehicle in question. To check if the feature is enabled, use the IsAppRefreshEnabled API.\n\nHow refresh throttling works\n\nWith throttled refreshes, apps can refresh the template as often as they want,\nbut the time between the refreshes is spaced out to minimize distraction. If\nmultiple refreshes are sent during the throttle period, the latest one is shown\nat the end of the period.\n\nInteractive maps\n\nDesign your app to include zooming and panning for navigation apps. Currently,\nusers can interact with maps via features (such as zooming and panning) in\ntemplates specific to navigation apps: Navigation, Route Preview, Map, and Place\nList (navigation).\n**Note:** The [Place List (map) template](/cars/design/create-apps/apps-for-drivers/templates/place-list-map-template) does not have an interactive map but does allow refresh of the list next to the map, as noted below. \nUsers can interact with maps using:\n\n- **Touchscreen gestures**, such as swiping to pan\n- **Taps** on specific areas of the map, such as points of interest\n- **[Buttons](/cars/design/create-apps/apps-for-drivers/components/button)** on the [map action strip](/cars/design/create-apps/apps-for-drivers/components/map-action-strip)\n- **A refresh button** that refreshes the information adjacent to the map (currently available only on the [Place List (map) template](/cars/design/create-apps/apps-for-drivers/templates/place-list-map-template) and the [Place List (navigation) template](/cars/design/create-apps/apps-for-drivers/templates/place-list-navigation-template))\nUsers zoom and pan to locate places on the map.\n\nRefreshing the content next to the map does not add to the\n[step count](#steps-refreshes) for a task flow."]]
