How I solved a Framer Marketplace problem
Elisabeth Mauvaisair
Like this project
Posted Dec 27, 2025
Not being able to test a component before purchase represents a risk for buyers. So why not let people interact with the properties on the feature page?
Likes
5
Views
46
Timeline
Dec 24, 2025 - Dec 26, 2025
I made a landing page for my new Framer component!
The feature of this page was supposed to be the Scatter/Stack Scroll cards, but I ended up exploring solutions to a significant problem in the Framer Marketplace, especially when it comes to paid components.
I would copy a component and struggle to set it up to match how it looked on its feature page, resulting in a significant waste of time.
By simply allowing users to see what’s under the hood before committing to anything, and letting them drag the image or copy the text values, this resolved any potential setup friction.
While this is just a text-value copy and paste for now, I am currently developing a Framer component that lets users change and experiment with the actual properties of any given component in real time, from the live site. Kind of a mock Framer UI.
Solution & Tradeoffs
Not being able to test a component before purchase represents a risk for buyers. So why not let people interact with the properties on the feature page?
When creating a highly-customizable component, setting the default properties to match the values in the feature page wouldn’t do much to showcase or explain the component’s features and limitations to the end user. This is a case where even the best practices aren’t exactly solving the problem.
While acknowledging that this solution comes with its own tradeoff, this time for creators - publicly exposing the properties represents the risk of people stealing concepts without you getting paid in the process - I thought I should at least be able to make that decision for myself.