Skip to content
BENIBIX Learn

Balsamiq, Framer and Dev Mode

Level 2 · Designing screens

Three tools for three steps. A rough plan in Balsamiq. A handoff to code in Figma Dev Mode. A live site, put online straight from Framer.

Course contentsLesson 6 of 12

After this lesson you can

  • Say why a rough wireframe helps
  • Explain what Dev Mode shows a developer
  • Say what Framer does that Figma does not

10 mincovers 3 glossary entries

Worth reading first: Auto Layout and Constraints

From a rough plan to a live site

A screen design goes through three moments: a rough plan, a finished look, and real working code. Different tools serve each one. Balsamiq is for the rough plan. Figma's Dev Mode, added in 2023, hands the finished look to developers. Framer skips the handoff and publishes a live website itself.

Balsamiq makes wireframes, the plain first plans of a screen. Its boxes and buttons look drawn by hand on purpose. That rough look tells everyone the screen is not finished. So people talk about where things go, not about the color of a button.

You can link Balsamiq screens, so a click on a button opens the next one. A team can click through five rough screens in a morning. Moving the email box costs a minute here. Moving it after the app is built costs a week.

Dev Mode is a view in Figma made for the people who write code. Click any part and it shows the exact size, color and spacing. It shows the names of shared parts and can show matching code. It also marks which screens are ready to build.

Framer is a design tool that turns a design into a real website. You lay out pages on a canvas and add motion. Then you press publish, and the site is live on the web. It also hosts the site. It is popular for landing pages and personal sites.

The three are not rivals so much as stages. A team might plan in Balsamiq, design in Figma, and hand off through Dev Mode. A person making a small site alone might skip all that and build it straight in Framer.

The common mistake is to start with the finished look. Polished screens make people argue about colors and fonts. Rough ones make them argue about whether the steps make sense, which is the question that matters first.

Plan where things go, then how they look, then how they work. Each stage has tools made for it.

Three tools, three moments

ToolMomentWhat you get
BalsamiqThe rough planClickable wireframes that look hand drawn
Figma Dev ModeThe handoff to codeExact sizes, colors and matching code
FramerThe live siteA published website, hosted for you

Worked example

A sign-up flow in one morning

Sam plans a sign-up flow in Balsamiq. By 11 o'clock, the team has clicked through 5 rough screens and moved the email box to the top.

The designer then builds the screens in Figma. The coder opens them in Dev Mode. She copies the gap of 24 pixels between fields straight into the code.

The words for this lesson3

Check yourself

Why do Balsamiq screens look drawn by hand?

Finished this lesson?

Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.