Skip to content

Email app inbox

The screen an email app opens on, drawn in Appetite UI, a Figma UI kit for iOS and Android apps built like a design system: messages under Today and Earlier this week as three line List rows with a blue unread dot, one row swiped to Archive, Flag and Delete, and the same rows with checkboxes and a toolbar.

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

Inbox, Swipe actions, Select, from the Mail page of the Appetite UI Figma file. The theme switch shows the dark frames.

Email app, dashboard393 x 852 each, Light and Dark
Inbox
Swipe actions
Select
Screens, screen, what it shows
ScreenWhat it shows
InboxMessages as three line rows with unread dots, grouped by day
Swipe actionsOne row swiped to reveal Archive, Flag and Delete
SelectRows with checkboxes and a toolbar for the selection

Which components carry the dashboard pattern?

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

Dashboard, live componentsKit geometry, light and dark

Quick Action Button and Navigation

How does this screen follow the dashboard pattern?

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

The pattern, rule, on this screen
RuleOn the email app
One thing leadsThe list leads: every message is a three line List row, sender, subject and preview, with a blue dot while it is unread, under an All, Unread and Flagged switch and a count of the unread.
Actions sit next to what they act onArchive, Flag and Delete sit on the row they act on, revealed by a swipe, and Select puts a checkbox on every row and archive, mark read, move and delete in a toolbar at the bottom.
The tab bar is the way outInbox and Swipe actions carry the Navigation tab bar, Inbox with the compose button above it; Select trades the tab bar for the selection toolbar, with Select all and Done at the top.

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
ListInbox, Swipe actions, Select
DividerInbox
Segmented ControlInbox, Swipe actions
Floating Action ButtonInbox
NavigationInbox, Swipe actions
CheckboxSelect
Top BarsSelect
ToolbarSelect

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 values, what it sets, iOS, Android, variable
What it setsiOSAndroidVariable
Tab bar height49 pt64 dpplatform/bar/bottom-height
Minimum touch target44 pt48 dpplatform/min-touch-target
Screen side padding16 pt16 dpplatform/screen-padding
Counterparts, component, iOS, Material 3, what differs
ComponentiOSMaterial 3What differs
NavigationiOS / Tab Bar, floating capsule 62 high, two to five tabsM3 / Navigation bar, 412 × 64 Flexible by default or 412 × 80 Baseline, three to five itemsMaterial is a full width bar with a separate 24 high Gesture Navigation component, iOS floats on glass
Top bariOS / Toolbar on a 44 high top barM3 / Top app bar, Small 64 high, Medium flexible 112, Large flexible 120Material has five bar types: Small, Center-aligned, Medium flexible, Large flexible and Search

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 599 variables in 6 collections and exports its token values to SwiftUI, Jetpack Compose, Flutter and CSS. Solo covers one person and Team up to ten people. You pay once and keep lifetime updates.

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