shalom cohen

Can You Really Build an App with One Prompt? I’m Trying to Do the Opposite

by

TL;DR
Building a planning-first vibe coding tool - not “one prompt apps”, but real specs, architecture, and step-by-step build plans.
Looking for honest dev feedback on what actually matters in planning.

Hi everyone!

Based on feedback from my previous post, I want to clarify something upfront:
I use AI to polish my English since it’s not my native language - but the ideas, structure, and opinions in this post are entirely my own.

I’m looking for feedback specifically from experienced developers who actively use vibe-coding tools.

What am I trying to build?

I’m working on a platform that focuses only on the planning stage of app development.

In a world where many tools sell the illusion of “build an app with one short prompt”, I’m trying to build the opposite:
bottom-up, structured, and stable planning process that enables flexibility in code, real customization, and long-term maintainability.

User input

The user describes their app in free text and can optionally define specific elements:

  • a special page

  • a specific feature

  • a particular design preference

Output

The user first gets a basic product specification.
After approval, they can generate additional layers:

  • technical specification

  • market research

  • mockups

  • data schema and diagrams

  • a chat to discuss and refine the content

  • very long, detailed, step-by-step build prompt

Target audience

Somewhere between:

  • developers with experience who want to upgrade their planning process, and

  • entrepreneurs who understand that building an app is not a “one-line prompt” problem

What do I need from you?

I’m not a programmer.
I understand basic code and how systems work, but I don’t fully know what the right planning outputs should look like from a professional developer’s perspective.

So I’d really appreciate your honest input:

  • what do you think about the solution I’m proposing?

  • would you personally use something like this?

  • what additional outputs would you expect from a serious planning tool?

  • what feels unnecessary or missing?

thank you!

3 views

Add a comment

Replies

Be the first to comment