# Classic Apps
> 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
Last updated: 2026-10-21
NocoDB classic apps, formerly Interfaces, are the equivalent of Airtable Interfaces: build custom apps on your project data from page layouts, without code.
**Classic apps** let you build custom, easy-to-use apps on top of your NocoDB project data. Classic apps were called **Interfaces** before. The project sidebar lists them under **Apps**, next to the AI app of the project.
You do not give everyone access to the full project with all its tables, views and configuration options. Instead, you design focused pages. Each page shows only the data and actions that its audience needs. For example:
* A review queue for approvers.
* A dashboard for leadership.
* A form for field teams.
* A full internal tool that combines all of them.
Build a classic app where [the sales team] can see and update [their deals]
Build a classic app with a page that lists [open orders] and a form to add new ones
Add a page to this classic app that shows [a dashboard of open tickets]
Publish this classic app
## Classic apps were Interfaces
NocoDB renamed Interfaces to classic apps. The product lists them under **Apps**, next to [AI apps](/docs/apps). Your interfaces are now your classic apps, with the same pages, access and published versions. Some labels in the builder still say "interface", for example **Restrict interface sharing** and **Go to interface page**.
NocoDB classic apps are the NocoDB equivalent of Airtable Interfaces, which you build in the Airtable Interface Designer.
## Classic app or AI app?
A NocoDB project can have both kinds of app. A classic app is a set of pages that you put together from layouts, without code. An [AI app](/docs/apps) is one custom app that [NocoAI](/docs/product/noco-ai) writes for the project, with its own screens, logic, teams and API.
On the **Apps** page of a project with no apps, NocoDB offers both kinds side by side. The **Classic App** card shows the **Formerly Interfaces** badge.
| | Classic app | AI app |
| ------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------- |
| **How you build it** | Pick a layout for each page and configure elements. Start from your existing views. | Describe the app to NocoAI. NocoAI writes the app code. |
| **Best for** | Trackers, intake forms, dashboards | Portals, approvals, partner tools |
| **How many in a project** | Any number, up to the limit of your plan | One |
For the full comparison of builders, access, releases and data, see [Apps vs Classic Apps](/docs/apps/apps-vs-classic-apps).
## How classic apps are structured
| Concept | Description |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Classic app** | A named app in a project. Each classic app has its own icon, color, style, pages and access controls. The project sidebar lists classic apps under **Apps**. |
| **Page** | A screen in a classic app. Each page uses one of six [layouts](/docs/classic-apps/layouts). Pages show in the app navigation. You can also hide a page and open it from context (for example, a record detail page that opens when you click a record). |
| **Elements** | The building blocks on pages: visualizations, widgets, fields, buttons and filters. See [Fields, buttons & filters](/docs/classic-apps/elements). |
| **Draft & published versions** | You make your changes in a draft. Viewers always see the last published version. You can change the draft safely and [publish](/docs/classic-apps/publish) when it is ready. |
## Page layouts
Each page in a classic app uses a layout:
| Layout | Purpose |
| --------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| [Table](/docs/classic-apps/layouts/table) | Work with records in Grid, Gallery, Kanban, List, Calendar or Timeline visualizations |
| [Record review](/docs/classic-apps/layouts/record-review) | Go through records one at a time. Good for approval and triage flows |
| [Dashboard](/docs/classic-apps/layouts/dashboard) | A high-level view of your data with charts, metrics and other widgets |
| [Form](/docs/classic-apps/layouts/form) | Let users create new records with a guided form |
| [Overview](/docs/classic-apps/layouts/overview) | Welcome users with links, bookmarks and resources |
| [Record detail](/docs/classic-apps/layouts/record-detail) | A reusable detail page for one record, opened from other pages |
## Who can do what
| Action | Who and how |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Build** | Only project creators and owners can create and edit classic apps. |
| **Use** | Collaborators use the published version of a classic app. Their roles control their access, at the app level or for each page. You can invite people who have no project role to a classic app. This makes classic apps a safe way to share data with a larger audience. |
| **Share publicly** | You can share single table and dashboard pages to the web as read-only pages, with an optional password. Public sharing comes in a separate release phase and is not available yet. |
## Get started
1. [Create a classic app](/docs/classic-apps/create-classic-app) with the guided setup.
2. Design pages in the [classic app builder](/docs/classic-apps/builder).
3. [Publish](/docs/classic-apps/publish) your changes and share the classic app with your team.
Published classic apps are fully responsive and work on mobile devices. The classic app builder itself is desktop-only.
## Availability
* Classic apps are available on all NocoDB Cloud plans and on self-hosted deployments. The Community Edition includes 2 classic apps with up to 2 pages each. Some classic app capabilities need a paid plan.
---
## Related pages
- [Create a Classic App](https://nocodb.com/docs/classic-apps/create-classic-app.md): 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.
- [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.