[null,null,["อัปเดตล่าสุด 2025-08-28 UTC"],[],[],null,["Inputs, content, or other actions may appear relative to each other or\nconstrained to a parent container. Layouts can be more custom, but make sure to\nfollow consistent grouping, columns, and spacing.\n\nAuthentication is a common relative layout, as shown in the following figure. Where a custom layout is described by how the UI elements in relation to each other.\n\nLayouts can also use a combination of layout types. For example, you might pair a\ncarousel or horizontal scroll with vertical cards. Or, you could present a\ncustom chart with vertical list data.\n\nYou can present content in scrolling rows or columns with lazy rows and lazy\ncolumns.\n\nFull-screen layout is another common layout, as used in [immersive mode](/design/ui/mobile/guides/layout-and-content/immersive-content).\n**Figure 27:** Full screen layout, as used in immersive mode\n\nIf you're working with Views instead of Compose, you can use\n[`ConstraintLayout`](/develop/ui/views/layout/constraint-layout) to lay out views according to relationships between\nsibling views and the parent layout, allowing for large and complex layouts.\n`ConstraintLayout` lets you build entirely by dragging and dropping instead of\nediting the XML using the layout editor. Learn more about [building a UI with\nLayout Editor](/studio/write/layout-editor).\n\nLearn more about [Compose layout basics](/develop/ui/compose/layouts/basics) and what makes up a composable.\n\nWebviews\n\nA Webview is a view that displays in-app web pages. In most cases, we recommend\nusing a standard web browser, like Chrome, to deliver content to the user. To\nlearn more about web browsers, read the guide for [invoking a browser with an\nintent](/guide/components/intents-common#Browser)."]]
