“Don’t make it ❤️ Hateble.”
— the very first thing you see on Hateble.dev
Last night I was ego-searching my own domain (don’t judge 😊) and a wild result popped up: Hateble.dev.
The promise? “The brutally honest AI website analyzer to make your product ready to market.”
Naturally, I clicked. Here’s what happened, who (I think) built it, and why I’m still cheering for it even though it’s currently throwing a nasty HTTP 500.
First impressions
- A gorgeous orange-to-black gradient hero.
- A big input box for your-probably-broken-site.com.
- A bright “🔥 Analyze my site for free” button.
- Under the button: “HTTP error! status: 500” — every single time. Ouch.
UI-wise it oozes the same heart-shaped logo and typography you’ll find on Lovable.dev, the well-funded “build apps by chatting with AI” platform. :contentReference[oaicite:1]{index=1}
That immediately set off a branding déjà-vu…
Who built Hateble.dev?
There’s no /about page, no footer credits, and WHOIS privacy is on.
But a few breadcrumbs point straight at Lovable’s orbit:
- The heart logo. Hateble’s word-mark uses the identical ♥ glyph Lovable uses for its brand.
- “Works with any vibecoding tool.” The bottom of the page lists bolt.new, Cursor, Lovable, and Replit — exactly the roster Lovable’s docs highlight when they talk about “vibe coding” tooling. :contentReference[oaicite:2]{index=2}
- Same color palette & type scale.
My best guess: Hateble is a tongue-in-cheek side project by someone inside the Lovable team (or at least by a designer/dev who hangs out in their Discord). Think of it as the sarcastic sibling: Lovable helps you ship, Hateble tells you why what you shipped kind of sucks.
What it says it does
- Runs an AI/LLM agent against your live site.
- Spits out a blunt UI/UX + performance audit (copy, layout, CLS, Lighthouse, etc.).
- Gives a fix-list “so your launch isn’t cringe”.
If it sounds like ChatGPT + Lighthouse + a roasted Dribbble critique mashed together, that’s probably the stack.
Why I still like the idea
- Negative feedback ≠ bad vibes. Early-stage founders need harsher truth, faster.
- Automated QA for vibe-coded apps. Lovable users spin up full apps in hours; an instant “roast” bot fits that workflow.
- Fun branding. Hateble is the perfect villain pairing for Lovable.
Lessons for indie builders
| Takeaway | Why it matters |
|---|---|
| Ship a landing page early | Even broken, the site captured attention (I’m literally blogging about it). |
| Brand extensions work | The “evil twin” trope is memorable and shareable. |
| Error messages are UX | A plain 500 in red text kills hype fast. Consider a witty fallback (“Our AI passed out from all the roasting — try again soon!”). |
What’s next?
- I dropped my email into their (working) wait-list form — fingers crossed.
- If/when the API comes back, I’ll run a full teardown on my own site and post the results.
- Meanwhile, you can DIY something similar with OpenAI’s JS SDK + Chrome-Lighthouse if you’re brave.
TL;DR
- Hateble.dev is a (currently broken) AI tool that promises to roast your site so you can fix it before launch.
- All signs point to it being a cheeky side-project from the Lovable.dev ecosystem.
- Even with a 500-error wall, the concept is 🔥 — and a reminder that honesty (and a bit of snark) is sometimes the fastest way to a better product.
Have you tried Hateble yet? Did you manage to get past the 500? Let me know in the comments — or roast this post, I can take it.
Happy shipping, and may your next deploy be more Lovable than Hateble. 🧡
Top comments (0)