Projects and databases work together in GlideOS.
Every project has one database. Every app in that project can use that same database, so related apps can work from the same information.
This is especially useful when you start from a spreadsheet. Glide can use the spreadsheet to understand the information your business already runs on, then help turn that information into apps, screens, and dashboards.
A project brings related work together:
Tables are like sheets in a spreadsheet. They hold rows and columns of information, such as customers, orders, tasks, products, locations, or events.
When your app needs data, Glide can help structure that data into tables that make sense for the app you are building.
Views are ways for Glide to look at table data for a specific purpose.
For example, a view might help power:
Glide creates views automatically when they are needed for certain features or screens. You can view them, but you do not create or edit views directly.
Tables may be editable. Views are read-only.
The project workspace lets you look at the data behind your app while you are building. This helps you understand what Glide is using, spot missing information, and make better decisions about what the app should show.
You can also ask Glide to help structure the data your app needs. For example, you might ask Glide to organize uploaded spreadsheet data, add a table for a new workflow, or adjust the structure so a screen or dashboard works better.
Because every app in a project uses the same project database, you can build multiple apps for the same workflow.
For example, one project might include:
Those apps belong together because they use the same data.
Use a separate project when apps should not share the same database.
For example, a sales pipeline app and an employee equipment tracker should usually be separate projects unless they are part of the same workflow.