Skip to content
Exepad Docs

How Exepad works

Exepad turns a description into a real, working web app. You say what you want in plain language, Exepad builds it, and you refine it by chatting — the same way you’d give feedback to a designer. No code, no setup.

From idea to app in one sentence

Section titled “From idea to app in one sentence”

Tell Exepad what you’re trying to make:

“A task tracker where I can add tasks with a due date, mark them done, and filter by what’s left.”

Exepad builds a complete app from that — designed pages, working buttons and forms, and a place to store your data. It’s a genuine app you can click through and use right away, not a picture of one.

What your app is made of

Section titled “What your app is made of”

Every app is built from a few simple pieces. You don’t manage them by hand — Exepad assembles them for you — but knowing the vocabulary helps you ask for exactly what you want.

Your app Pagesthe screens Designthe look & feel Datawhat it remembers Accountsoptional login Featuresforms, blog, email
  • Pages — the screens of your app (a home page, a dashboard, a settings page). You can ask for as many as you need.
  • Design — the colors, fonts, and overall look. Ask for “clean and minimal” or “bold and colorful,” or point Exepad at a style you like.
  • Data — information your app saves and shows, like a list of tasks, customers, or bookings. Add data whenever your app needs to remember something.
  • Accounts — an optional login, so each person who uses your app signs in and sees their own information.
  • Built-in features — ready-made capabilities you can switch on, like a contact form, a blog, or email notifications.

How you build and refine

Section titled “How you build and refine”

Building is a conversation, not a checklist:

  1. Describe it. Write a sentence or two about what you want. The more specific about what it does and what it stores, the closer the first version lands.
  2. Review it. Exepad shows you the working app in a preview.
  3. Refine by chatting. Ask for changes in plain language — “make the header dark,” “add a priority field with a colored tag,” “put the newest tasks on top.” Each request updates the app.
  4. Repeat until it’s right. Small, one-idea requests work best.

Draft and published

Section titled “Draft and published”

Your app has two states:

  • Draft — your private working copy. Only you can see it while you build and refine.
  • Published — the live version, out on the web at its own link (your-app.exepad.app, or your own custom domain) for anyone you share it with.

Publishing is a single step, and you can publish again any time you make changes — or roll back to an earlier version if you need to.

What you can build

Section titled “What you can build”

Exepad is a fit for a wide range of apps, for example:

  • Tools that track things — task managers, CRMs, inventory, applicant trackers.
  • Sites that collect information — contact forms, sign-up pages, surveys, booking pages.
  • Content sites — landing pages, portfolios, blogs, documentation.
  • Internal apps — dashboards and admin tools for your team, behind a login.

Next steps

Section titled “Next steps”