Cards

Cards are bounded surfaces that each carry one item, a photo or an avatar, a title, a short row of stats and usually a single action, so a page of them can be scanned as a set of things rather than read top to bottom. The border and the shadow do real work: they say where one item ends and the next begins, which is what lets a grid hold entries that aren't the same shape.

The eight blocks in this family are a good argument against calling these product cards. One is a job post with an hourly rate, one is an identity record with a scannable code, one is a boarding pass with a countdown on the route. Same shell, unrelated content. The thing that trips people up is hover: lifting the whole card promises that the whole card is clickable, so either make it clickable or keep the lift on the button. A card that animates and then does nothing when you click the photo is worse than a flat one.

17 blocks

Job post

Freelance boards, hiring feeds: a listing with a rate and a Contact menu

Job post reply

Hiring feeds where the answer happens in the card

Job post rates

Contracts where the rate and the weeks it buys decide the reply

Vacation

Stay bookings: a full-bleed hero photo with the price that explains itself

Vacation, promoted

Featured stays: the same photo card, a Details button that turns it over

Profile stats

Insurance and account profiles: an identity card with five fields and a QR code

Profile wallet card

Insurance and membership cards you show at a counter

Profile coverage

Policies and subscriptions where time left is the point

Apartment listing

Rental catalogues: a tall photo, the rent beside the title, no footer to spare

Apartment gallery

Rentals where the rooms sell the flat: the photo is a gallery you scrub

Apartment for sale

Real-estate listings: a price-led card with a byline and two actions

Apartment estimate

Real-estate listings that show what owning costs each month

Recipe

Cooking and food apps: a dish card with time, servings and level

Recipe servings

Cooking apps where the recipe adapts: servings scale every quantity

Flight info

Boarding passes, travel apps: a route with boarding details and check-in

Boarding pass

Check-in flows: pick a seat and the card prints a boarding pass

Flight live

Flight tracking: the countdown is the card

01

Using Cards

Reach for it when

  • A grid of listings people compare before picking one to open
  • Entries carrying a photo and a few unlike stats: price, rating, distance
  • A record that has to stand alone on a phone: a pass, a profile, a ticket
  • When the action belongs to the item rather than the page: Contact, Reserve, View details

Reach for something else when

  • Rows of identical fields people want to sort and compare: use a table
  • The full detail of one record: give it a page, not a card with a scrollbar inside it
  • Section navigation: a list with leading icons carries it more quietly than a grid of boxes
02

Where it shows up

01

Rental listings

A search result needs a photo big enough to judge, the price where the eye lands first, and beds, baths and floor area in one row so two listings can be compared without opening either.

02

Job and gig boards

A post carries the poster's avatar, the skills as tags, the rate beside its unit, and a contact button that belongs to that post rather than to the page around it.

03

Boarding passes

Travel apps show a route, a countdown to boarding and the gate and seat details as one object a traveller holds on screen. The card boundary matters here: it is the document.

04

Account profile summaries

An identity or policy card gathers a photo, a status badge, an expiry date, a scannable code and a grid of fields that would read as a dull form anywhere else.

03

Questions

When should I use a card instead of a table row?

Use a card when the item has a picture and several unlike fields (a photo, a price, a rating, a tag row) and people judge one item at a time. Use a table when every item has the same handful of values and the reader's job is to sort, compare and scan a column rather than look at any single record.

Should the whole card be clickable, or only the button?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.