# Create a Classic App
> Part of the NocoDB documentation (Classic Apps). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.
URL: https://nocodb.com/docs/classic-apps/create-classic-app
Last updated: 2026-10-21
Create a NocoDB classic app (formerly an interface), the equivalent of an Airtable interface: name it, select a layout and connect it to a table.
Build a classic app for [this table]
Build a classic app for [managers] with a page of [team tasks] and a page of [project status]
Build a classic app with a form to [submit support requests] and a page to [track them]
A NocoDB classic app starts with a guided setup: you name the app, select a layout for its first page and connect that page to a table.
## Before you start
Each classic app is for a specific audience, and each audience needs something different. For example, a field technician may only need to log site visits. A finance lead wants a summary of spend across all projects.
First decide who the classic app is for and what they must do. This decision makes the rest of the setup easier. It tells you which records to show, which actions to give and who gets access.
If you do not know where to start, complete this sentence:
> I'm building an app to **\[action]** for **\[audience]**.
For example: "I'm building an app to triage incoming support tickets for our customer success team."
Keep that answer near you during the setup below. Use it to decide what goes in the classic app and what to leave out.
## Create a new classic app
The **Classic App** card in the product shows the **Formerly Interfaces** badge.
1. Open your project. In the mini sidebar, click **Apps**. The **Apps** page of the project opens.
2. Click **New app** in the project sidebar. The **Create an app** dialog opens.
3. On the **Classic App** card, click **Build from views**. The guided setup opens.
Where AI apps are not available, **New app** opens the guided setup directly.
On a project that has no apps, the **Apps** page offers **Build from views** on the **Classic App** card. It opens the same setup.
### Step 1: Name your app
The first step is **Name your app**. You share classic apps with other people, so give the app a name that your team can use. You can also customize:
| Setting | What it sets |
| ---------- | ----------------------------------------------------------------------------- |
| **Icon** | An icon from the searchable icon library. |
| **Colour** | An accent color for the classic app. |
| **Style** | The visual style of the app chrome: **Bold**, **Quiet**, **Wash** or **Ink**. |
You can change these settings later from the context menu of the classic app. See [Actions on a classic app](/docs/classic-apps/actions#classic-app-actions).
### Step 2: Choose a layout
Select the layout for the first page of your classic app. For a guide to each layout, see [Page layouts](/docs/classic-apps/layouts).
### Step 3: Connect to a table
Most layouts show data from a table. In this last step, select the table that the page connects to. Some layouts have more settings:
| Layout | Setting |
| ----------- | ------------------------------------------- |
| **Kanban** | The single-select field for **Stacked by**. |
| **Gallery** | An optional **Cover image field**. |
Layouts that do not show table data, for example **Overview**, skip this step.
For the **Grid** and **Record review** layouts, you can also [copy settings from an existing view](#copy-settings-from-a-view) of the connected table in this step.
On the last step, click **Create app**. The classic app opens in the [classic app builder](/docs/classic-apps/builder). You can then start to design it.
## Copy settings from a view
The **Copy settings from a view** option starts a new **Grid** or **Record review** page with the settings of a view of the connected table. Use it when the table already has a view that looks the way you want the page to look. You then do not have to make its filters, sorts and field settings again. The option is in the **Connect to a table** step.
1. In the dropdown, select the source view. The list shows all views of the connected table, except **Form** and **Map** views.
2. Click **Choose settings**.
3. Turn on the settings to copy, or click **Select all**. The button shows the number of selected settings.
4. Create the page as usual. NocoDB applies the copied settings to the page. You can change them later in the builder, as on any other page.
You can copy the same settings as in the [Copy another view's configuration](/docs/product/tables/views/actions-on-view#copy-another-views-configuration-) dialog: **Field visibility**, **Field order**, **Column width**, **Row height**, **Filter condition**, **Group**, **Sort** and **Row coloring**.
You can copy across types. For example, a filtered Grid view can be the source for a Gallery page. NocoDB offers only the settings that the destination layout can use:
| Destination | Available settings |
| ------------------------- | ------------------------------------------------------------------- |
| Grid, List | All eight |
| Timeline, Gantt | All except Column width |
| Gallery, Kanban, Calendar | Field visibility, Field order, Filter condition, Sort, Row coloring |
| Record review | Field visibility, Filter condition, Group, Sort, Row coloring |
Settings that the selected view cannot give are grayed out. If you change to a source view or visualization that does not support a selected setting, NocoDB removes that setting from your selection automatically.
Some view settings, such as certain filter conditions or grouping, have no equivalent on a classic app page. NocoDB does not copy them. The wizard warns you before it creates the page.
## Add pages to a classic app
A classic app can have many pages, but your plan may limit the number. To add a page:
1. Put the pointer on the classic app in the sidebar, or use the page list in the builder.
2. Click **New page**.
3. Select a layout. If the layout needs a table, connect it to a table. The setup is the same as for a new classic app, but without the naming step.
The app navigation shows the pages in the listed order. You can drag pages to change their order, rename them inline or hide them from the navigation. Hidden pages stay available for contextual use. For example, a [record detail page](/docs/classic-apps/layouts/record-detail) opens when a user clicks a record.
Every classic app must have at least one page, and at least one page visible in the navigation.
## Availability
* Only project creators and owners can build classic apps.
---
## Related pages
- [Classic Apps](https://nocodb.com/docs/classic-apps.md): NocoDB classic apps, formerly Interfaces, are the equivalent of Airtable Interfaces: build custom apps on your project data from page layouts, without code.
- [Classic App Builder](https://nocodb.com/docs/classic-apps/builder.md): The NocoDB classic app builder, formerly the interface builder, is the equivalent of Airtable Interface Designer: design, configure and preview pages.
- [Fields, Buttons & Filters](https://nocodb.com/docs/classic-apps/elements.md): Fields, field groups, buttons and user filters on NocoDB classic app pages (formerly interfaces), and how to configure each element in the builder.
- [Publish a Classic App](https://nocodb.com/docs/classic-apps/publish.md): Publish a NocoDB classic app (formerly an interface), the equivalent of an Airtable interface: edit a draft in the builder, then publish your changes.
- [Actions on a Classic App](https://nocodb.com/docs/classic-apps/actions.md): Rename, restyle, duplicate, reorder, hide and delete NocoDB classic apps (formerly interfaces, the equivalent of Airtable Interfaces) and their pages.