Skip to content

Booking app confirmation

What a traveler sees after paying, drawn in Appetite UI, a Figma UI kit for iOS and Android apps built like a design system: a green check, Booking confirmed with a reference number, a trip summary card, three next-step rows, and View trip and Message Maren. Trips then holds the stay as an Upcoming card, In 3 weeks.

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

Confirmed, Trips, from the Booking page of the Appetite UI Figma file. The theme switch shows the dark frames.

Booking app, order tracking393 x 852 each, Light and Dark
Booking app Confirmed screen: a green check, Booking confirmed with a reference number, a trip summary card, three next-step rows and View trip and Message Maren buttonsBooking app Confirmed screen in dark mode: a green check, Booking confirmed with a reference number, a trip summary card, three next-step rows and View trip and Message Maren buttons
Confirmed
Booking app Trips screen: an Upcoming card for Lakeside cabin with an In 3 weeks label, and Later this year rows for Harbor loft with a Pay balance label and Coastal house with a Confirmed label, above a floating tab barBooking app Trips screen in dark mode: an Upcoming card for Lakeside cabin with an In 3 weeks label, and Later this year rows for Harbor loft with a Pay balance label and Coastal house with a Confirmed label, above a floating tab bar
Trips
Screens, screen, what it shows
ScreenWhat it shows
ConfirmedA confirmation, a reference and the next three steps
TripsAn upcoming trip as a large card and later trips as rows

Which components carry the order tracking pattern?

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

Order tracking, live componentsKit geometry, light and dark

Progress Steps, step 3 of 4

34

Button, Fill and Weak

How does this screen follow the order tracking pattern?

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

The pattern, rule, on this screen
RuleOn the booking app
Lead with the arrival timeBooking confirmed leads the screen in place of an arrival time: the reference sits right under it, the thing a traveler is asked for later.
Steps, not a percentageThree next-step rows say what happens now instead of a bar of progress, each one a sentence.
The person is one tap awayMessage Maren puts the host one tap away, beside View trip, before the traveler has to look for her.

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
ButtonConfirmed
Lucide iconsConfirmed
Top BarTrips
Section HeaderTrips
Vertical CardTrips
Horizontal CardTrips
NavigationTrips

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/min-touch-target4448
Counterparts, component, iOS, Material 3, what differs
ComponentiOSMaterial 3What differs
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.