Skip to content

Calendar app month, week and day views

One week of events drawn four ways in Appetite UI, a Figma UI kit for iOS and Android apps built like a design system: November as a month grid with the 12th selected, Week 46 as seven day columns on an hour grid, Thursday with a red now line at 09:41, and the next seven days as an agenda.

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

Month, Week, Day, Agenda, from the Calendar page of the Appetite UI Figma file. The theme switch shows the dark frames.

Calendar app, dashboard393 x 852 each, Light and Dark
Month
Week
Day
Agenda
Screens, screen, what it shows
ScreenWhat it shows
MonthA month grid with event dots and the selected day's events under it
WeekSeven day columns on an hour grid with a now line
DayOne day on the same hour grid
AgendaThe next seven days as a list grouped by day

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 calendar app
One thing leadsThe selected day leads every view: Month lists the events of Thursday 12 November under the grid, Week and Day lay them on the Time Grid around the red Now Indicator at 09:41, and Agenda opens on Today.
Actions sit next to what they act onDay, Week and Month sit in one Segmented Control on Month, Week and Day, and a Floating Action Button to add an event stands above the tab bar on all four views.
The tab bar is the way outAll four views carry the Navigation tab bar, with a Scroll Edge under it, so events fade out before they reach the bar.

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
Date PickerMonth
Calendar EventMonth, Week, Day, Agenda
Segmented ControlMonth, Week, Day
Floating Action ButtonMonth
NavigationMonth, Agenda
Week StripWeek, Day
Time GridWeek, Day
Now IndicatorWeek, Day
DividerAgenda

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.