What should you describe first?
Start with one task a visitor needs to finish. For a community garden, ask for a page that lists available plots and records one request. Give the builder an example of what the visitor should see after sending it.
Where are requests saved?
An app connected to Atoms Cloud can save records in its database. Look for separate Development and Production databases when they are available. Decide which records belong in each before sharing a public link.
What do you pay for after you publish?
Atoms separates credits for making changes from Cloud & AI charges for published apps. Check the published-app rates and any available spending limits. A working preview only shows what you built, so estimate how often visitors will save records or use paid features.
How do you keep the app and its records?
Check whether your plan can download the project files from the editor. Export database tables separately as CSV files. Make another list for uploads, sign-in and connected services so you can see what a new host would still need.
How would you check a plot request on paper?
Draw what happens when a fictional gardener requests Plot 4 and returns later to find the result.
- Separate the two copiesWrite the made-up request under Development. Leave the Production list empty.
- Trace the confirmationShow where the request appears for the organizer and what the gardener sees.
- Plan the handoffPut the project files and the list of requests on two separate lines. Add a line for any files the app accepts.