Should I vibe code
Design-forward website builder with CMS, animations, and hosting
A visual builder is an editor plus a renderer plus a hosting story. That is three products.
?
Their verdict, the Basic price and the build-time estimate come from their entry, MIT-licensed. Checked 2026-08-03.
?
Our verdict, the regret score and everything below it. Editorial and unsponsored — nobody can pay to be moved.
The honest answer
why the verdict is what it is
Any one layer is approachable. All three together, keeping animations smooth and output fast, is why this costs what it costs.
What actually breaks
not "if". the specific failures.
- The animation runtime, which is the reason to choose this category and is a performance budget rather than a feature
- Scroll-linked effects, which jank on any device slower than the one they were authored on
- Motion that ignores reduced-motion preferences, making a site unusable for people who get sick from it
- Page weight, since a design-forward site accumulates fonts, images and a motion library until it loads in six seconds on mobile
- Interaction state — hover on a touchscreen, focus for keyboards — which visual editors rarely surface
The site is beautiful on the machine it was built on. The launch tweet goes out and most of the traffic is mobile, on connections you did not test, where the hero animation runs on the main thread and blocks the first paint. Analytics shows a large majority leaving before anything rendered. The site is not broken and never errors — it is simply slower than the patience of the people you spent a month attracting.
Is that you?
the verdict is a default, not a law
- Motion is decorative, respects reduced-motion, and the page is usable without it
- You set a performance budget first and checked it on a mid-range phone
- Output is static and hosted on a CDN
- Content depends on animation to become visible
- Reduced-motion preferences are ignored
- There is no performance budget and no mobile testing on real hardware
- The animation library is larger than the content it animates
If you build it anyway
the checklist, then the prompt that enforces it
- Set a performance budget before designing — total bytes, time to first paint on a mid-range phone — and treat it as a constraint rather than a report.
- Honour prefers-reduced-motion everywhere, and make sure the page is fully usable and complete with all motion disabled.
- Animate only transform and opacity. Anything that triggers layout will jank on the devices you did not test on.
- Never gate content on animation. Text must be present and readable before any script runs.
- Test on a real mid-range phone on a throttled connection, not on a desktop with fast internet.
- Handle hover, focus and touch states explicitly, since a visual editor makes hover the default and touchscreens do not have one.
Before you build a design-forward website with motion, apply these and push back if I ask you to break them. 1. Ask me for a performance budget before any design work — total page weight and time to first contentful paint on a mid-range phone over a throttled connection. Treat those as constraints that reject designs, not as metrics reported afterwards. 2. Honour prefers-reduced-motion throughout, and verify the site is fully usable and visually complete with all motion disabled. Tell me some people are made ill by scroll-linked animation. 3. Animate only transform and opacity. Refuse to animate properties that trigger layout, and explain that these are what cause jank on devices I do not own. 4. Never make content depend on animation to appear. All text must be present and readable before JavaScript runs. 5. Handle hover, focus and active states explicitly for keyboard and touch. A visual editor makes hover the default and touchscreens have no hover. 6. Budget fonts deliberately: subset them, limit weights, and use font-display so text is never invisible while loading. 7. Publish as static files to a CDN with atomic deploys. 8. Before launch, test on a real mid-range phone on a throttled connection and report the numbers to me. 9. Out of scope unless I ask: CMS, ecommerce, membership, complex page transitions.
That one keeps you out of trouble. For the prompt that actually builds it, canivibecodeit.com has one.
their build prompt ↗Or don’t build it
the boring option, and the way back out
$10 a month buys a motion runtime that has been optimised across many devices and hosting on a real CDN. Building a site with hand-written CSS animation is entirely reasonable; building a general motion editor is a much larger project than the sites it would produce.
$10/mo is cheaper than your weekend.
Publish static HTML, CSS and assets that stand alone without the editor, and keep content separate from presentation. Motion is the most fashion-driven part of a site and the first thing you will want to remove in three years — keep it separable from the content it decorates.
Open-source web builder framework useful for a DIY site editor.
Questions
How is this different from the Webflow entry?
Webflow's entry is about document structure — semantics, heading order, whether the markup means anything. This one is about motion and performance: the animation runtime that makes the category appealing is also the thing that decides whether the site loads on the phones most of your visitors are using.
Is reduced-motion really a common preference?
Common enough to matter, and the consequence for those users is not aesthetic — vestibular disorders make parallax and large scroll-linked movement genuinely nauseating. It is also a single media query to respect. The failure is almost never a decision; it is that nobody tested with the setting enabled.
Every week, someone ships something they shouldn’t have.
New verdicts, the worst thing that landed in the trap, and the occasional incident report. No other email, ever.
last reviewed 2026-08-03 · verdict is editorial and unsponsored · shared entry data from canivibecodeit under MIT · not legal advice