All posts
Process
4 min read
Why we design straight in Framer
Static mockups hide the hard parts of a website. Designing in the browser shows them on day one, which is why most of our client work skips the mockup stage.
What a mockup can’t show
A mockup is a picture of one screen at one width. Real visitors bring long headlines, missing images, slow connections and phones of every size. Most surprises in a web project come from that gap.
When we design directly in Framer, every layout already reflows. We see what happens to a card grid at 390 pixels while we are still choosing the type scale, not two weeks later in a review round.
Reviews on a real link
Clients review a live link instead of a PDF. They open it on their own phone, in the browser they actually use. Feedback gets more specific: “this button is hard to reach with my thumb” helps more than “can we make it pop”.
It also means there is no handoff. The design you approve is the site that ships, so nothing gets lost between a design file and a build.
When we still sketch first
For complex flows like multi-step forms or pricing logic we still start on paper. A few boxes and arrows settle the structure faster than any tool. Once the structure holds, we move to Framer and stay there.
Working on a site of your own?
Tell us what you’re building. We reply within one working day.