Skip to content

  3 min read

iOS vs Android values: what a screen changes when it moves platforms

Moving a screen from iPhone to Android changes its touch target, safe areas, bar heights, row height, switch and corners. Each value side by side, in pt and dp.

On this page
  1. Values that differ
  2. Values that stay
  3. Handoff

When a screen moves from iPhone to Android, its touch target, its safe areas, its bar heights, its list row height, its switch track and three of its corners change. Its card corner and its side padding stay as they are. Appetite UI keeps each of these numbers in one Figma variable with a value per platform mode, so the touch target variable reads 48 dp in a frame set to the android mode and 44 pt in a frame set to ios-md.

Appetite UI is a Figma UI kit for iOS and Android apps, built like a design system. The values below are its Platform collection, the same numbers Platform Bridge prints, and each row links to the glossary term that explains it.

Which values differ between iOS and Android?

iOS and Android values, what it sets, iOS, Android, variable, term
What it setsiOSAndroidVariableTerm
Minimum touch target44 pt48 dpplatform/min-touch-targetTouch target
Top safe area59 pt52 dpgrid/safe-area/topSafe area
Bottom safe area34 pt24 dpgrid/safe-area/bottomSafe area
Top bar height44 pt64 dpplatform/bar/top-heightTop app bar
Tab bar height49 pt64 dpplatform/bar/bottom-heightTab bar
List row, minimum height44 pt56 dpplatform/list-row/min-heightList row
Switch track width64 pt52 dpplatform/switch/track-widthToggle and switch
Switch track height28 pt32 dpplatform/switch/track-heightToggle and switch
Control corner8 ptFully roundplatform/control/cornerCorner radius
Sheet corner12 pt28 dpplatform/sheet/cornerBottom sheet
Dialog corner12 pt28 dpplatform/dialog/cornerCorner radius

iOS is the ios-md mode, Android the android mode of the Platform collection in the Appetite UI Figma file. Fully round is how the file stores a full radius, 9999.

The Android column is larger in every height on the list. A top bar grows from 44 to 64 and a list row from 44 to 56, so a screen that fits on iPhone loses rows on Android unless it scrolls. The switch turns from a wide, low track into a narrower, taller one, and buttons and fields go from an 8 point corner to a full pill.

Which values stay the same on both platforms?

The card corner is 12 and the side padding of a screen is 16 in every mode, so a card list keeps its edges when the screen changes platform. The ios-lg mode, for the larger iPhones, differs from ios-md in one value only: the top safe area is 62 pt instead of 59. The two iPhone Duo modes set the tab bar height to 0 and add a trailing safe area of 96, which the iPhone Duo article explains.

How do you hand these values to a developer?

Name the variable, not the number. A spec that says the row is platform/list-row/min-height holds on both platforms, while a spec that says 44 is right on one of them. In the file the variable returns the iOS column in a frame set to ios-md and the Android column in a frame set to android, so the spec and the frame name the same thing. For the touch target the two numbers come from Apple and Google, and the touch target article quotes both with the controls of the file measured against them.

Written by

Bob Poláček

Designer of Appetite UI. Builds the Figma file, the token architecture and the code output, and answers the support inbox.

Keep reading

  • Guide · Oct 8, 2026 · 15 min read

    Touch target size on iOS and Android: 44 pt, 48 dp and the WCAG minimum

    Touch target size is 44 × 44 pt on iOS, 48 × 48 dp on Android and 24 × 24 CSS px in WCAG 2.2, checked against one Figma file

  • Guide · Sep 24, 2026 · 11 min read

    How to design one app for iOS and Android in Figma

    Keep one token set, share the components that behave alike, draw bars and sheets once per platform, and switch touch targets with a Figma variable mode.

  • Platforms · Sep 24, 2026 · 14 min read

    iOS vs Material 3: what changes per component

    iOS and Material 3 differ most in navigation, the primary action, sheets and snackbars. Per component: SwiftUI and Compose names, touch targets and sizes.

Your next rebrand is one edit.