Updated October 31, 2026

A drag-and-drop database lets you model data visually instead of writing a schema by hand. In Form.io, you drag components onto a resource, and that resource becomes the data model, the place your records are stored, and a REST API your app can read from and write to. This is the story of a front-end guy who used one to build an app without ever thinking of himself as a database person.

On a whim.

Through an unexpected set of circumstances, he started building an app, more of a proof-of-concept (POC).

Hold up a sec, I need to explain something.

He never considered himself a “developer.”

I mean, how much code/languages/technologies do you have to know to call yourself one?

Regardless, he always saw himself somewhere in between a power-user and a dev.

He knew HTML, CSS, and a little JavaScript. A front-end-ish guy—maybe some would call him a “dev.”

He could design an app, but he couldn’t architect one or build one out. Databases are like Kryptonite to front-end folks. IYKYK.

Well, that all kind of changed last week.

You see, he’d been drinking the Form.io elixir for a while now and it finally hit him.

“I don’t have to be a database person to build an app.”

Maybe it used to be that way, but not anymore. Not with today’s tools.

He had this old project collecting dust on the bottom shelf in the back room of his hard drive, so he decided to clear off the dust like blowing out a well-loved Nintendo cartridge from the 80s and see if he could make it work.

Modeling Data Visually With a Drag-and-Drop Resource

The first thing he did was open up Form.io and create a resource.

Then he dragged a few components onto a form-resource, stared at it, and just sat there thinking:

“What would be the best way to…”

He was modeling data—visually.

He had never “modeled data” before, but it seemed so much more approachable and achievable because it could be done visually.

He had never set up an API endpoint before either, but Form.io wrote it for him.

So he wrote some JavaScript that connected to that API, then some to make the data display in his app.

We’re not talking about embedding forms—no. We’re talking actually pulling data from the Form.io database so that it displays natively in the app.

Like, real dev stuff.

And when he got stuck, a little help from ChatGPT was there to fill in the gaps.

Afterwards, he went gangbusters and got data sending, updating, etc.

Do you remember when you were a kid and you learned how to ride a bike? And the first time you got going on your own—and kept going? That’s how he felt.

For any dev who remembers the first time they got something working, you know the feeling.

Why This Isn’t Really About Forms

So why am I telling you this story?

Because none of this is really about FORMS in the traditional sense. He wasn’t building a form-based app (which are all good and necessary). But we often get pigeon-holed into being perceived as a tool ONLY to help you with your forms in some way.

No, this was a productivity app for organizing research and building workflows. And Form.io bridged the gap to a new kind of tool-builder, one who never considered themselves a dev.

This is the democratization of technology happening before our eyes. More people are going to build tools, there will be more innovation, and Form.io is going to be in the middle of it.

How a Drag-and-Drop Database Works in Form.io Today

The steps in his story still line up with how Form.io works:

• Drag components onto a resource. Resources are built with the same drag-and-drop builder as forms. Each one defines a data object: the back-end data model, its API, and the front-end UI.
• The API comes with it. The builder outputs a JSON schema, and that same schema defines the REST endpoints that accept submissions, so there is no separate back-end setup step.
• Your app reads and writes the records. Once a resource exists, your app can create, read, delete, and query its records like any other database collection. The JavaScript SDK has calls such as loadSubmissions and saveSubmission for this, which is the “pulling data so it displays natively” part of the story.
• Storage is handled. Submission data is collected and stored automatically on MongoDB or an equivalent, such as MongoDB Atlas, AWS DocumentDB, Azure Cosmos DB, or MongoDB Enterprise Advanced on premises. Data can also be sent on to other databases.
• You still build the app. Form.io handles the forms, data models, and APIs. Routing, page layouts, and business logic beyond validation live in your own app code, just like the JavaScript he wrote.

Sources: Form.io’s Resources and JavaScript SDK docs, how the drag-and-drop builder creates an API, and How Form.io works. Keep reading: Model Data In A Schema-Less Data Environment With No-Code, Build Features With A REST API Layer For Rapid Deployment, and Why You Shouldn’t Use Form.io If You Don’t Have a Dev Team. Want to try it? Start a free 30-day trial or contact us.