Build with AI: From Zero to Your First App · Module 8: Finish, publish and present
Run the Pre-Release Checklist
Launch day is a checklist, not a feeling. This lesson runs content, layout, behavior, storage, safety and wording checks, then signs with date and snapshot.
11 min reading
Objectives
- Run the full pre-release checklist on a real project
- Verify content, layout, behavior, storage, safety and words
- Fix findings singly with re-runs, never batched
- Sign the checklist with date and snapshot name
Why this matters
Skipped checks become user-facing bugs within hours: wrong hours published, overflow on the owner's phone, echo broken, entries lost, a real phone number in a screenshot. The checklist converts hope into evidence across six areas in under an hour. Signing it (date plus snapshot name) makes the release a fact rather than a mood.
Concepts
The six areas. Content: every section true against the brief, no placeholder text, hours and prices current. Layout: two-width test passed, labels visible, button reachable. Behavior: routine from M07L27 green (normal, edge, invalid, old features). Storage: reload persistence, delete works, limits line visible. Safety: no secrets, no personal data, screenshots cropped (M01L4 sweep). Words: README states what it is, limits, AI contribution honestly (lesson M08L32 extends this).
Findings singly. Each failing line becomes one single-change fix with a re-run of its area plus the neighboring areas. Batching pre-release fixes repeats the M06L21 chaos at the worst moment. Small, verified, signed.
Sign with date and snapshot. "Released 2026-10-07 from snapshot folder-2026-10-07-pre-release." Rollback named, moment recorded. Future-you thanks present-you when the first user report arrives.
Worked example
Bakery release run: content (hours verified against the shop door: pass), layout (360px pass, desktop pass), behavior (routine green), storage (reload pass, corrupt test pass), safety (sweep: one real phone in an old screenshot, replaced with the cropped table-only image), words (README honest). One finding fixed singly (screenshot replaced), areas re-run, signed with date and snapshot. Launch took fifty minutes; the first week took zero apologies.
Expected result: your signed checklist with six areas checked, findings fixed singly, date plus snapshot recorded.
The common wrong move
"Looks good, ship it" after eyeballing one desktop width. Eyeballing tests rendering on one machine; checklists test behavior on every visitor's terms.
Lab and next step
Lab A24 runs the checklist on your project with findings log. Next, lesson 32 writes the README that presents the work honestly, including the AI contribution.
Quick check
An optional 4-question self-check. Answers never leave your device, are not stored, and never count toward any assessment.
Lesson feedback
No published feedback yet.
Log in and complete the lesson to leave feedback.
Exercise
Run the six-area checklist on your project. Log each line pass or fail; fix findings singly with re-runs; sign with date and snapshot name.
Pass criteria
Six areas checked with per-line results; findings fixed singly with re-runs recorded; signature line with date plus snapshot present.