Skip to content
VISUAL DESIGN / REAL CODE

From design to real components.

Design on the canvas. Build with Zaoly Kit. Hand off React components your team can use in other products.

ORIENTATION

Why Zaoly.
And when the others.

One table: job, pros, cons — with a clear view of where Zaoly wins for design → React building block.

Comparison table: Zaoly, Figma, Framer, Penpot, Sketch, and Webflow with job, pros, and cons
CriterionZaolyBuilding blockFigmaFramerPenpotSketchWebflow
JobWeb UI → reusable React componentUI design, collaboration, Inspect/Dev ModeDesign is the published websiteOpen-source design + SVG/CSS inspectMac-native UI design + librariesVisual site builder + CMS / commerce
Pros
  • Visual work lands as a React module + tokens in your codebase — less rebuilding.
  • Kit atoms, local Token Studio, and breakpoint compare are product core — not a plugin.
  • Community source and self-host: you keep control of stack and operations.
  • No site-hosting lock-in — the building block keeps living in your product.
  • Market leader for collaborative UI design and prototyping.
  • Dev Mode and ecosystem deliver specs, assets, and agent hooks.
  • Very fast from canvas to a polished, hosted site.
  • Strong motion and marketing aesthetics out of the box.
  • Truly open source and self-hostable — full data control.
  • Web-native inspect formats (SVG/CSS) without a proprietary file.
  • Fast, focused Mac app for experienced UI teams.
  • Solid libraries and established Mac workflows.
  • Strong CMS and commerce — content and shop without a separate backend.
  • Build visually and host or export directly.
Cons
  • Not Figma-scale multiplayer or plugin ecosystem — deliberate focus on the building block.
  • Doesn’t publish a marketing URL for you — integrating into your product stays the step.
  • No CMS/commerce — instead a clear path from design → component for enterprise web.
  • Outcome is often still a spec/snippet — the real product component gets rebuilt afterward.
  • Closed product; your code and hosting stay separate worlds.
  • Optimized for the Framer site — not React building blocks in your product code.
  • Hosting and platform lock-in are part of the deal.
  • Remains a design/inspect tool — not a React kit and token handoff into your product.
  • Ecosystem and enterprise workflows are narrower than Figma’s.
  • Mac-only and weaker live collaboration than browser-based tools.
  • Handoff leans on plugins/specs — not your React building block.
  • The site is the system — not your product React components.
  • Platform and hosting lock-in; enterprise code reuse isn’t the core.
Best whenWhen design and engineering need the same React building block — not just specs or a site.When you want to design and collaborate broadly first — and accept handoff as specs.When the website itself is the product — landing, portfolio, campaign.When open design and self-host are the priority — and code export is secondary.When your team is already deeply rooted in Sketch on the Mac.When CMS, commerce, and a hosted marketing site are the goal.

Zaoly isn’t trying to replace Figma as a design OS or Framer/Webflow as a site publisher — it owns the step where design becomes a React building block in your product.

WHY ZAOLY

Less rebuilding.
More reuse.

Zaoly turns visual decisions into structured building blocks with variants, design tokens, and code, so design and development can keep working from the same source.

DESIGN→COMPONENT→PRODUCT
EXPERIENCE ZAOLY

Don’t just read.
Try it.

Five public demos here — full interaction at /explore. App links go to /editor, /kit, and /tokens (sign-in).

Illustration · not the live editor

PAGESLAYERS / HOME
HOME / DESKTOP 1440100%
STUDIO FORMWORK   ABOUT   CONTACT
DESIGN WITH A SYSTEM

Design becomes the language of a product.

✓ Preflight checked
SELECTED WORK 01 / 03
CANVASDESKTOP · 1440 × 900 · 100%
INSPECT / HEADINGNew spaces
for ideas.
DESIGN
WidthAuto
Size64 px
Farbe Ink

Selection: Heading · HOME · Canvas

Illustration · lenses · pages · layers · canvas hotspots.

One workspace.
Three lenses.

Canvas, Masters, Preflight — illustration here; full demo on Explore.

INSIDE ZAOLY

The system.
At work.

Three real views with sample data — no mockup, no suite requirement.

Zaoly Token Studio app view showing color tokens from the local seed pack
Token StudioActual app view · sample data

Token paths connect values to components in the editor.

Zaoly Kit Playground showing a component list, TSX code, live preview, and token panel
Zaoly Kit PlaygroundActual app view · sample data

Kit atoms, TSX, and live preview sit side by side.

Zaoly editor showing the same page on desktop, tablet, and mobile artboards side by side
Multi-breakpointActual app view · sample data

Multi-breakpoint compare on the canvas.

PROJECTS

One building block.
As many projects
as you need.

Your projects have different goals. Well-made components can still live on in more than one context.

◇New spaces
for ideas.
A module for stories.Landing
Studio Form
◇Everything
in view.
Same structure. New context.Dashboard
Product
◇Ready to
move on.
Ready for the next product.App shell
Platform

Start your own project

DESIGN → DEV

Handoff
without guesswork.

Turn a visual building block into a React module with imports, token context, and guidance for integration into other React projects.

Visual component · Example master
One idea.
Many places.
Explore ↗

Marketing example · not a seed atom

React module
01import { Stack, Text, Button }02from '@zaoly/site-kit'0304export function FeatureCard() {05  return (06    <Stack>07      <Text>One idea. Many places.</Text>08      <Button>Explore</Button>09    </Stack>10  )11}
CONTACT

Let’s talk about
Zaoly.

Planning a team rollout, want to learn about hosting and AI features, or have questions about developer handoff? We’ll help you find the right next step.

Make more of
your next
design.

Design today what keeps working as a component tomorrow.

Get started
Zaoly — From design to reusable components