Free app launch checklist
Before you share it, try the whole journey.
Changing the journey, version or environment resets outcomes. Use invented records and separate test accounts. If setup is missing or a test would make a real charge or send a real message, leave it Not tested.
01 · Finish the main customer actionNot tested
Open a fresh customer session and submit one valid invented request.
Look for: The action completes with an identifiable result and the correct next step. A pending request is described as pending.
What did you enter, what reference or state appeared, and what happens next?
02 · Recover from missing informationNot tested
Leave a required field empty, submit, then correct it and try again.
Look for: The error explains the correction, preserves appropriate input and lets you finish without an extra record.
Which field failed, what did the message say, and did the corrected attempt finish?
03 · Find the saved record after refreshNot tested
Refresh or reopen the app and find the same invented record through the normal customer or owner route.
Look for: The record and its important fields remain correct. A success screen alone does not show this.
Which record did you follow, which fields survived, and where did you find it?
04 · Keep another person's record privateNot tested
In separate sessions, open test customer A's record address as customer B and, where access should be private, while signed out.
Look for: Unauthorized viewers cannot read the private record. The legitimate customer can still open their own record.
Who was signed in, whose record was requested, and what was displayed or refused?
05 · Refuse unauthorized changesNot tested
Have the implementation reviewer attempt an edit to A's invented record as B in an app you are authorized to test. Reopen it as A or the owner.
Look for: The unauthorized change is refused and the record stays unchanged. A hidden edit button alone does not establish this.
What edit was attempted, under which test identity, and what value remained? If you cannot observe this, leave it Not tested.
06 · Confirm and decline as the ownerNot tested
Create two invented requests. Confirm one and decline the other, then refresh and reopen both. Adapt the decisions to your app's workflow.
Look for: Both decisions persist on the right records and the customer sees the promised state where applicable.
Which records changed, what states remained, and what did the customer see?
07 · Repeat an action without accidental duplicatesNot tested
Repeat a submit or retry the same intended action, then inspect the saved records. Also try a deliberate new request.
Look for: A retry does not create unintended work, while a legitimate new request still follows the business rule.
How did you repeat the action, how many records appeared, and did a deliberate new request work?
08 · Complete the journey on a phoneNot tested
On a phone or clearly labelled browser emulation, finish the customer journey and any intended owner actions. Open the keyboard and correct an error.
Look for: The required controls, errors and confirmation stay reachable and readable throughout the journey.
What device or emulation width did you use, and was anything clipped or unreachable?
09 · Complete the journey on desktopNot tested
Complete the customer action and owner decision in a desktop browser. Try the main controls with the keyboard.
Look for: The intended journey works, with a visible current state and next action. This is a practical check, not a full accessibility review.
Which browser and window size did you use, and did any control or layout block you?
10 · Open the address customers will useNot tested
Open the actual published address in a fresh session. Repeat the main journey and check customer and owner access there.
Look for: The intended version is reachable and follows the expected access rules. Preview results and deployment badges are not this check.
Which published version did you open, which roles did you try, and what happened? Omit private or token-bearing links.
11 · Recheck after changing one business ruleNot tested
Review a recent change, or make one in a disposable test version before this review. Check its intended effect, then rerun the other applicable checks on that version.
Look for: The changed rule works and the other journeys still pass. Do not alter live business rules just for this worksheet.
What rule changed, what effect did you observe, and which checks did you rerun? Leave this Not tested if a safe change or regression evidence is unavailable.
12 · Find the owner's next moveNot tested
Ask the owner to locate the created record, publishing controls and a way to correct an ordinary mistake or get help.
Look for: The owner can find all three and explain the next action. This does not establish that a rollback or restoration was tested.
Where are the data, publishing controls and correction or help route? Which step needed assistance?
Make each check useful
Pick one journey and follow the same invented record from customer to owner and back. You can use this worksheet with any app builder, on your own or with a class. A missing setup step belongs under Not tested; a screen that looks finished is only the start of the check.
- Before you publish an AI app, try these real journeys →
- Write acceptance criteria an AI app builder can be judged against →
- Test app permissions with two users and a direct link →
- Run a customer-journey demo that tests the app's real work →