> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What is the difference between apps and tables
- URL: https://blog.jestor.com/difference-between-apps-and-tables/
- Published: 2026-09-16T18:50:53.000Z
- Updated: 2026-09-16T18:50:53.000Z
- Author: Bruno Bannach

The **difference between apps and tables** is the difference between data and presentation. A table is where the data lives, organized in rows and columns like a spreadsheet. An app is the visual layer built on top of it, deciding how that data is displayed. In **Jestor**, understanding this separation is what makes everything else make sense.

## Why the separation matters

If data and interface were the same thing, every way of looking at your information would require a copy of it. That is exactly what happens in a company running on spreadsheets: one file per view, all drifting apart.

Separating them means one set of data can be presented in as many ways as there are people who need it.

What the separation enables:

- A single dataset shown as a table, a board and a dashboard
- Changing how something looks without touching the data
- Different views for different roles, from one source
- Adding a new visualization without duplicating anything

## What belongs to each layer

| Concern       | Table                      | App                         |
| ------------- | -------------------------- | --------------------------- |
| Storage       | Rows and columns           | Nothing stored              |
| Field types   | Defined here               | Displayed here              |
| Relations     | Connections between tables | Navigated here              |
| Visualization | Not its concern            | Kanban, dashboard, list     |
| Layout        | Not its concern            | Blocks, colors, arrangement |

## Step by step to think about a new process

1. **Start with the data**: what facts need recording, and in which tables.
2. **Define the fields**, choosing the right type for each.
3. **Create the relations** between tables before building any interface.
4. **Then build the app**, choosing how that data should be presented.
5. **Add more views** as different people need different perspectives.
6. **Change the app freely**, since the data underneath is unaffected.

## Why beginners should build the table first

The most common mistake is designing the screen before the data model, which leads to fields invented to make a layout work. Getting the table right first means the app can be rebuilt any number of times without risk.

- **Table as the foundation:** a relational database under everything
- **App as the presentation:** how the data is shown, not where it lives
- **Many apps per table:** several views from one dataset
- **Safe redesign:** changing a view never threatens the data

## Frequently Asked Questions

### Is a table just a spreadsheet?

It resembles one, but it is a relational database with field types and connections. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can one table have several apps?

Yes. The same data can be presented in as many views as you need.

### What should I build first?

The table, since the app depends on the data model rather than the reverse.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.