Skip to content

Finance app payment screen

Money to a person, drawn as a sheet in Appetite UI, a Figma UI kit for iOS and Android apps built like a design system: a Pay and Receive switch, Send money to Amara Diallo, an amount of $450.80, a QR code and Share and Save QR buttons.

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

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

Finance app, checkout393 x 852 each, Light and Dark
Finance app Pay sheet: Send money to Amara Diallo with a Pay and Receive switch, an amount of $450.80, a QR code and Share and Save QR buttonsFinance app Pay sheet in dark mode: Send money to Amara Diallo with a Pay and Receive switch, an amount of $450.80, a QR code and Share and Save QR buttons
Pay
Screens, screen, what it shows
ScreenWhat it shows
PayA sheet that sends money to a person or shows a QR code

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 finance app
Show the total before the buttonThere is no price breakdown to show, so the amount itself is the total, set large in the middle of the sheet where a checkout would put its sum.
The button says what it doesThe buttons say Share and Save QR, the two things the sheet does, rather than a generic Done.
Every choice is a rowPay is a sheet without a tab bar: it opens over the app and closes back to it, so the person and the amount are the only choices on it, switched by one Segmented Control.

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 BarPay
Segmented ControlPay
AvatarPay
ButtonPay

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.