Design Teams

Hand off working prototypes from design to development.

Design and development can review the local build together before staging exists. Designers click real flows, catch interaction gaps, and bring precise feedback back to the developer.

How it works

Three steps. One review window.

Start from the build in front of you, share a scoped link, and keep the session visible while reviewers click through.

01

Run the prototype

Start the local build that carries the design work. Set the review window before you share.

zsh

$ wiremaven --port 3000 --expires 30m

relay active

tunnel: relay.wm/p/design-handoff

expires: 30m · overlay: enabled

02

Review with design

Send the relay URL to the designer or design lead. They click the real UI in their browser.

03

Bring back specifics

Use the session events to connect feedback to the flow, route, or request that produced it.

Why wiremaven

Figma sets intent. The browser proves behavior.

Design handoff loses detail when teams stop at static frames. wiremaven gives designers and developers a shared working prototype while the build still lives on localhost.

Behavior

Review the real interaction.

Designers can check motion, empty states, responsive breaks, and copy inside the browser.

Handoff

Connect feedback to the build.

Developers see the session path, requests, and failures behind each design note.

Context

Keep Figma and code in the same loop.

Use Figma for intent, then use the local build to test what the user will touch.

Focus

Review before staging politics.

Share a working prototype without waiting for a deploy, preview environment, or release branch.

The shift

From static handoff to a working prototype review.

Before
  • Design feedback stays in Figma comments
  • Developers infer interaction details from frames
  • Responsive issues wait for staging
  • Designers cannot click the local implementation
  • Prototype gaps turn into meeting follow-up
After
  • Designers open the local build in their browser
  • Developers watch the reviewed flow in context
  • Interaction gaps surface during the handoff
  • Figma intent and code behavior stay connected
  • Feedback points to the exact working prototype
What you get

Design and development review the same thing.

Working

Local prototype links

Share the implementation that runs on your machine, not a static export.

Scoped

Expiry by review window

Keep access open for the handoff session, then let it close.

Visible

Viewer and request events

See who joined, what routes loaded, and where the prototype failed.

Low friction

No reviewer install

Designers open the URL. They do not need Node, a repo clone, or local setup.

Precise

Feedback with route context

Use the session trail to locate the flow behind each handoff note.

Safe

Outbound tunnel

The developer machine connects to wiremaven. Reviewers never connect to a local port.

Start here

Move the next handoff into the working prototype.

Share the local build with design, review the real interaction, and keep the session trail in view.

Read the docs
FAQ

Common questions

Is this meant to replace Figma?
No. Figma remains the place for design intent. wiremaven adds a working prototype review once development has a local build.
Does the designer need the project running on their machine?
No. The developer runs the local build and shares a wiremaven link. The designer opens the URL in a browser.
Can design teams use this before staging?
Yes. That is the point: review the working local prototype before staging setup slows the loop.
What should teams review with this?
Use it for interaction details, responsive states, empty states, copy checks, and flows that need real browser behavior.