Create a tracking app that fits how you work
Start with records, statuses, search, and a clear saving method, then decide if you need a team and accounts.
Let's understand the idea
You may need to track customer orders, content production, or expenses. Write down what each record contains, the statuses it moves through, and who can add, edit, and view it. This clarifies whether you need a tool on your device or an app for a team.
Local storage does not sync across devices, and an interface showing usernames does not prove permissions work. Start with sample data and test adding, editing, filtering, reopening, and exporting. If you need accounts and private data, ask for an actual architecture, storage, and permissions, and test them.
Tools for this workflow
Choose from what's available to you. You can use these prompts with several tools. What they can carry out depends on supported features and files.
See tool details and uses in the Tools library →Examples to expand the idea
A private tutor cannot remember who has paid and who has not. He describes an app to Lovable with the student’s name, lessons, amount paid, and balance. He starts opening it on his phone after every lesson, with overdue payments shown in red.
Invoice and expense inbox
Uploading an invoice photo and extracting its data requires a real service and checking the date and amount before saving. Test duplicates, exporting, and privacy.
Track job opportunities
An organization, original link, date, status, and follow-up date, without automatically sending anything just because the status changes.
Bookings or orders
Clarify the difference between a form that records a request and confirmation of availability or payment, and test the message the user receives.
Steps from start to delivery
Open any step by its heading. Each explains what to do, why, and what to check before continuing.
1Map the record’s workflowA clear record and workflow.Details
The fields should support actual tracking.
What should I do?
- Define the record type, fields, and statuses.
- Write down who does what and in what order.
2Define storage and usersSpecific storage and access requirements.Details
Your storage choice changes what can be shared.
What should I do?
- Decide between one device, a team, or multiple devices.
- Define private data, permissions, and what happens when data is deleted.
3Build the first flowThe main task works from start to finish.Details
A small, complete flow is better than screens with no working behavior.
What should I do?
- Start with adding, editing, and searching for a record.
- Use labeled sample data and empty and error states.
Tools for this part: choose oneA guide for this stepHow do you get started with ChatGPT and produce work you can use?4Test storage and permissionsStorage and access that match the description.Details
A record appearing the first time is not enough.
What should I do?
- Reopen the app and test exporting, duplicate entries, and incomplete entries.
- If there are accounts, test separate users and confirm they cannot see each other’s data.
5Review usage before expandingA useful version whose data you know how to recover.Details
Adding features too early can complicate a simple process.
What should I do?
- Try a day’s work with nonsensitive material.
- Fix the fields and filtering before adding alerts or external connections.
Prompts for your work
Open a prompt and fill in your details. Empty fields remain visible so you don't forget them.
Build the tracking appOpen it to copy or tailor the prompt
Prepare the listed inputs and start with the prompt in an available tool. Open the output and review it against your work.
Copy the prompt as it is, or tailor it with your details first.
Tailor the prompt to your workOptional: add your details and the prompt adjusts itself
View full prompt
Why is the prompt written this way?
Clarifying behavior and inputs helps us build something people can use, beyond just a page's appearance.
Review data and accessOpen it to copy or tailor the prompt
Copy the prompt as it is, or tailor it with your details first.
Tailor the prompt to your workOptional: add your details and the prompt adjusts itself
View full prompt
Did the result serve your original goal?
Return to the inputs and sources, and open the output where you'll use it. Check these points before relying on it.
- Does saving persist as required?
- Do users see only what belongs to them?
- Have editing, exporting, and errors been tested?
If there's a problem, name the unsuitable part, show an example, and request a specific edit.