Onboarding screen design examples

An onboarding step collects a few answers early so the product can tailor what a new user sees first. Our examples show the second of four steps: a progress indicator, selectable use-case cards, team-size chips and Back and Continue buttons, drawn for web and mobile in eight visual styles with light and dark versions. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.

DeviceAll Web Mobile

StyleAll Minimal Editorial Brutalist Luxury Playful Corporate Retro Monochrome

Theme

16 examples

Web · minimal

Web · editorial

Web · brutalist

Web · luxury

Web · playful

Web · corporate

Web · retro

Web · monochrome

Mobile · minimal

Mobile · editorial

Mobile · brutalist

Mobile · luxury

Mobile · playful

Mobile · corporate

Mobile · retro

Mobile · monochrome

See it in a flow

Sign up and onboarding

Onboarding step design tips

Tell people how many steps remain, such as 2 of 4, so the questions feel finite and worth finishing.
Ask only questions whose answers change what the product shows next; anything purely for marketing belongs later or nowhere.
Use large tappable cards or chips for choices instead of dropdowns, so options are visible and comparable at a glance.
Keep the Back button available and preserve earlier answers, so people can correct a choice without starting the flow again.

Questions

How many steps should an onboarding flow have?

Use as few steps as the personalisation genuinely needs, often three to five short screens. Each step should earn its place by changing the experience that follows. If a question does not alter defaults, templates or recommendations, cut it or ask it later in context.

Should onboarding steps be skippable?

Yes, in most products a skip option is kind and reduces drop-off from people who already know what they want. Apply sensible defaults when someone skips, and let them return to the questions from settings or a checklist later so nothing is lost.

Where should the progress indicator go on an onboarding step?

Place it at the top, above the question, so people see their position before they read. A short segmented bar or a step count works well. Avoid numbered labels for every step on mobile, as they crowd the header and add little.

Browse by pattern

App screens

Dashboard
Data table
Analytics charts
Login
Sign up
Forgot password
Two-factor code
Welcome
Onboarding step
Permissions request
Home
Feed
List view
Detail view
Kanban board
Calendar
File manager
Search results
Editor toolbar
AI chat assistant
Chat list
Chat thread
Video call
Image viewer
Map view
Video player
Create post
Class schedule
Booking details
Booking confirmed
Product detail
Cart
Checkout
Order confirmation
Settings
Profile
Notifications center
Team members
Roles permissions
Audit log
API keys
Integrations
Billing plans
Invoice
Paywall upgrade
Cancel subscription
Empty state
404 error
Loading skeleton
Success confirmation
AI workspace
AI settings
Version history
Approval queue
Doctor directory
Telehealth visit
Clinic home
Music player
Playlist
Portfolio home
Case study
Security dashboard
Project tracker
Course dashboard
Multi-step form wizard
Bank onboarding
Product scan
Split view (master-detail)
Canvas editor
Floor plan
Voice call
Toast / snackbar with undo
Confirm dialog (destructive)
Side drawer
Command palette
Date range picker
Form validation errors
Sign-in error
Card declined at checkout
Find a pro (home services)
Book a home-service visit
Job tracker
Account email
Order email
Shift scheduler
Leave calendar
Time-off request
Multi-location operations dashboard
Inventory stock
Savings goal
Onboarding carousel

UI components

Tabs
Cards
Pagination
Popover
Tooltip
Dropdown menu
Accordion
Radio buttons
Breadcrumbs
Toggle switch
Stepper
Sidebar navigation
Loading spinner

Website sections

Website templates

Building with an AI coding agent? Every screen here is also in the free Made Good Designs MCP server: ask Claude, Cursor or ChatGPT to search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.