1
0 Comments

Building a clipboard manager for UI components — first signup after 2 days

Building Pastable — a desktop app that saves UI components from Figma, Webflow, or any website into a local library. When you need one later, you paste it back as a real editable component — not a screenshot or flat HTML.

The problem: designers and no-code builders working across tools constantly rebuild the same navbars, cards, and sections from scratch. There's no clipboard that works across Figma, Webflow, and code.

Where I am (Day 3):

  • Working prototype (Tauri/Rust desktop app)
  • Bidirectional copy/paste for Figma, Webflow, and HTML
  • Landing page live at pastable.app
  • Posted on r/webflow — 1.6K views, 5 upvotes, 5 comments (genuine interest)
  • First email signup from someone I don't know
  • Active on Mastodon, building in public

What's working: Webflow developers seem to resonate most. One Reddit user asked detailed technical questions about how we handle Webflow's clipboard format. The pain of losing components across projects is real.

What I'm testing next:

  • Is the Figma audience equally interested, or is this mainly a Webflow problem?
  • Would anyone pay $10-20/month?
  • What's the right positioning — "component library" vs "clipboard manager" vs "design asset manager"?

Happy to share learnings. Anyone else building niche tools for designers?

on March 8, 2026