> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/getting-started/choose-ai-or-classic-app-builder.md).

# Choose AI or Classic App Builder

**Prompt Assistant** is the starting point for a new app. Describe a task and the connected data, review what it builds, and request changes in plain language. Follow [Build your first app with AI](/getting-started/start-here.md).

![AI app creation begins with the dashboard prompt](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FLYcXgzVcQB0CAC4z5quh%2Fai-create-app-prompt.jpg?alt=media)

AI app creation starts with a description of the app you want.

**Classic App Builder** is the drag-and-drop editor for existing apps. Its guides cover pages, components, binding, variables, JavaScript, and visual design. Use Maintain an existing Classic app for changes to a Classic project.

![Classic builder with a visual canvas, component palette, and Parameters, Actions, Overlays, and Variables controls](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FRIJ2cdUu5dR1HqNd38On%2Fclassic-builder-overview.jpg?alt=media)

Classic apps use a visual canvas and a component palette. The example shows a product table.

Both modes can use Jet Admin data sources, workflows, access rules, and publishing features. Before changing a live app, test any generated queries, actions, and permissions in a separate environment. If you are moving a workflow from Classic to AI, start with one task and compare the result rather than treating the prompt as a complete specification.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/getting-started/choose-ai-or-classic-app-builder.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.