Edge To Edge
Android (Google)OfficialCreated by Google LLCDistributed by Android (Google)
- Skill
- Guidelines
- Software development
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach for developers to implement edge-to-edge support in Android Jetpack Compose applications. It covers the necessary configuration for Activities, proper handling of system insets to prevent UI obstruction, and specific patterns for managing IME (soft keyboard) interactions. The guide also addresses legibility concerns for system bars and provides best practices for full-screen dialogs and scrollable lists to ensure a modern, immersive user experience.
What it does
- Enables edge-to-edge display support for Jetpack Compose Activities.
- Provides patterns for applying system insets to prevent UI overlap.
- Offers solutions for managing IME padding to keep input fields visible.
- Includes techniques for ensuring system bar icon legibility.
- Details configuration for full-screen edge-to-edge dialogs.
- Provides a checklist for verifying edge-to-edge implementation.
When to use it
- When migrating an existing Jetpack Compose app to support edge-to-edge layouts.
- When UI components like buttons or lists are obscured by system bars.
- When the soft keyboard overlaps input fields in your application.
- When you need to ensure system bar icons remain visible against app content.
Advantages
- Ensures critical UI remains tappable and visible.
- Prevents common issues like double padding or clipped content.
- Provides clear 'right' vs 'wrong' code patterns for complex scenarios.
- Supports modern Android design standards for immersive apps.
Usage examples
- “How do I make my Jetpack Compose app edge-to-edge?”
- The agent will guide you through adding enableEdgeToEdge in your Activity's onCreate and applying appropriate insets to your UI components.
- “My text field is hidden when the keyboard opens, how do I fix it?”
- The agent will explain how to configure adjustResize in your manifest and apply correct IME padding or fitInside modifiers to your content.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/android/edge-to-edge/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip edge-to-edge.zip -d .agents/skills
Documentation by Google LLC
Prerequisites
Project MUST use Android Jetpack Compose.
Project MUST target SDK 35 or later. If the SDK is lower than 35, increase the SDK to 35.
Step 1: plan
Locate and analyze all Activity classes to detect which have existing edge-to-edge support. For every Activity without edge-to-edge, plan to make each Activity edge-to-edge.
In each Activity, Locate and analyze all lists and FAB components to detect which have existing edge-to-edge support. For every component without edge-to-edge support, plan to make each of these components edge-to-edge.
In each Activity, scan for
TextField,OutlinedTextField, orBasicTextField. If found, then you MUST verify the IME doesn't hide the input field by following the IME section of this skill.
Step 2: add edge-to-edge support
Add
enableEdgeToEdgebeforesetContentinonCreatein each Activity that does not already callenableEdgeToEdge.Add
android:windowSoftInputMode="adjustResize"in the AndroidManifest.xml for all Activities that use a soft keyboard.
Step 3: apply insets
The app MUST apply system insets, or align content to rulers, so critical UI remains tappable. Choose only one method to avoid double padding:
PREFERRED: When available, use
Scaffolds and passPaddingValuesto the content lambda.
Scaffold { innerPadding -> // innerPadding accounts for system bars and any Scaffold components LazyColumn( modifier = Modifier .fillMaxSize() .consumeWindowInsets(innerPadding), contentPadding = innerPadding ) { /* Content */ } }<br />
PREFERRED: When available, use the automatic inset handling or padding modifiers in material components.
Material 3 Components manages safe areas for its own components, including:
TopAppBarSmallTopAppBarCenterAlignedTopAppBarMediumTopAppBarLargeTopAppBarBottomAppBarModalDrawerSheetDismissibleDrawerSheetPermanentDrawerSheetModalBottomSheetNavigationBarNavigationRail
For Material 2 Components, use the
windowInsetsparameter to apply insets manually forBottomAppBar,TopAppBarandBottomNavigation. DO NOT apply padding to the parent container; instead, pass insets directly to the App Bar component. Applying padding to the parent container prevents the App Bar background from drawing into the system bar area. For example, forTopAppBar, choose only one of the following options:PREFERRED:
TopAppBar(windowInsets = AppBarDefaults.topAppBarWindowInsets)TopAppBar(windowInsets = WindowInsets.systemBars.exclude(WindowInsets.navigationBars))TopAppBar(windowInsets = WindowInsets.systemBars.add(WindowInsets.captionBar))
For components outside a Scaffold, use padding modifiers, such as
Modifier.safeDrawingPadding()orModifier.windowInsetsPadding(WindowInsets.safeDrawing).Box( modifier = Modifier .fillMaxSize() .safeDrawingPadding() ) { Button( onClick = {}, modifier = Modifier.align(Alignment.BottomCenter) ) { Text("Login") } }<br />
For deeply nested components with excessive padding, use
WindowInsetsRulers(e.g.Modifier.fitInside(WindowInsetsRulers.SafeDrawing.current)). See the IME section for a code sample.When you need an element (e.g. a custom header or decorative scrim) to equal the dimensions of a system bar, use inset size modifiers (e.g.
Modifier.windowInsetsTopHeight(WindowInsets.systemBars)). See the Lists section for a code sample.
Adaptive Scaffolds
NavigationSuiteScaffoldmanages safe areas for its own components, like theNavigationRailorNavigationBar. However, the adaptive scaffolds (e.g.NavigationSuiteScaffold,ListDetailPaneScaffold) don't propagate PaddingValues to their inner contents. You MUST apply insets to individual screens or components (e.g., listcontentPaddingor FAB padding) as described in Step 3 . DO NOT applysafeDrawingPaddingor similar modifiers to theNavigationSuiteScaffoldparent. This clips and prevents an edge-to-edge screen.
IME
For each Activity with a soft keyboard, check that
android:windowSoftInputMode="adjustResize"is set in the AndroidManifest.xml. DO NOT useSOFT_INPUT_ADJUST_RESIZEbecause it is deprecated. Then, maintain focus on the input field. Choose one:PREFERRED: Add
Modifier.fitInside(WindowInsetsRulers.Ime.current)to the content container. This is preferred overimePadding()because it reduces jank and extra padding caused by forgetting to consume insets upstream in the hierarchy.
Add
imePaddingto the content container. The padding modifier MUST be placed beforeModifier.verticalScroll(). Do NOT useModifier.imePadding()if the parent already accounts for the IME withcontentWindowInsets(e.g.contentWindowInsets = WindowInsets.safeDrawing). Doing so will cause double padding.
IMEs with Scaffolds code patterns
RIGHT
RIGHT because contentWindowInsets contains IME insets, which are passed to the
content lambda as innerPadding.
// RIGHT
Scaffold(contentWindowInsets = WindowInsets.safeDrawing) { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.consumeWindowInsets(innerPadding)
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
RIGHT because fitInside fits the content to the IME insets regardless of
contentWindowInsets.
// RIGHT
Scaffold() { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.consumeWindowInsets(innerPadding)
.fitInside(WindowInsetsRulers.Ime.current)
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
RIGHT because the default contentWindowInsets does not contain IME insets, and
imePadding() applies IME insets:
// RIGHT
Scaffold() { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.consumeWindowInsets(innerPadding)
.imePadding()
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
WRONG
WRONG because there will be excess padding when the IME opens. IME insets are
applied twice, once with innerPadding, which contains IME insets from the passed
contentWindowInsets values, and once with imePadding:
// WRONG
Scaffold(contentWindowInsets = WindowInsets.safeDrawing) { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.imePadding()
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
WRONG because the IME will cover up the content. Scaffold's default
contentWindowInsets does NOT contain IME insets.
// WRONG
Scaffold() { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
IMEs without Scaffolds code patterns
RIGHT
The following code samples WILL NOT cause excessive padding.
// RIGHT
Box(
// Insets consumed
modifier = Modifier.safeDrawingPadding() // or imePadding(), safeContentPadding(), safeGesturesPadding()
) {
Column(
modifier = Modifier.imePadding()
) { /* Content */ }
}<br />
// RIGHT
Box(
// Insets consumed
modifier = Modifier.windowInsetsPadding(WindowInsets.safeDrawing) // or WindowInsets.ime, WindowInsets.safeContent, WindowInsets.safeGestures
) {
Column(
modifier = Modifier.imePadding()
) { /* Content */ }
}<br />
// RIGHT
Box(
// Insets not consumed, but irrelevant due to fitInside
modifier = Modifier.padding(WindowInsets.safeDrawing.asPaddingValues()) // or WindowInsets.ime.asPaddingValues(), WindowInsets.safeContent.asPaddingValues(), WindowInsets.safeGestures.asPaddingValues()
) {
Column(
modifier = Modifier
.fillMaxSize()
.fitInside(WindowInsetsRulers.Ime.current)
) { /* Content */ }
}<br />
WRONG
The following code sample WILL cause excessive padding because IME insets are applied twice:
// WRONG
Box(
// Insets not consumed
modifier = Modifier.padding(WindowInsets.safeDrawing.asPaddingValues()) // or WindowInsets.ime.asPaddingValues(), WindowInsets.safeContent.asPaddingValues(), WindowInsets.safeGestures.asPaddingValues()
) {
Column(
modifier = Modifier.imePadding()
) { /* Content */ }
}<br />
Navigation Bar Contrast & System Bar Icons
If the Activity uses
enableEdgeToEdgefromWindowCompat, you MUST setisAppearanceLightNavigationBarsandisAppearanceLightStatusBarsto the inverse of the device theme for apps that support light and dark theme so the system bar icons are legible. It's recommended to do this in your theme file. DO NOT do this if the Activities useenableEdgeToEdgefromComponentActivitybecause it handles the icon colors automatically.// Only use if calling `enableEdgeToEdge` from `WindowCompat`. // Apply to your theme file. @Composable fun MyTheme( darkTheme: Boolean = isSystemInDarkTheme(), content: @Composable () -> Unit ) { val view = LocalView.current if (!view.isInEditMode) { SideEffect { val window = (view.context as? Activity)?.window ?: return@SideEffect val controller = WindowCompat.getInsetsController(window, view) // Dark icons for Light Mode (!darkTheme), Light icons for Dark Mode controller.isAppearanceLightStatusBars = !darkTheme controller.isAppearanceLightNavigationBars = !darkTheme } } MaterialTheme(content = content) }<br />
If any screen uses a
Scaffoldor aNavigationSuiteScaffoldwith a bottom bar (e.g.,BottomAppBar,NavigationBar), setwindow.isNavigationBarContrastEnforced = falsein the corresponding Activity for SDK 29+. This prevents the system from adding a translucent background to the navigation bar, verifying your bottom bar colors extend to the bottom of the screen.
Lists
Apply inset padding (like
Scaffold'sinnerPadding) to thecontentPaddingparameter of scrollable components (e.g.LazyColumn,LazyRow). DO NOT apply it as aModifier.padding()to the list's parent container, as this clips the content and prevents it from scrolling behind the system bars.Create a translucent composable covering the system bar so that the icons are still legible.
class SystemBarProtectionSnippets : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
// enableEdgeToEdge sets window.isNavigationBarContrastEnforced = true
// which is used to add a translucent scrim to three-button navigation
enableEdgeToEdge()
setContent {
MyTheme {
// Main content
MyContent()
// After drawing main content, draw status bar protection
StatusBarProtection()
}
}
}
}
@Composable
private fun StatusBarProtection(
color: Color = MaterialTheme.colorScheme.surfaceContainer,
) {
Spacer(
modifier = Modifier
.fillMaxWidth()
.height(
with(LocalDensity.current) {
(WindowInsets.statusBars.getTop(this) * 1.2f).toDp()
}
)
.background(
brush = Brush.verticalGradient(
colors = listOf(
color.copy(alpha = 1f),
color.copy(alpha = 0.8f),
Color.Transparent
)
)
)
)
}<br />
Dialogs
If both the following conditions are true, then the Dialog is full screen and must be made edge-to-edge:
The
DialogPropertiescontainsusePlatformDefaultWidth = false.The Dialog calls
Modifier.fillMaxSize().
To make a full screen Dialog edge-to-edge, set decorFitsSystemWindows = false
in the DialogProperties.
Dialog(
onDismissRequest = { /* Handle dismiss */ },
properties = DialogProperties(
// 1. Allows the dialog to span the full width of the screen
usePlatformDefaultWidth = false,
// 2. Allows the dialog to draw behind status and navigation bars
decorFitsSystemWindows = false
)
) { /* Content */ }<br />
Checklist
[ ] Does every
ActivitycallenableEdgeToEdge()?[ ] Is
adjustResizeset in theAndroidManifest.xml?[ ] Does every
TextField,OutlinedTextField, orBasicTextFieldhave a parent withimePadding(),fitInside,Modifier.safeDrawingPadding(),Modifier.safeContentPadding(),Modifier.safeGesturesPadding(), orcontentWindowInsetsset toWindowInsets.safeDrawingorWindowInsets.ime?[] Does the first and last list item draw away from the system bars by passing insets to
contentPadding?[] Do FABs draw above the navigation bars by either being inside a Scaffold or by applying
Modifier.safeDrawingPadding()?[] Does the project build? Run
./gradlew buildto be sure.
Files
- ATTRIBUTION.mdAdded by AutoGineer947 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md14.1 KiB
SKILL.md
Prerequisites
Project MUST use Android Jetpack Compose.
Project MUST target SDK 35 or later. If the SDK is lower than 35, increase the SDK to 35.
Step 1: plan
Locate and analyze all Activity classes to detect which have existing edge-to-edge support. For every Activity without edge-to-edge, plan to make each Activity edge-to-edge.
In each Activity, Locate and analyze all lists and FAB components to detect which have existing edge-to-edge support. For every component without edge-to-edge support, plan to make each of these components edge-to-edge.
In each Activity, scan for
TextField,OutlinedTextField, orBasicTextField. If found, then you MUST verify the IME doesn't hide the input field by following the IME section of this skill.
Step 2: add edge-to-edge support
Add
enableEdgeToEdgebeforesetContentinonCreatein each Activity that does not already callenableEdgeToEdge.Add
android:windowSoftInputMode="adjustResize"in the AndroidManifest.xml for all Activities that use a soft keyboard.
Step 3: apply insets
The app MUST apply system insets, or align content to rulers, so critical UI remains tappable. Choose only one method to avoid double padding:
PREFERRED: When available, use
Scaffolds and passPaddingValuesto the content lambda.
Scaffold { innerPadding -> // innerPadding accounts for system bars and any Scaffold components LazyColumn( modifier = Modifier .fillMaxSize() .consumeWindowInsets(innerPadding), contentPadding = innerPadding ) { /* Content */ } }<br />
PREFERRED: When available, use the automatic inset handling or padding modifiers in material components.
Material 3 Components manages safe areas for its own components, including:
TopAppBarSmallTopAppBarCenterAlignedTopAppBarMediumTopAppBarLargeTopAppBarBottomAppBarModalDrawerSheetDismissibleDrawerSheetPermanentDrawerSheetModalBottomSheetNavigationBarNavigationRail
For Material 2 Components, use the
windowInsetsparameter to apply insets manually forBottomAppBar,TopAppBarandBottomNavigation. DO NOT apply padding to the parent container; instead, pass insets directly to the App Bar component. Applying padding to the parent container prevents the App Bar background from drawing into the system bar area. For example, forTopAppBar, choose only one of the following options:PREFERRED:
TopAppBar(windowInsets = AppBarDefaults.topAppBarWindowInsets)TopAppBar(windowInsets = WindowInsets.systemBars.exclude(WindowInsets.navigationBars))TopAppBar(windowInsets = WindowInsets.systemBars.add(WindowInsets.captionBar))
For components outside a Scaffold, use padding modifiers, such as
Modifier.safeDrawingPadding()orModifier.windowInsetsPadding(WindowInsets.safeDrawing).Box( modifier = Modifier .fillMaxSize() .safeDrawingPadding() ) { Button( onClick = {}, modifier = Modifier.align(Alignment.BottomCenter) ) { Text("Login") } }<br />
For deeply nested components with excessive padding, use
WindowInsetsRulers(e.g.Modifier.fitInside(WindowInsetsRulers.SafeDrawing.current)). See the IME section for a code sample.When you need an element (e.g. a custom header or decorative scrim) to equal the dimensions of a system bar, use inset size modifiers (e.g.
Modifier.windowInsetsTopHeight(WindowInsets.systemBars)). See the Lists section for a code sample.
Adaptive Scaffolds
NavigationSuiteScaffoldmanages safe areas for its own components, like theNavigationRailorNavigationBar. However, the adaptive scaffolds (e.g.NavigationSuiteScaffold,ListDetailPaneScaffold) don't propagate PaddingValues to their inner contents. You MUST apply insets to individual screens or components (e.g., listcontentPaddingor FAB padding) as described in Step 3 . DO NOT applysafeDrawingPaddingor similar modifiers to theNavigationSuiteScaffoldparent. This clips and prevents an edge-to-edge screen.
IME
For each Activity with a soft keyboard, check that
android:windowSoftInputMode="adjustResize"is set in the AndroidManifest.xml. DO NOT useSOFT_INPUT_ADJUST_RESIZEbecause it is deprecated. Then, maintain focus on the input field. Choose one:PREFERRED: Add
Modifier.fitInside(WindowInsetsRulers.Ime.current)to the content container. This is preferred overimePadding()because it reduces jank and extra padding caused by forgetting to consume insets upstream in the hierarchy.
Add
imePaddingto the content container. The padding modifier MUST be placed beforeModifier.verticalScroll(). Do NOT useModifier.imePadding()if the parent already accounts for the IME withcontentWindowInsets(e.g.contentWindowInsets = WindowInsets.safeDrawing). Doing so will cause double padding.
IMEs with Scaffolds code patterns
RIGHT
RIGHT because contentWindowInsets contains IME insets, which are passed to the
content lambda as innerPadding.
// RIGHT
Scaffold(contentWindowInsets = WindowInsets.safeDrawing) { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.consumeWindowInsets(innerPadding)
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
RIGHT because fitInside fits the content to the IME insets regardless of
contentWindowInsets.
// RIGHT
Scaffold() { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.consumeWindowInsets(innerPadding)
.fitInside(WindowInsetsRulers.Ime.current)
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
RIGHT because the default contentWindowInsets does not contain IME insets, and
imePadding() applies IME insets:
// RIGHT
Scaffold() { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.consumeWindowInsets(innerPadding)
.imePadding()
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
WRONG
WRONG because there will be excess padding when the IME opens. IME insets are
applied twice, once with innerPadding, which contains IME insets from the passed
contentWindowInsets values, and once with imePadding:
// WRONG
Scaffold(contentWindowInsets = WindowInsets.safeDrawing) { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.imePadding()
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
WRONG because the IME will cover up the content. Scaffold's default
contentWindowInsets does NOT contain IME insets.
// WRONG
Scaffold() { innerPadding ->
Column(
modifier = Modifier
.padding(innerPadding)
.verticalScroll(rememberScrollState())
) { /* Content */ }
}<br />
IMEs without Scaffolds code patterns
RIGHT
The following code samples WILL NOT cause excessive padding.
// RIGHT
Box(
// Insets consumed
modifier = Modifier.safeDrawingPadding() // or imePadding(), safeContentPadding(), safeGesturesPadding()
) {
Column(
modifier = Modifier.imePadding()
) { /* Content */ }
}<br />
// RIGHT
Box(
// Insets consumed
modifier = Modifier.windowInsetsPadding(WindowInsets.safeDrawing) // or WindowInsets.ime, WindowInsets.safeContent, WindowInsets.safeGestures
) {
Column(
modifier = Modifier.imePadding()
) { /* Content */ }
}<br />
// RIGHT
Box(
// Insets not consumed, but irrelevant due to fitInside
modifier = Modifier.padding(WindowInsets.safeDrawing.asPaddingValues()) // or WindowInsets.ime.asPaddingValues(), WindowInsets.safeContent.asPaddingValues(), WindowInsets.safeGestures.asPaddingValues()
) {
Column(
modifier = Modifier
.fillMaxSize()
.fitInside(WindowInsetsRulers.Ime.current)
) { /* Content */ }
}<br />
WRONG
The following code sample WILL cause excessive padding because IME insets are applied twice:
// WRONG
Box(
// Insets not consumed
modifier = Modifier.padding(WindowInsets.safeDrawing.asPaddingValues()) // or WindowInsets.ime.asPaddingValues(), WindowInsets.safeContent.asPaddingValues(), WindowInsets.safeGestures.asPaddingValues()
) {
Column(
modifier = Modifier.imePadding()
) { /* Content */ }
}<br />
Navigation Bar Contrast & System Bar Icons
If the Activity uses
enableEdgeToEdgefromWindowCompat, you MUST setisAppearanceLightNavigationBarsandisAppearanceLightStatusBarsto the inverse of the device theme for apps that support light and dark theme so the system bar icons are legible. It's recommended to do this in your theme file. DO NOT do this if the Activities useenableEdgeToEdgefromComponentActivitybecause it handles the icon colors automatically.// Only use if calling `enableEdgeToEdge` from `WindowCompat`. // Apply to your theme file. @Composable fun MyTheme( darkTheme: Boolean = isSystemInDarkTheme(), content: @Composable () -> Unit ) { val view = LocalView.current if (!view.isInEditMode) { SideEffect { val window = (view.context as? Activity)?.window ?: return@SideEffect val controller = WindowCompat.getInsetsController(window, view) // Dark icons for Light Mode (!darkTheme), Light icons for Dark Mode controller.isAppearanceLightStatusBars = !darkTheme controller.isAppearanceLightNavigationBars = !darkTheme } } MaterialTheme(content = content) }<br />
If any screen uses a
Scaffoldor aNavigationSuiteScaffoldwith a bottom bar (e.g.,BottomAppBar,NavigationBar), setwindow.isNavigationBarContrastEnforced = falsein the corresponding Activity for SDK 29+. This prevents the system from adding a translucent background to the navigation bar, verifying your bottom bar colors extend to the bottom of the screen.
Lists
Apply inset padding (like
Scaffold'sinnerPadding) to thecontentPaddingparameter of scrollable components (e.g.LazyColumn,LazyRow). DO NOT apply it as aModifier.padding()to the list's parent container, as this clips the content and prevents it from scrolling behind the system bars.Create a translucent composable covering the system bar so that the icons are still legible.
class SystemBarProtectionSnippets : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
// enableEdgeToEdge sets window.isNavigationBarContrastEnforced = true
// which is used to add a translucent scrim to three-button navigation
enableEdgeToEdge()
setContent {
MyTheme {
// Main content
MyContent()
// After drawing main content, draw status bar protection
StatusBarProtection()
}
}
}
}
@Composable
private fun StatusBarProtection(
color: Color = MaterialTheme.colorScheme.surfaceContainer,
) {
Spacer(
modifier = Modifier
.fillMaxWidth()
.height(
with(LocalDensity.current) {
(WindowInsets.statusBars.getTop(this) * 1.2f).toDp()
}
)
.background(
brush = Brush.verticalGradient(
colors = listOf(
color.copy(alpha = 1f),
color.copy(alpha = 0.8f),
Color.Transparent
)
)
)
)
}<br />
Dialogs
If both the following conditions are true, then the Dialog is full screen and must be made edge-to-edge:
The
DialogPropertiescontainsusePlatformDefaultWidth = false.The Dialog calls
Modifier.fillMaxSize().
To make a full screen Dialog edge-to-edge, set decorFitsSystemWindows = false
in the DialogProperties.
Dialog(
onDismissRequest = { /* Handle dismiss */ },
properties = DialogProperties(
// 1. Allows the dialog to span the full width of the screen
usePlatformDefaultWidth = false,
// 2. Allows the dialog to draw behind status and navigation bars
decorFitsSystemWindows = false
)
) { /* Content */ }<br />
Checklist
[ ] Does every
ActivitycallenableEdgeToEdge()?[ ] Is
adjustResizeset in theAndroidManifest.xml?[ ] Does every
TextField,OutlinedTextField, orBasicTextFieldhave a parent withimePadding(),fitInside,Modifier.safeDrawingPadding(),Modifier.safeContentPadding(),Modifier.safeGesturesPadding(), orcontentWindowInsetsset toWindowInsets.safeDrawingorWindowInsets.ime?[] Does the first and last list item draw away from the system bars by passing insets to
contentPadding?[] Do FABs draw above the navigation bars by either being inside a Scaffold or by applying
Modifier.safeDrawingPadding()?[] Does the project build? Run
./gradlew buildto be sure.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Google LLC
- Publisher
- Android (Google) (Official)
- Distributed by
- Android (Google)
- Source
- android/skills · system/edge-to-edge · commit bf68e2d
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE.txt)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google LLC or Android (Google).
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download edge-to-edge.zip