How Your App Data Works
When you describe your app, Proyecta plans the data model, provisions real collections, and seeds them with realistic sample content before the UI is built. Your app ships wired to real, owner-editable data from the very first build — no placeholder mock data to swap out later.
You don’t design a database, write schemas, or wire up an API. You describe what you want in plain language, and Proyecta builds the data layer first, then builds a bespoke interface on top of it. This page explains what happens under the hood so the rest of the data docs make sense.
What happens when you describe your app
Section titled “What happens when you describe your app”- You describe your app in chat — what it’s for, who it’s for, what it should do.
- Proyecta plans the data model — which content collections your app needs (chosen from ready-made designs or designed custom) and which capabilities are on (forms, commerce, auth, and so on).
- The platform provisions and seeds those collections with real, realistic sample content — deterministically, before any UI exists. Your “posts”, “services”, or “menu” already have believable entries in them.
- Proyecta builds the bespoke UI against that real data — pages, components, and an admin panel to manage it — reading through typed content hooks the AI writes for you.
Because the data is real from step 3, what you see in the preview is what your app actually does — not a static mockup that breaks the moment you edit something.
The layering guardrail
Section titled “The layering guardrail”Proyecta splits every app into two layers, and treats them very differently:
- The plumbing is pre-built and deterministic. Your data model, the seeding, the admin panel, form handling, auth, and the capability wiring are assembled from tested, reusable pieces. This is the part that has to be correct, so it isn’t improvised page by page.
- The public-facing UI is bespoke and AI-authored. Your marketing pages, layouts, components, and brand are written fresh for your app — never stamped out from generic templated sections. This is the part that has to be distinctive.
The payoff: your app gets a solid, reliable backend and a one-of-a-kind front end. The AI spends its creativity on what visitors see, and leans on proven machinery for everything behind it.
Where your data lives
Section titled “Where your data lives”Almost every app’s data lives in the CMS — Proyecta’s built-in, managed content store. It’s the default home for durable content and records: posts, services, listings, FAQs, a product catalog, bookings, and your business info. You never run or manage it; it’s just there. See Content Management.
A smaller set of apps need data that changes live — a chat that updates as messages arrive, an activity feed, presence (“who’s online”), or multiplayer game state. A dedicated realtime store for that behavior state is coming soon; durable content and the commerce catalog will still live in the CMS.
| If your app needs… | It uses… |
|---|---|
| Content, records, a catalog, forms (the common case) | CMS (default) |
| User accounts & sign-in | Auth |
| Products, orders, payments | Commerce |
| Uploaded files & media | Files & Media |
You never have to decide where content, users, orders, or files go — the platform owns those. A realtime store for live behavior is coming soon; until then, apps that need live updates get everything else and are told the live piece is on the way.
Managing your data
Section titled “Managing your data”Once your app is built, there are two ways to work with its data — no code needed:
- Ask the AI in chat —
"Add a service called 'Deep clean' for $120","Edit the FAQ about refunds". It writes to whichever store the data lives in. - Your app’s admin panel — a sign-in-protected editor on your published app for managing content and form submissions directly, no AI required.
A realtime record browser for live-updating apps is coming soon. Manage your CMS content through your app’s admin panel or the AI.
Where to go next
Section titled “Where to go next”- Content Management — collections, entries, and fields.
- Forms — capture leads, quotes, and bookings into your admin inbox.
- Admin Panel — the built-in, no-code way to manage your app’s content and submissions.
- Database — how your data is stored, and the realtime database that’s coming soon.