Build an App With AI That Keeps Your Data

Act as the developer who fixes AI-built apps after they go live and knows where they break: the data is stored only in the browser and disappears when the person switches phones, everyone who logs in sees everyone else's records, and nobody knows how to make a copy of the data before changing something. Context: I want an app to [WHAT THE APP DOES, IN ONE SENTENCE - EX: manage the appointments and client history of my nail salon]. The people who will use it are [WHO USES IT AND HOW MANY PEOPLE - EX: me and two other nail techs, each on her own phone]. What the app needs to store is [WHAT IT STORES - EX: the clients, the booked appointments and what each client had done at each visit]. Who can see and change what is [WHO SEES WHAT - EX: each nail tech sees only her own appointments; I see everything]. The data includes [PERSONAL DATA - EX: the clients' phone numbers and dates of birth]. I want to open the app [WHERE IT OPENS - EX: on my phone, from an icon on the home screen, without downloading anything from the App Store or Google Play]. The tool I am going to use is [TOOL - EX: Lovable, Base44, Bolt, Google AI Studio or "I don't know"]. My level is [YOUR HONEST LEVEL - EX: I have never programmed]. What I can pay per month to keep the app running is [THE REAL LIMIT - EX: nothing at first]. Task: write THE BRIEF I paste into the tool so it builds this app with the data truly stored, and the order in which I ask for each part. Rules: 1. Before the brief, give me the smallest version: the screens and the data that go into the first delivery, what waits until later, and why. 2. Describe each thing the app stores as a table, with each field's name, its type and an example [EX: client - name (text) "Emily Carter", birthday (date) "03/12"], and say how one table links to another (one client has many appointments). 3. Spell out that the data lives in a cloud database, never only in the browser or in the phone's memory: data stored only on the device disappears when the person clears the browser or switches phones. 4. Build the who-sees-what table: each type of person in a row, each data table in a column, and in each cell "sees", "creates", "edits" or "nothing". Ask for this rule to be enforced in the database, not just by hiding the button on the screen. 5. Login only if more than one person uses the app or if it stores personal data; if there is a login, say how a person recovers a forgotten password. 6. For each piece of personal data I listed, write in one line why the app needs it; anything without a reason comes out of the brief. 7. Ask for a button that exports all the data to a spreadsheet (CSV) and say how often I download that copy. 8. Spell out the "DO NOT" block: no payments, no notifications, no table or field I did not ask for and no deleting data without asking for confirmation. 9. Do not decide in secret: anything my brief does not say becomes "[TO BE DECIDED: ...]", with the simplest option and the reason in one line. 10. Write the acceptance test as sentences of the form "I do X and I see Y", always with these three: I open the app on another phone and the data is there; I log in with someone else's account and I do not see what is not theirs; I export the spreadsheet and it opens with everything in it. Format of the answer: first the smallest version, in three lines. Then THE BRIEF, in a separate block and ready to copy, with the data tables and the who-sees-what table. Then the acceptance test as a numbered list. Then the "[TO BE DECIDED]" items that are left. And at the end, the message I send before asking for any change once the app already holds real data.