The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
If your developer keeps asking questions about your Figma file.
that's usually a good sign.
Questions like:
"What happens when this button is hovered?"
"How should this section behave on mobile?"
"Is this card a reusable component?"
"What should users see while data is loading?"
These aren't delays.
They're the questions that prevent expensive revisions later.
The best frontend projects don't start with code.
They start with clear communication.
That's why I always review a design before development begins.
It helps uncover missing states, improve consistency, and make the handoff between design and development much smoother.
A few minutes spent asking the right questions can save hours of rework.
If you're preparing a Figma design for development, I'd be happy to review it before the first line of code is written.
#Figma #FrontendDevelopment #React #WebDevelopment #UIUX #Startup #LandingPage #DesignReview #Contra
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
13:40: a finished Figma frame. 15:48: this, live on Vercel
Claude wrote every line of the code. I spent those two hours on the part clients actually pay for: looking at each version and saying what's off
17 commits, each one deployed. My notes went in as screenshots with red circles:
→ make the button edges look like ticket cutouts
→ replay the story chips every time you scroll past them
→ spacing 156, then 92, then back to 156
What made it fast was one Figma frame called "Ready for Dev". Every size, color and gap came from there, so nobody had to guess what the mockup meant
For a founder this means a real link on day one, and a fix you ask for at lunch is live by the afternoon
I designed this eight-page website collection in Figma for lawyers and law firms. This preview shows two example pages from the collection.
The design follows a story: introduce the firm, explain its services, and give visitors enough context to feel comfortable starting a conversation.
Before asking someone to get in touch, I wanted to help them understand who they would be working with and whether the firm could help with their situation.
The homepage begins that introduction. It moves through the firm’s background, services, and supporting information before reaching the contact section. The services page builds on that story, giving each practice area space for a fuller explanation.
Alternating images and text create pauses and changes in rhythm, inviting visitors to keep reading. The deep green palette, architectural photography, and angular shapes support the formal character of the design.
The contact section follows the explanation. My aim was to make that connection feel like a natural next step once visitors understand the firm and what it offers.
Need a website design for your law firm? Message me to discuss your services and the pages you need.
We built a freight forwarder that doesn't exist. Then we made its website actually work.
Halyard is a concept project — no client, no brief. We wanted to see what happens when a corporate site stops describing its product and just runs it.
So on the site you can:
→ Hover a live route map — 16 real ports, containers moving along their trade lanes, each port showing its local time and weekly sailings.
→ Track a container — type a number and it's checked against the real ISO 6346 check digit. Mistype one and it suggests the correction. You get the vessel, voyage, arrival date and every milestone from booking to delivery.
→ Price a lane — Shanghai to Rotterdam, 40ft reefer, pick a weight. Out comes transit time, sea distance, an indicative rate range and that container's CO₂e.
Five pages, built in Framer. The route map, tracker, estimator, counters and clocks are custom React code components. Open roles on the Careers page come from the CMS.
The part we keep coming back to: most corporate sites make you book a call to see the product. This one hands it to you on the homepage.
Try it → halyard.site
Case study → Find more
