Ethan Cole
Posted 4 min ago · Remote
Looking for a creative UI/UX designer to build our app
Remote, four days a week, alongside two engineers who ship every Thursday. You would own the design system end to end.
$200/hr
HourlyCards 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.
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.
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.
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.
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.
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.
Pick one and make the visuals agree. If the card is the link, the hover state belongs to the card and any inner button has to stop the click reaching it. If only the button acts, do not lift or highlight the card on hover, because that lift is a promise. A card with two actions in its footer should not also be clickable as a whole.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
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.
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.
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.
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.
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.
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.
Pick one and make the visuals agree. If the card is the link, the hover state belongs to the card and any inner button has to stop the click reaching it. If only the button acts, do not lift or highlight the card on hover, because that lift is a promise. A card with two actions in its footer should not also be clickable as a whole.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Ethan Cole
Posted 4 min ago · Remote
Remote, four days a week, alongside two engineers who ship every Thursday. You would own the design system end to end.
$200/hr
HourlyNorthwind
Product design · 4 min ago
Remote, four days a week, alongside two engineers who ship every Thursday. You would own the design system end to end.
Ethan Cole
Replies in about 2 h
$200/hr
Contract · Remote
Ethan Cole · Northwind · 4 min ago
Rate
$200 per hour
One hour of a 32-hour week · Mon–Thu, Friday off
Ethan Cole
Posted 4 min ago · Remote
Remote, four days a week, alongside two engineers who ship every Thursday. You would own the design system end to end.
$200/hr
HourlyNorthwind
Product design · 4 min ago
Remote, four days a week, alongside two engineers who ship every Thursday. You would own the design system end to end.
Ethan Cole
Replies in about 2 h
$200/hr
Contract · Remote
Ethan Cole · Northwind · 4 min ago
Rate
$200 per hour
One hour of a 32-hour week · Mon–Thu, Friday off