I designed an actual Framer Components Library layer with Bubble
Elisabeth Mauvaisair
Like this project
Posted Feb 3, 2026
Framer Collections is a personal library layer that lets you save, tag, organize, and re-insert your Framer components across any project, from one place.
A Framer Library,
Accessible Anywhere.
Self-initiatedApp landing page: mauvaisair.com/framercollections
Bubble prototype: framercollections.site/login
If you’re a designer, you surely understand how big of a thorn context switching can be, in any good workflow's paw.
And right now, if you need to frequently manage components in Framer, you can use the native Framer library feature across projects--you know, the wonderful dropdown list of obscure component names only available from the commands menu?).
But there is currently no way to manage, tag, or organize your own components at scale without some serious time and effort.
My solution:
A browser app + Framer plugin + Chrome extension that lets you save, tag, organize, and re-insert your Framer components across any project, from one place.
One setup. Works across all your workspaces.
From zero to a fully ideated, revenue-ready product — all real, and built in Bubble in just over 24 hours.
The Build
Framer Collections is a centralized component library for agencies + high-volume creators built to eliminate context switching, fix asset documentation and management, and unlock integrations (API-first, plugin, chromium extension).
A Framer Library, accessible anywhere… directly inside Framer or in your browser.
For
Agencies shipping multiple client sites with shared patterns + rotating teams
Volume creators producing many pages/variants weekly
The pain
Context switching between Framer projects, docs, chats, and asset folders breaks flow and creates rework.
Documentation doesn’t scale: teams can’t quickly answer “what’s approved / latest / reusable.”
No real integration layer: even if a library exists, it’s not where the work happens (the editor / browser / workflows).
Who pays + why
With such reduction in cognitive load for workflow-heavy design operations, paired with the automation capabilities,
Agencies pay because this directly improves margin (less searching, less rework, faster shipping).
Creators pay because it increases throughput (reuse + speed, reduced cognitive load).
Pricing, Scaling, and GTM Strategy
Pricing
Free: personal library + limited assets + extensions access
Creator Pro: higher limits + advanced search + API access
Agency Team: shared libraries, roles/permissions, auditability, API access, client handoff
Enterprise: SSO/OAuth, compliance, custom integrations
Expansion levers: seats, libraries (per client/brand), storage/asset volume, API usage, premium integration features.
GTM Strategy
Free plugin and extension access → the app is discoverable, provides value first, and inevitably becomes indispensable, since it's a real market gap.
MVP focus › what’s working now
I shipped the adoption foundation agencies require before they’ll trust a library:
User accounts + login (Email/Password)
(in testing)Saved Library
(in testing)API access
(done)scoped permissions
token generation
secure component link transport
This makes the product “integration-ready” instead of a dead-end folder of components.
Why Bubble?
Bubble was ideal for building a real, testable prototype fast while still covering the “serious product” bits:
authentication flows
permissioning/scopes + tokens
library data model + future-proofing for plugins/extensions
Roadmap › what comes next
Designed around removing context switching + making large libraries usable:
Library UX + retrieval logic
Visual previews
V1Collections
V1Tags
V3Integrations (the wedge for adoption)
Framer plugin
V2: import/copy, drag & drop, collections access, save/paste from editor, searchChrome extension
V3: paste components into private collections, from any siteLibrary transfers
AI/automation lane
MCP Server + Auth (V4)
Landing page: mauvaisair.com/framercollections
Bubble prototype: framercollections.site/login