One paragraph in,
a running app out

1. 1 a few seconds

   Describe the idea in one paragraph

   You doType your idea, attach a document if you have one, then choose a style, a budget and how closely you want to approve each step.

   AppForge doesAppForge sets up everything else, and all of it can be changed later.

   You start in plain words and never write a spec yourself. An existing document, such as a BRS, can be attached as it is.

   

2. 2 1 min 5 s

   AI turns the idea into requirements

   You doRead it, then approve it or ask for changes.

   AppForge doesIt writes the user groups and a feature list a team could work from straight away.

   Requirements you can check line by line, in about a minute.

   

3. 3 3.3 min

   A council of six AI designers

   You doReview the overall design, the risks and the first screen.

   AppForge doesSix AI agents work at once on UX, architecture, database, API, mobile and security, and their work is merged into one document.

   MindDNA got 8 screens, 9 tables and 8 APIs, with its CRITICAL risks flagged, before a line of code was written.

   

4. 4 under 30 s

   The API Spec form: the heart of 6GL

   You doCheck the form the AI filled in, choose who may access each table, and answer only what the system asks.

   AppForge doesEvery API is sorted into a kind the compiler understands, such as crud, query or aggregate, and the rest are marked custom.

   This form is the blueprint a person approves and the compiler reads. MindDNA was asked one question: a relation to a table that does not exist.

   

5. 5 one AI call

   Check each screen's words in Thai and Chinese

   You doOn a compiled screen, open Words on screen and change any word. On a form drafted earlier, press Translate the missing words.

   AppForge doesA small AI translates the page titles and field labels once. A word you wrote is never overwritten, and an empty box keeps the English.

   ClinicAi got all 43 missing words from one AI call costing less than one baht, so its compiled pages speak the user's language.

   

6. 6 one click

   Approve the form

   You doPress Approve.

   AppForge doesIt fixes what the compiler writes by itself and what is left for the AI.

   For MindDNA the compiler writes 5 of 8 APIs and 3 of 8 screens with no AI at all, with the same result every time.

   

7. 7 before every payment

   See the price before you build

   You doChoose a budget: Premium, Balanced, Economy or Scaffold only. Then approve: the credits are taken at that moment, at exactly the price shown. Everything before this was free.

   AppForge doesIt prices only the work left after the compiler, and adds the 11 recommended kits.

   MindDNA cost 109 credits. Had the AI written the whole app, it would have been 145. The difference is what 6GL does for free.

   

8. 8 15.6 min

   Five build stages, every file checked

   You doWait, and follow each stage with its real time.

   AppForge doesBackend, Frontend, UX/UI, QA and Deploy. Every file the AI writes must be complete, import only what exists, and call only APIs the app has.

   In this run a test file the AI wrote was incomplete. The system caught it, charged nothing, and the stage passed on a rerun in 6 seconds; since then the QA stage repairs such a file once by itself. All 5 AI-written pages called the right APIs.

   

9. 9 2.5 min

   Open the preview and use the real app

   You doPress Start preview in Studio, then open the app on its own link.

   AppForge doesThe whole app runs, its web pages, API and its own database, on a preview link, and stops by itself when it is not in use.

   MindDNA was running on its preview at 11:12, 27 minutes after the idea was typed.

   

   What the app looks like: one theme, one language, one menu

   Pages the AI wrote and pages the compiler built both sit in the app's menu, use the theme's colours and speak the user's language. A page that needs data no API provides yet says it is not available, instead of calling something that does not exist.

   

   

   

   These are the same production build, opened on a test machine, because these pages need an account.

10. 10 at once

    Keep editing on the real screen in Studio

    You doClick a spot on the running app and change it there.

    AppForge doesAn edit with a fixed address lands at once and is free. Anything bigger is priced first.

    The Studio guide book walks through all six steps.

    

11. 11 one click

    Publish, or take the code further

    You doPress Publish & get a live link, push to GitHub, or download a .zip.

    AppForge doesYou get a link to share at once, with nothing to install, and can add ready-made kits from the library of 87.

    You get the app's full source code, not a mock-up.

    

MindDNA: the compiler wrote 5 APIs and 3 screens; the AI wrote 3 APIs and 5 screens.

Three checks on every file the AI writes

1Open Studio

Studio starts a copy of your app by itself. The first start takes about a minute. If your app is already live, the live app stays as it is.

2Your app, running inside Studio

Running, the time left before it stops by itself, and a line saying you are editing a copy.

3Pick the spot to change

A frame on what you clicked. Solid means Studio can change it exactly, for free. Dashed means you describe the change in words and see the price first.

4Change a colour

The page changes at once. No AI is called and it costs 0 credits.

5Describe a change and see its price first

Before anything runs: how many AI calls, the estimated tokens, the credits and the provider's cost. Cancel costs nothing.

6Undo, and check before it goes further

Every edit, with its time and whether it was direct or AI. Environments move an edit through SIT, then UAT, and each stage runs the exact frozen code the stage before approved.

The Studio screenshots are from ClinicAi on production, 25 Sep 2026.