Patterns
Common screens: the structure that works, where to spend creativity, and what usually goes wrong.
Landing page
Structure:
- Hero: what it is and who it's for in one specific headline (under about 10 words), a sentence of support, one primary action and maybe one secondary, and the product itself (screenshot, demo, diagram) rather than an abstract image.
- Proof early: logos, a number, or a quote, close to the hero, small and quiet.
- How it works or what it does: three to five ideas, each with a real visual. Prefer showing the product doing the thing over icon-and-text cards.
- Depth for the convinced: details, integrations, comparisons, security.
- Pricing or next step, then FAQ.
- Closing call to action that restates the promise.
Where to be creative: the hero composition, the headline's typography, how the product is shown, one memorable section (an interactive demo, a big statistic, a drawn diagram), and the closing section.
Pitfalls: headlines that could describe any product; every section with the same layout; three identical feature cards; a hero image that shows nothing real; ten calls to action with different wording.
Dashboard
Structure:
- The few numbers that answer "how are things?" at the top: value large, label small, change since last period with direction and color.
- One or two primary charts showing trend over time.
- Lists or tables of the items that need attention, with actions.
- Filters and time range in one consistent place.
Where to be creative: the hero metric (it can be big), chart styling within the palette, annotations explaining anomalies, a well-written empty state for new accounts.
Pitfalls: twelve equally weighted stat cards; pie charts with many slices; charts without units or time labels; decorative gradients in charts; color meaning different things in different charts.
Forms and settings
Structure:
- One column, labels above, related fields grouped under short headings, a clear primary action at the end.
- Settings: grouped into sections with a title and a one-line description, each setting with a label, a description of its effect, and its control aligned consistently (often right-aligned toggles or a left label column on wide screens).
- Long forms: steps with progress, or sections with a sticky table of contents.
Where to be creative: almost nowhere inside the form. Put personality in the surrounding page, the illustration and the success state.
Pitfalls: placeholders as labels; two-column layouts that break the reading order; unclear which settings save automatically; errors only at the top of the page.
Onboarding
Structure: few steps (three to five), each with one goal, visible progress, the ability to skip what isn't essential, and a meaningful first success (a first project made, a first result shown) as early as possible.
Where to be creative: the welcome, illustrations, the first-success moment, sample content that's specific and delightful.
Pitfalls: tours that explain the interface instead of getting the person to do something; asking for information the product doesn't need yet.
Pricing
Structure: two to four plans side by side, the recommended plan emphasized (border, label, raised), the price large with its period clear, a short line on who each plan is for, the key differences listed (not every feature), one call to action per plan, a monthly/yearly toggle if relevant, then a detailed comparison table and FAQ.
Where to be creative: how the recommended plan is marked, the headline above the plans, the price typography.
Pitfalls: every plan visually equal; feature lists so long that nothing stands out; prices without currency or period.
Sign-in and sign-up
Structure: the product mark, one short heading, the fastest method first (social or passkey, or email link), the form, a link to the other flow (sign in ↔ sign up), and legal text small at the bottom. Centered, narrow, calm.
Where to be creative: the background or a side panel (a product image, a quote, a brand graphic) on wide screens.
Pitfalls: distracting animations; asking for a password twice; unclear errors.
Empty states
Structure: a short heading saying what will be here, a sentence on why it's empty or what to do, one primary action, and optionally an illustration or a preview of what it looks like with content.
Distinguish first use ("No projects yet"), no results ("No projects match 'tide'", with a way to clear filters) and cleared ("All caught up").
Where to be creative: this is one of the best places for personality: an illustration, a witty but helpful line, sample content.
Data tables
See Components. Add: a toolbar with search and filters above, bulk actions that appear on selection, row actions on hover or in a menu at the end, and column widths that fit their content.
Mobile app screens
Structure: a clear title, the main content in one column, the primary action reachable by the thumb (bottom of the screen), tab bar for 3–5 top-level destinations, and navigation back at the top left.
Where to be creative: headers, cards for primary objects, the transition moments (success, empty, first launch).
Pitfalls: desktop layouts squeezed down; targets under 44px; important actions at the top corners; text smaller than 16px for body.
Structure: a single column 560–640px wide, the logo, one message per email with one primary button, plain text that works if images don't load, and a quiet footer.
Pitfalls: multiple competing calls to action; text baked into images; tiny type.