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,["# Apps\n\nAn app is a focused view that handles tasks that are too complex for a complication,\ntile, or notification. Apps on Wear OS are similar to a mobile app's main user interface. Use\nsurfaces such as tiles, complications, and notifications to accomplish simple tasks, but link\nthese surfaces into an app to carry out more complex tasks.\n\n\nReview the following principles and use cases for a better understanding of apps.\n\nUX principles\n-------------\n\n\nDesign apps with the following principles in mind:\n\nFocus\n: Focus apps on critical tasks to help people get things done within seconds to avoid\n ergonomic discomfort or arm fatigue\n\nShallow and linear\n: Avoid hierarchies deeper than two levels. Show navigation inline\n\nScroll\n: Views can scroll. This is a natural gesture for users to see more content on the watch\n\nWhen to use an app\n------------------\n\n\nUse apps in the following situations:\n\nFor additional info\n: Focus apps on critical tasks to help people get things done within seconds to avoid\n ergonomic discomfort or arm fatigue.\n\nFor richer interactions\n: To provide richer interaction than a complication or Tile.\n\nFor adjusting preferences\n: To provide access to education and preferences.\n\nBuilding an app\n---------------\n\nWear OS supports two distinctive ways of building an app:\n\n- [Compose-based UI](/training/wearables/compose)\n- [View-based UI](/training/wearables/views)\n\nCompose for Wear OS is a modern declarative UI toolkit and is the recommended\napproach for building apps on Wear OS.\n\nCompose-based UIs in most cases result in less code and accelerates the development process of\nAndroid apps as a whole. See [Why Compose](/jetpack/compose/why-adopt) for more\ninformation on the general advantages of a declarative UI framework.\n\nThe Compose Material Catalog for Wear OS follows material styling, includes built in\naccessibility, and implements material theming, which allows you to customize the design for your\nbrand. Compose for Wear OS offers more components than are available with Views, and is designed\nto help you create user experiences that conform to Wear OS design guidelines.\n\nIf you have an existing Wear OS app with a large view-based codebase, it's possible to gradually\nadopt Compose by using the\n[Compose Interoperability APIs](/jetpack/compose/interop/interop-apis) rather than\nhaving to rewrite the whole codebase.\n\nGuides for creating apps with Compose\n-------------------------------------\n\n[Use Jetpack Compose on Wear OS](/training/wearables/apps/lists)\n: Learn how to build with Compose for Wear OS.\n\n[Create lists](/training/wearables/compose/lists)\n: Learn how to create lists that are optimized for wearable devices.\n\n[Navigating with Compose for Wear OS](/training/wearables/compose/navigation)\n: Learn more about building navigation in Compose.\n\n[Compose performance on Wear OS](/training/wearables/compose/performance)\n: Learn more about performance and testing your app performance."]]
