AppReviewX Log in

Test gesture vs three-button navigation on Android

Check that bottom content, back gestures and insets work in both navigation modes.

In this guide

Android phones offer gesture navigation and the classic three-button bar. The two use different amounts of screen at the bottom and handle "back" differently. An app tested in one mode often breaks in the other: content hidden behind the bar, buttons that clash with the swipe-up area, a back swipe that closes the app instead of a dialog.

Switch modes

Per Google, on Pixel phones the path is Settings > System > Navigation mode; on other devices it is Settings > System > Gestures > Navigation mode. Names vary by manufacturer. Choose Gesture navigation or 3-button navigation. Run the checklist once in each mode. Restart the app after switching.

Checklist

  1. Bottom content is not covered. Last list item, bottom buttons, bottom tabs and floating buttons must sit clear of the system bar. Why: the bar height differs by mode. Check: scroll every list to the end and tap the last item.
  2. Edge-to-edge screens. If your app draws behind the system bars, content must still be padded correctly (insets). Check: look at the top and bottom of each screen, including splash, full-screen media and dialogs.
  3. Bottom actions near the gesture area. A button right at the bottom edge is hard to hit in gesture mode because swiping up starts there. Check: tap bottom buttons and bottom sheet handles repeatedly.
  4. Back gesture from the side edge. Swiping in from the left or right edge goes back. It can collide with side drawers, carousels and sliders. Check: use each swipeable control near the edge.
  5. Back goes where the user expects. Back should close the dialog, then the screen, and only then leave the app. Check: from a deep screen, press or swipe back step by step and note each stop.
  6. Back in special states. During a form with unsaved input, a payment step, a video or an open keyboard. Check: go back in each state; unsaved input should not vanish silently.
  7. Custom back handling. If you intercept back, make sure it works with both the gesture and the button, and that you can still leave. Check: try to exit from every screen.
  8. Keyboard and bar together. Input fields stay visible above keyboard and bar. Check: focus fields at the bottom of forms.
  9. Landscape. The bar sits at the side or bottom depending on mode and device. Check: rotate on key screens.
  10. Switching live. Change navigation mode while the app is open and return. Layout should adapt without clipping.

What to report

Navigation mode, device model, Android version, screen name, a screenshot of the problem, and for back bugs the exact steps taken. Our bug report template helps.

Limits

Gesture handling differs between manufacturers and Android versions, so one passing device is not proof for all. Test at least one device in each mode, and prefer different brands if you have testers.

Overview: Android app testing. Related: split-screen and multi-window and process death and state restore.

Start free on AppReviewX and get structured feedback from testers who use different navigation modes.