Skip to content

Food delivery app checkout

The order, ready to pay, in Appetite UI, a Figma UI kit for iOS and Android apps built like a design system: rows for the address Prinsengracht 512, As soon as possible 19:20 to 19:35, Visa ending 4242 and Add a tip, a breakdown that totals $34.39, and Place order.

On this page
  1. Preview
  2. Live components
  3. The pattern
  4. Built from
  5. iOS and Material
  6. Related
  7. Get the file

Preview

Checkout, from the Foodie page of the Appetite UI Figma file. The theme switch shows the dark frames.

Food delivery app, checkout393 x 852 each, Light and Dark
Foodie app Checkout screen: rows for the address Prinsengracht 512, Amsterdam, As soon as possible 19:20 to 19:35, Visa ending 4242 and Add a tip, a price breakdown that totals $34.39, and a Place order barFoodie app Checkout screen in dark mode: rows for the address Prinsengracht 512, Amsterdam, As soon as possible 19:20 to 19:35, Visa ending 4242 and Add a tip, a price breakdown that totals $34.39, and a Place order bar
Checkout
Screens, screen, what it shows
ScreenWhat it shows
CheckoutAddress, time, payment, tip and the total

Which components carry the checkout pattern?

The kit's components, drawn live from the same tokens as the frames. Tap them: they behave as the Figma prototype does.

Checkout, live componentsKit geometry, light and dark

List, Price Row

Subtotal$32.90Service fee$1.49Total$34.39

Stepper

2

Button, Fill, large

How does this screen follow the checkout pattern?

The rules every checkout screen in the kit follows, and what this one does with each.

The pattern, rule, on this screen
RuleOn the food delivery app
Show the total before the buttonThe Price Rows end on $34.39 right above Place order, the same total the cart showed, so nothing changes between the two screens.
The button says what it doesPlace order names the act; it is the only button on the screen.
Every choice is a rowAddress, time, card and tip are four List rows, one choice each, so checkout stays one screen.

What is it built from?

Every control with a component is an instance of it, so one token change moves these screens with the rest of the file.

Built from, component, screens
ComponentScreens
Top BarCheckout
ListCheckout
Price RowCheckout
ButtonCheckout

What changes between iOS and Material?

The frames are drawn in the ios-md Platform mode. Switch a frame to android and these variables take the Material values; the components below are where the two systems draw the same need differently.

Platform variables, variable, iOS, Android
VariableiOS (ios-md)Android
platform/sheet/corner1228
platform/list-row/min-height4456
platform/min-touch-target4448
Counterparts, component, iOS, Material 3, what differs
ComponentiOSMaterial 3What differs
SheetiOS / Sheet - Full ScreenM3 / Bottom sheet 412 wide and Side Sheet 320 wideMaterial adds a side sheet for large screens
ListiOS / List with a 44 minimum rowM3 / List Item, 56, 72 or 88 high by LinesMaterial sets the row height by lines of text, iOS sets only a minimum

Start from these screens.

Every frame on this page is part of the Appetite UI file, drawn from its components and bound to its variables, so one brand edit moves every screen in light and dark.

The file holds 589 variables in 6 collections and exports its token values to SwiftUI, Jetpack Compose, Flutter and CSS. Solo covers one designer and Team up to ten people. You pay once and keep lifetime updates. Price goes up Nov 1

The read-only Figma preview opens the whole file, every screen and every variable, before you buy.