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
Back to feedPost
Are no-code sites actually better than custom coded ones?
Genuinely curious what people think about this.
No-code tools like Webflow and Framer have made it possible to launch something beautiful in days. The speed is real, the results can be stunning, and for a lot of projects that's honestly enough.
But then there's custom code. Slower to build, harder to hand off, but you own every layer of it.
Both have won projects. Both have lost projects to each other.
In my opinion they serve completely different needs and the real mistake is using one when the other was the right call.
What do you think? Is there a clear winner or does it always depend?
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
Challenges
View all
Related posts
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:)
Love this approach—exposing spacing, radius, and state controls makes the component feel genuinely usable for non-coders.
Title: UtilForge — Client-Side Developer Tool Matrix
Summary: A suite of 20+ developer utilities that run entirely in
the browser. No uploads, no server, no data leaving your machine.
What I did: Built the full stack — Next.js frontend, Web Workers
for heavy processing (formatting tens of thousands of lines of JSON,
PDF manipulation, hashing) so the UI never blocks. Every tool works
offline after first load.
Tags: Next.js · React · TypeScript · Web Workers
Link: utilforge.dev
The no-upload promise is the strongest part. I'd make the offline state visible in the UI, so someone working with sensitive JSON or PDFs can see that the file stays on their machine before they drop it in.
Experimenting with my components to create something special for you :)
A: Hero section created using Dither Engine
B: Pricing section created using Halftone Engine
Which one would you pick? 👀
👇 A or B ?
0 votes
Ends in 1d