Your app's data

When your app saves something, such as a booking, a client or an order, it goes into the app's own database. Each project has its own database, so two apps never share data.

How crisp designs your data#

crisp reads your description and decides which kinds of records your app needs and which details each one has. For "a booking has a class, a time and an email address", it creates bookings and classes, and links each booking to its class. Its plan at the start of the build lists the data it will create.

Sample records#

crisp fills a new app with realistic sample records, so every page shows something useful while you build. If a table is empty, ask for sample records in the chat, or press Ask crisp to add sample rows in the Data tab.

Look at your data#

Open the Data tab to see every table and record, change a value, add a record or delete one. See The Data tab. You can also ask crisp a question about the data in the chat.

Change the shape of your data#

Ask for a new detail, a new kind of record, or a change to an existing one in the chat, like any other change: "Add a phone number to each client." crisp updates the database and the pages that use it.

The data in your preview#

Everything you add while you try your app in the preview is real and stays in the database. Sample records and test entries stay too, until you or crisp remove them.

Your published app has its own data, separate from the preview. When you publish for the first time, you choose whether it starts empty or with a copy of your preview's data. See Publish your app.