All posts

Android edge-to-edge: test for hidden buttons and text

· 7 min read

You raise your target SDK to keep your app on Google Play. You open it on a new phone. The top bar sits under the status bar. The bottom button is behind the gesture bar. Nothing crashed, but part of your app is hidden. I checked Google's pages in November 2026, and this post is what they say, how to fix it, and how to test it.

Short answer: newer target SDKs make your app draw edge-to-edge, behind the system bars. You must add padding for those bars yourself. Then test on gesture and 3-button navigation, in portrait and landscape, with a cutout, with the keyboard open, and at the end of every list.

What changed

Google's edge-to-edge guide says: "Once you target SDK 35 or higher on a device running Android 15 or higher, your app is displayed edge-to-edge." It adds: "If your app is not already edge-to-edge, portions of your app may be obscured and you must handle insets." Insets are the sizes of the system UI that you have to keep clear.

With Android 15 you could opt out. The Android 16 behavior changes page says that for apps targeting Android 16 (API level 36), windowOptOutEdgeToEdgeEnforcement "is deprecated and disabled, and your app can't opt-out of going edge-to-edge." On an Android 15 phone the same page says the attribute still works.

Why you may be raising your target now: Google Play's target API level page says "Starting August 31, 2026: New apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play". It lists exceptions for Wear OS, Android Automotive OS, Android TV and Android XR. It also says you can "request an extension to November 1, 2026". Check that page for your own situation.

What breaks

  • The top bar sits under the status bar or the camera cutout.
  • A bottom button or tab bar sits under the navigation bar.
  • The last item in a list can't be scrolled into view.
  • A floating button sits over the gesture area.
  • A text field is covered by the keyboard.
  • Status bar icons are the wrong color on your background.

Google's guide shows the floating button case: "the floating action button (FAB) in figure 3 is partially obscured by the navigation bar".

How to fix it

Views (XML)

Use system bar insets for things people tap. The guide says system bars insets are "best for views that are tappable and that must not be visually obscured by the system bars." Add the cutout type for lists:

ViewCompat
  .setOnApplyWindowInsetsListener(
    list) { v, insets ->
  val bars = insets.getInsets(
    WindowInsetsCompat.Type
      .systemBars() or
    WindowInsetsCompat.Type
      .displayCutout())
  v.updatePadding(
    bars.left, bars.top,
    bars.right, bars.bottom)
  WindowInsetsCompat.CONSUMED
}

The guide also says to check "that the last list item isn't obscured by the system bars" by handling insets and setting clipToPadding to false:

android:clipToPadding="false"

The guide says enableEdgeToEdge() "makes the system bars transparent, except on 3-button navigation mode where the navigation bar gets a translucent scrim." It also says that when you go edge-to-edge "you might need to manually update the system bar icon colors so they contrast with your app's background."

Compose

The Compose insets page says the Material 3 Scaffold "can reduce the work required to be compatible with the Android 15 edge-to-edge enforcement." For your own layouts it says to use WindowInsets.safeDrawing "to protect content that shouldn't be drawn underneath any system UI."

The keyboard

The keyboard has its own inset. The Compose page says WindowInsets.ime describes "the amount of space on the bottom that the software keyboard occupies." In Views, Google's keyboard page reads it like this:

val keyboardHeight = insets
  .getInsets(
    WindowInsetsCompat.Type.ime())
  .bottom

Keep the field the person is typing in above that height. The same page says to set the activity's windowSoftInputMode to adjustResize "to achieve the best backward compatibility with this AndroidX implementation."

Flutter

Flutter's breaking change page says "By default, apps targeting Android SDK 15+ will opt in to edge-to-edge mode." It also says that "as of Android 16, you can't" opt out. For layout, the SafeArea page says "SafeArea ensures that your app content won't be cut off in a generic way". Wrap your screen content:

SafeArea(
  child: MyScreen(),
)

React Native and Expo

The React Native SafeAreaView page says "Use react-native-safe-area-context instead", and that the built-in one is "only applicable to iOS devices". Expo's system bars page says "with edge-to-edge on Android, you will need to use safe areas to ensure that content does not overlap with system bars." Its safe area context page says "SafeAreaView is a regular View component with the safe area edges applied as padding." The hook gives you top, right, bottom and left numbers:

const insets = useSafeAreaInsets()
const pad = {
  paddingTop: insets.top,
  paddingBottom: insets.bottom,
}
// then: style={pad}

How to test it

Google's Android Help page "Select a Navigation mode" says to open Settings. On a Pixel you tap System, then Navigation mode. On other phones the page shows System, then Gestures, then Navigation mode. It describes the two modes this way: "Gesture navigation: To navigate between apps and other items, use swipe gestures rather than buttons." and "3-button navigation: In the navigation bar, at the bottom or side of your screen, use dedicated buttons for Home, Back, and Recents." See Google's navigation mode help page.

On the emulator or any phone, the display cutout page says to enable Developer options, scroll to the Drawing section and select "Simulate a display with a cutout". It also notes that in landscape "the cutout may be on the vertical edge."

SettingLook atPass if
Gesture navigationBottom buttons, tabs, floating buttonAll fully visible and tappable
3-button navigationSame screensNothing hidden by the bar
Portrait and landscapeTop bar, side edgesNothing cut off on either side
Cutout and no cutoutTop bar, titlesText clear of the camera
Keyboard openEvery formActive field and button visible
End of every listLast itemYou can scroll it fully into view
Light and dark themeStatus bar iconsIcons clearly readable

Google's Android 15 behavior changes page says "even if you think you aren't impacted, we recommend you test your app." It names onboarding, sign-in and settings screens as ones to check too.

A test task for testers

Paste this into your test task. For more on wording, see how to write a test task.

Test: is anything hidden or covered?

1. Open the app. Check the top bar
   and the bottom buttons.
2. Open Settings, then System, then
   Navigation mode. Try gestures,
   then 3-button. Look again.
3. Rotate the phone sideways. Look
   at every main screen.
4. Open every form. Tap each field.
   Is the field and the Save button
   still visible with the keyboard?
5. Scroll to the end of every list.
6. Report anything covered or cut
   off. Send a screenshot, your phone
   model and your Android version.

Testers have phones with different cutouts and screen sizes, which you probably don't own. See testing on phones you don't own. A Play pre-launch report can also catch some problems, see the pre-launch report and Android vitals.

Where TestSwap fits

TestSwap is a free app testing exchange for indie developers. You post web, iOS and Android apps with a link testers can open or install, like a TestFlight link or a Google Play testing link. You can add a test login that only signed-in testers see. Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1. You can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit. I can't promise how many testers you get or which phones they own. TestSwap is not affiliated with Google.

The checklist

  1. Did you read Google's edge-to-edge and behavior change pages for your target SDK?
  2. Is the top bar clear of the status bar and the cutout?
  3. Are bottom buttons and tabs clear of the navigation bar?
  4. Does the floating button stay out of the gesture area?
  5. Can you scroll the last item of every list into view?
  6. Is every text field visible when the keyboard is open?
  7. Are status bar icons readable in light and dark theme?
  8. Did you test gesture and 3-button navigation?
  9. Did you test portrait, landscape, and a cutout?
  10. Did you visit onboarding, sign-in and settings?
  11. Does your test task ask for screenshots, phone model and Android version?

Try it

Switch to 3-button navigation today and open your busiest screen. Fix what is hidden. Then post your app on TestSwap with the test task above, and review someone else's app first to see how it works. Tell me what's missing or broken (@dizid on X).