RumataTutorial: Build a feedback board
Create a feedback board from a prompt, try it with sample data, and make your first improvement.
Step-by-step guidance.
Before you start
- A Rumata account with an active subscription. Follow Set up Rumata if you have not signed in yet.
- A project you can build in. Your private project normally appears in the Home project picker.
What you’ll build
This optional tutorial applies the four-step app-building guide to a small app called Feedback Board. Someone submits an idea, the idea appears in a list, and you can mark it as planned. This is a starter exercise: use fictional feedback while you learn.
The prompts below are examples, not a prebuilt template. Rumata may ask questions or produce a different layout. Use the checks in this guide to decide whether the result works. Build time depends on your request and workspace.
| You’ll use | What it does |
|---|---|
| Home | Starts a new factory inside your selected project. |
| Chat | Plans and builds your app, then makes changes. |
| Preview | Lets you use the app before publishing it. |
1. Describe the app
- Open Home (opens in a new tab) and select your project below the prompt box.
- Keep Plan selected. Paste the prompt below, then choose Send once.
- Wait for the factory workspace to open. Confirm your message appears in the conversation.
Build an app called Feedback Board for collecting product ideas.
Start with one page: a form with title and description, a list of saved
ideas, and a status for each idea: New or Planned. Let me change the
status and filter the list by it. Save ideas so they survive a reload.
Use fictional sample data. Keep the layout usable on a phone.
Plan the smallest working version first. Do not publish it yet.2. Review the plan and build
Check that the plan includes the form, saved ideas, status changes, and a filter. For this first version, you do not need payments, email, or an external integration.
- Answer any questions in the workspace chat. If the plan includes extra features, ask Rumata to keep this version small.
- When the plan matches your request, approve it using the offered chat controls or explicitly ask Rumata to build that plan.
- Wait for the build to finish, then open Preview Mode.
3. Submit one idea and check it stays saved
- In Preview, submit an idea titled “Add a dark theme” with the description “Make the board comfortable to read at night.”
- Confirm it appears once in the list with status New.
- Change its status to Planned. Filter by Planned and confirm the idea is visible.
- Reload Preview. Confirm the idea and its Planned status remain.
- Switch the preview size to Mobile and repeat the form and filter actions.
In Feedback Board Preview, I submitted “Add a dark theme” and changed
its status to Planned. After reloading, the idea disappeared.
I expected the idea and its status to stay saved. Please find the cause,
fix it, and verify the same steps with sample data.4. Make one change
Once the basic task works, ask for one improvement. A focused request is easier to review and test than a long list of unrelated changes.
Add a count beside each status filter so I can see how many ideas
are New and Planned. Keep the existing records and behavior.
Verify that each count updates when I change an idea’s status.- Send the request in the same factory’s chat and wait for the change to finish.
- Move one idea from New to Planned. Check that both counts change correctly.
- Reload and repeat the original form-and-filter task to check that it still works.
Next: get ready to share
You now have a first app to build on. Before real people use it, decide who can submit, read, and change feedback. Ask Rumata to implement those access rules and test them with separate accounts.
When the app is ready, follow Publish your app. Publishing has its own review and verification steps; a working preview is not yet a live release.
Want to see where the ideas are stored? Open Database. Want to automate what happens after a submission? Try your first workflow.