One small problem with using code components in Framer: they can be really useful… until you need...One small problem with using code components in Framer: they can be really useful… until you need...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
One small problem with using code components in Framer:
they can be really useful… until you need to customize them asp er your wants and needs.
Then suddenly you’re opening code just to change a color, size or tiny styling detail, what if you do not know how to code😭
That’s something i wanted to avoid with this Custom Checkbox Framer Component .
All the useful controls are already in the Framer edit panel.
Change the colors, type, checkbox size, spacing, radius, border, background, shadows + more.
No need to code. No need of prompt. No rebuilding the checkbox from scratch.
Just drop it in and play around with the controls:)
Asif's avatar
This is exactly the gap that makes or breaks a code component for non-coders: the value is not the code, it is how many of the right props you surface as Framer property controls. Exposing color, radius, spacing and shadow in the edit panel is the difference between a component...
Shruti's avatar
agree with you, that's what the goal and motive is.
Rohan's avatar
Love this approach—exposing spacing, radius, and state controls makes the component feel genuinely usable for non-coders.
Shruti's avatar
yes, adding small changes as per the needs and requirements of creator including in edit panel, give alot of freedom with designs and in building stuff in framer.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started