Tiles Jetpack 라이브러리는 사용자가 작업을 완료하는 데 필요한 앱 데이터에 쉽게 액세스할 수 있도록 합니다. 사용자는 시계 화면에서 빠른 스와이프로 카드를 스크롤하면서 자주 사용하는 서비스의 정보와 작업을 볼 수 있습니다. 이 Codelab에서 첫 번째 카드를 빌드하는 방법을 알아봅니다.
[[["이해하기 쉬움","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"]],[],[],[],null,["# Wear OS user interfaces\n\nWear OS makes it easy for users to engage with apps optimized for a watch.\nEnsure that content is displayed on the appropriate surface.\n\nApp surfaces on Wear OS are designed with jobs in mind. For example, if you\nhave a single unit of information that users are likely to want to glance at\nmultiple times a day, consider providing a complication. If your content is\nhigh-value and highly contextual, consider a notification instead.\n\nAnother useful way to design app content intuitively on Wear OS is to consider\nthe priority of information across surfaces, elevating the most valuable content\nto Wear OS's glanceable surfaces.\n\nDisplay the highest-priority content in complications and notifications, and\nthen use the larger space on tiles and your app to display more content\nappropriately.\n\nThe following sections cover each of these surfaces in more detail.\n\nApp\n---\n\nAn app is a focused view that can serve a complex or less-common task or\na cluster of tasks. An app is immersive, and it's similar to a mobile app's\nmain user interface (UI), though there are some differences.\n| **Note:** Consider using [Compose for Wear OS](/training/wearables/compose) to create your app. Compose for Wear OS is a modern declarative UI toolkit and is the recommended approach for building apps on Wear OS.\n\nOther surfaces (tiles, complications, and notifications) can link into an\napp to let users carry out more complex tasks.\n\n**Figure 1.** You can use an app to start a workout, browse a playlist, send\na message, or review workout data.\n\nTiles\n-----\n\nTiles provide quick, predictable access to information and actions to solve\nuser needs.\n\nWhile apps can be immersive, tiles are fast-loading and focus on the user's\nimmediate needs. If users want more information, they can tap tiles to open an\napp on the watch.\n\n**Figure 2.** Use tiles to track the user's daily activity progress,\nquick-start a workout, start a recently played song, or send a message to a\nfavorite contact.\n\nNotifications\n-------------\n\nA notification provides glanceable, time-sensitive information and actions for\nthe user. Notifications on Wear OS are similar to mobile notifications.\n| **Note:** You can combine ongoing notifications that have a background task with an ongoing activity to appear on additional surfaces within the Wear OS user interface. This keeps users more engaged with long running activities.\n\n**Figure 4.** Use a notification to show a new message or email, track a\nworkout after the user has left the app, or show information on the current\nsong playing.\n\nApp launcher entries\n--------------------\n\nApp launcher entries help users start and return to experiences on their watch.\nTapping a shortcut launches an app.\n\nDevices support at least one of the following app launcher experiences:\n\n- **Grid view:** The icons appear next to each other both vertically and horizontally, as shown in figure 5. Available on all devices that run Wear OS 5 and higher, and on some devices that run previous versions of Wear OS.\n- **List view:** The icons appear next to each other vertically, as shown in figure 6. Available on almost all devices that run Wear OS, and on all devices that don't support the grid view.\n\nIf a device supports both types of views, switch between the two using system\nsettings. \n**Figure 5.** The grid-based app launcher view. \n**Figure 6.** The list-based app launcher view.\n\nWatch faces\n-----------\n\nWatch faces are dynamic, digital canvases where users can express their style.\nMost apps don't need to create a custom watch face. However, if creating a watch\nface makes sense for your app, Wear OS lets you customize the surface\nas much as you want.\n\n**Figure 7.** Use a custom watch face to show a customized analog timepiece\nor a customized digital timepiece that displays complications.\n\nComplications\n-------------\n\nA complication is a single, often-repeated action or a highly glanceable unit of\ninformation on the watch face. As with tiles, users can tap complications to\nopen an app on the watch for a deeper experience.\n\n**Figure 3.** Use complications to track the date, the user's water intake or\nsteps, or the current weather."]]
