Should Designers Be Playing With Tools Like Loveable?
Have we reached the point where ignoring AI isn’t an option anymore? Loveable makes a strong case for that

Loveable promises to turn an idea into an app “in seconds.”
It brands itself as your “superhuman full stack engineer.” You give it a prompt, maybe import a doc or attach a file, and out comes a working thing—task manager, job board, blog, whatever.
It’s not the first tool like this, and it won’t be the last. But here’s the awkward question: should we, as designers, be playing with this stuff?
Some of Us Don’t Want To
A lot of designers still carry a healthy skepticism of AI tools.
Some of us have seen the buzzwords before—no-code, low-code, drag-and-drop—and lived through the fallout. Others just don’t like the idea of AI in design. It feels cold. It feels like cheating. It feels like giving up craft in exchange for speed.
And in fairness, some AI output is still junk. The defaults are boring. The interactions feel flat.
You can spot a "generated" UI a mile away. But even if you hate it, here’s the hard bit: AI doesn’t care. It’s still moving. Fast.
The fear isn’t about taste. It’s about survival.
We know what happens when new tools reshape the landscape. Flash, jQuery, Bootstrap, Webflow, Figma—they all changed the game. The people who kept experimenting stayed relevant. The ones who didn’t... didn’t.
Loveable and similar tools aren’t targeting designers directly, but give it time. You’ll start to see the blur. It’s already being used by founders and product folks to ship “good enough” MVPs.

And once those get traction, your role becomes cleaning up someone else’s vision instead of shaping it from the start.
So Should You Be Playing With It?
Honestly? Probably, yeah. You don’t need to love it. You don’t need to use it daily. But you should poke at it. See where it breaks. See what it spits out. See what it can’t do.
Understanding the tools—even the ones you don’t like—is part of staying sharp.
Loveable doesn’t “design” in the way we do. It assembles. It patterns. It mimics. And when the brief is simple, it often does a decent job.

But it doesn’t solve edge cases. It doesn’t think about real users. It doesn’t understand that accessibility isn’t just contrast ratios, or that UX isn’t just stacking cards in a layout. That’s still our job.
That said, there’s value in knowing what Loveable can do—because it helps you focus on what it can’t.
You can check out loveable by heading over to loveable.dev.