Saving what visitors submit
The difference between collecting submissions and needing a real database, and how Sneh decides which your app gets.
Two different needs
Most apps only need to collect things: signups, contact messages, orders of interest. Those go to Sneh Data, which works with no setup from you — the form saves, and you can read what came in from the workspace.
A database is a different requirement. It is for apps that must read their own data back out: a catalogue rendered from stored products, a dashboard over saved records, search across things people submitted earlier.
How the decision gets made
This is settled in the Product Brief, before the build, rather than discovered halfway through. The brief lists the collections your app will write to and states plainly whether a database is needed and why.
If the brief says no database and you know your app needs to read data back, say so at approval time. That is exactly the kind of correction the brief step exists for.
Where your data lives
Submissions work identically in the sandbox preview and in the deployed app, so a form you test before launch writes to the same place as one a real visitor uses. You can view what has been collected from the workspace at any time.
Read next
- Adding API keys and secretsHow to give your app access to another service without pasting a key into your code or a chat message.
- The Product BriefSneh writes a plan before it writes code, and asks you to approve it. Here is what is in it and why it matters.
Did this miss what you needed? Email hello@sneh.ai — or browse the rest of the help centre.