One of the most frustrating parts of building an app is the empty state - you design it, build it, and then you're staring at blank screens and placeholder boxes, with a database still to set up before any of it feels real.

In Biscuit, that step is handled for you. Here's how it works, using an online course app as the example.

You explore your design on the canvas first, then hit Build. From your design, Biscuit works out the data models and creates them automatically - for a course app that's User, Course, Module, Enrollment, and Lesson. No schema design, no tables to define. 🎉

Then you land on a screen called "Bring your app to life with data," with a few ways to fill it:

* Create example data → fills every empty screen with realistic sample content (courses, modules, lessons). One click and the empty state disappears (this is the one in the video below).
* Use my files → upload a PDF, CSV, or XLSX, like your real course catalog or student list, and Biscuit populates the app from it.
* Pull from a website → point Biscuit at an existing page and start with content from there.
* Or "I'll add data later" if you'd rather skip it for now.

However you fill it, your data then lives under App → Data in a spreadsheet-style view you can scan, edit directly, or bulk-edit.

That empty → filled moment is small, but it's what turns a wireframe into something that feels like a real app.

  
Try this prompt👇 → [https://biscuit.so/](https://biscuit.so/)

    I want a platform where I can sell an online course. Each course has multiple lessons made up of video and written content. Students pay once to enroll, then work through the lessons in order and track their progress.
    As the creator I should be able to add lessons, organize them into modules, and see how many students are enrolled, who completed what, and total revenue. The student-facing pages should look clean and focused, with no distractions while they're learning.

Skip the database setup - Biscuit builds your data models and fills them