2
2 Comments

Everyone is Using AI for Vibe Coding, but What You Really Need is Vibe UX

As someone with a background in both Software Development (but with poor coding skills) and UX Research (but with poor UI skills), AI has been a game-changer.

Much like everyone and their mother, I can launch a front-end application in a matter of minutes, and delegate all the "hard" work to the latest AI model so that I never have to touch a line of code, without having to design a single interface, page, or button.

But when it comes to creating your own product, is this really the "hard" work?

As a UX professional who has for years exclusively dealt with the research part, a good 90% of my job consisted in (politely) telling other people that their ideas were sht and the other 10% trying to prove why their ideas were sht. You can create the most beautiful, efficient, well-coded app in the world, but if the initial idea is sh*t, or if you are trying to solve the wrong problem, or if you are building with the wrong audience in mind - nobody is going to use it, and all your "hard" work will be for nothing.

There are dozens, maybe hundreds, of "vibe coding" tools targeted at wannabe entrepreneurs out there that market themselves as "turn your idea into a working prototype in 10 seconds"... the issue? Very few people have good ideas and even fewer decide to test them BEFORE they start creating anything.

My absolute favourite task as a UX researcher was being asked to do research for things that did not exist yet. Something that does not have a product nor a prototype, at best a series of post-its on a wallboard. Now THAT's how you design a succesful product.
Step 1: Pick a problem OR a target audience.
Step 2: Decide which problem you want to solve for which target audience.
Step 3: Research research research.
Prototyping doesn't come after AT LEAST step 4.

And if you don't have access to your target audience, research won't be as effective. But there's something that we UX people and service designer sometimes do: we sit at a table, brainstorm, and co-create. We talk to experts who KNOW the audience. We exchange and challenge and improve our own ideas so that we don't just create something random.

So now that I am "indie hacking" on my own, and that AI does all my coding, all my front-end, all my UI. What am I to do?

I can share all my amazing ideas with someone (allegedly) smarter than me, who (allegedly) knows my target audience better than me, and ask it to tell me why MY ideas are sh*t.

I can ask AI to actually provide me with my customer segments, personas, business canvases, problem statements, and product requirements. It can do that, and then I can just feed all of those back to it to actually build something useful.

I cannot think of a good term for this delegation of the service design process. But it's what comes before "vibe coding" and what will make you stand out from 99.99% of the other amazingly-undervalidated-idea-turned-shitty-web-apps out there.

on January 25, 2026
  1. 1

    This resonates. "Vibe coding" gets all the hype, but the real leverage is in what you're describing — using AI as a sparring partner before you write a single line.

    I've noticed the same gap building a tech news aggregator. The temptation is to jump straight into features, but AI is actually more valuable when I use it to challenge my assumptions: "Who exactly needs this? What problem does this actually solve? What would make them stop using it?"

    The step order you laid out (problem → audience → research → THEN prototype) is exactly where most people skip. They go idea → prototype → "why isn't anyone using this?"

    Curious: when you use AI to critique your own ideas, do you find it more useful to prompt for specific failure modes ("how could this fail?") or general critique ("what's wrong with this?")?

    1. 2

      I often ask it to do "worst case scenarios" and propose its own risk mitigation strategy. It also helps to give the same prompt or design challenge but ask it to impersonate different people - e.g. a UX expert vs a marketing expert.

Trending on Indie Hackers
Write COLD DM like this and get clients easily User Avatar 34 comments I built a tool to search all my messages (Slack, LinkedIn, Gmail, etc.) in one place because I was losing my mind. User Avatar 26 comments Learning Rails at 48: Three Weeks from Product Owner to Solo Founder User Avatar 16 comments Our clients have raised over $ 2.5 M in funding. Here’s what we actually do User Avatar 15 comments 🚀 I Built a Chrome ExtensionThat Turns Reddit Into a Real-Time Lead & Research Engine(Free for First 10 Users) User Avatar 13 comments How I got my first sale from a forgotten project User Avatar 11 comments