By Bob Poláček, updated
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.
By Bob Poláček, updated
Preview
Inbox, Swipe actions, Select, from the Mail page of the Appetite UI Figma file. The theme switch shows the dark frames.
| Screen | What it shows |
|---|---|
| Inbox | Messages as three line rows with unread dots, grouped by day |
| Swipe actions | One row swiped to reveal Archive, Flag and Delete |
| Select | Rows 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.
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.
| Rule | On the email app |
|---|---|
| One thing leads | The 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 on | Archive, 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 out | Inbox 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.
| Component | Screens |
|---|---|
| List | Inbox, Swipe actions, Select |
| Divider | Inbox |
| Segmented Control | Inbox, Swipe actions |
| Floating Action Button | Inbox |
| Navigation | Inbox, Swipe actions |
| Checkbox | Select |
| Top Bars | Select |
| Toolbar | Select |
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.
| What it sets | iOS | Android | Variable |
|---|---|---|---|
| Tab bar height | 49 pt | 64 dp | platform/bar/bottom-height |
| Minimum touch target | 44 pt | 48 dp | platform/min-touch-target |
| Screen side padding | 16 pt | 16 dp | platform/screen-padding |
| Component | iOS | Material 3 | What differs |
|---|---|---|---|
| Navigation | iOS / Tab Bar, floating capsule 62 high, two to five tabs | M3 / Navigation bar, 412 × 64 Flexible by default or 412 × 80 Baseline, three to five items | Material is a full width bar with a separate 24 high Gesture Navigation component, iOS floats on glass |
| Top bar | iOS / Toolbar on a 44 high top bar | M3 / Top app bar, Small 64 high, Medium flexible 112, Large flexible 120 | Material 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.