Skip to content

Build an app by describing it

What happens between the sentence you type into REM Vibe Coder and the app that comes back - and how to write the sentence so you get the app you meant.

RREM Vibe Coder team3 min read

Most app ideas start as one sentence. "A habit tracker where I tick things off and see my streak." "A booking page for my yoga classes." "A dashboard of this sales sheet." REM Vibe Coder is built to take that sentence seriously: you describe the app, and it plans, builds, tests and deploys a real one, with a backend and a database, not a mock-up.

This post walks through what happens to your sentence, and how to write it well.

Step one: your words become a plan

The first thing Vibe Coder does is not write code. It makes a plan: one quick step that turns your message into the features it will build, in your words, with no technology names. For

Build a habit tracker: add habits with a name and a colour, tick each habit off for today, and see each habit's current streak and the last 7 days.

the plan card read:

  • Add a new habit with a name and colour

  • Tick off habits completed today

  • See the current streak for each habit

  • View the last 7 days of each habit

  • Saves your data in a database

followed by the system's own steps: Build + unit tests, Preview, Workflow test.

The plan matters for two reasons. You can see, before anything is built, whether Vibe Coder understood you. And the build works only from the plan: once approved, the builder starts from a clean slate with your request and the plan, not the whole conversation. That keeps builds fast and their cost predictable.

In Auto the plan is approved automatically (you still see it). Turn on the Plan chip and it waits for you: change a line, drop a feature, or type "add a weekly summary", then Approve & build.

Step two: you never pick a stack

You will not be asked "React or Vue?", "which database?" or "which host?". Vibe Coder picks the stack itself (a FastAPI backend with a React front end by default) and starts installing dependencies before the first line of code is written. You describe what; it decides how.

Step three: questions only when they matter

If something in your description would really change what gets built, Vibe Coder asks, on a card with up to six options: "Should guests book without an account?" It does not ask about things it can decide sensibly on its own.

How to write a good description

The best descriptions answer who uses the app and what they do in it.

Weak

Strong

A CRM

A small CRM for my 3-person sales team: companies, contacts under each company, deals with a stage and an amount, and a board of deals by stage

A booking app

A booking page for my yoga studio: classes with a time and 12 places, people book with name and phone, and I see who booked each class

Expense app

An expense splitter for a trip: people, expenses paid by one and shared by some, and who owes whom at the end

Add what you care about: the data to keep, the rules ("no more than 12 people"), the look ("calm, our blue #3938b0"), the language of the labels. Do not worry about saying too much: the plan keeps it to at most eight features, and the rest can come as follow-ups.

Start without a blank page

Not sure how to start? Home has four starters (Habit tracker, Team task board, Booking page, Expense splitter) that fill in a description you can edit, and Templates has four finished apps (an analytics dashboard, a catalogue browser, a vision board and a marketing website) whose first message you can change before you start: "…for a bakery, in warm colours".

You can also attach a file. "Build a dashboard from this sales sheet" with an XLSX attached gets an app built around your real columns, and its workflow test checks that your imported rows actually appear.

Then keep talking

The first build is the start, not the end. "Make the buttons bigger." "Weekends should not break the streak." Each follow-up gets its own small plan, its own checks and a new deploy at the same link.

Create your account and describe the first app you have been putting off. The user guide has every step in detail.

REM Vibe CoderSecurity

How REM Vibe Coder keeps your apps safe

An AI that writes and runs code needs walls around it. The sandbox, the network rules, the permission cards, the redaction and the push filter that REM Vibe Coder puts around every build.

RREM Vibe Coder team18 Nov 2026 · 3 min read
Build an app by describing it · REM Platforms Blog