The Vibe Coding Diaries: š Ready to Launch
The eighth, ninth and tenth hour
2nd Night 3rd to 5th Hour - The Pre-Launch Checklist
Itās 11:12 PM and Iām doing the classic pre-launch dance: one tab for my app, one for my notes, one for a rapidly cooling cup of tea. Iām kidding, of course, I have hundreds of tabs open by now. š
The birthday planner is getting ready for the showdown, but before I call it ādone,ā Iām walking through myā¦
The Pre-Launch Checklist
š§½ Polish the Look & Experience.
We have done this already.
š± Make It Mobile-Friendly.
Because if it breaks on mobile, itās broken.
Prompt to try:
āCheck all pages for mobile responsiveness issues.
List:
- Elements that donāt resize correctly
- Text that overflows
Suggest fixes and update the code.ā
šŖŖ Finalise Authentication.
Nothing like asking a friend to test your app and realising the login doesnāt work.
Prompt to try:
āReview the appās current authentication system for security issues.
Check for:
- Client-side route protection (redirect if not logged in)
- Server-side token/session verification
- Secure password storage and handling
- Any outdated or unsafe methods
Suggest improvements and, if possible, implement updated code that meets current secure authentication standards.ā
š Hide Your Secrets.
You donāt want strangers (or bots) racking up your bill, breaking your app, or sneaking into your usersā data, do you?
Prompt to try:
āScan my codebase for any hardcoded API keys, secrets, or tokens.
If found:
- Replace with environment variables in a .env file
- Update code to use process.env
- Confirm .env is in .gitignoreā
š¾ Back It Up.
If something breaks (a bad update, a deleted table, or a corrupted file), a backup is your safety net to restore your app without losing everything you built.
I always link my app to my GitHub repo. From here, I can download the entire codebase to my computer for safekeeping. GitHub is not just a backup, though; it lets me use different AI coding tools (Bolt, Cursor) to continue building the same app.
š Do a Launch Dry-Run.
Are you ready for real users?
Prompts to try:
āHelp me set up real-time error tracking and performance monitoring using [Sentry / PostHog].ā
āGenerate 5 short, friendly questions I can ask users about their experience using my app. Keep them conversational, not technical.ā
š I have an extra tip for you!
You donāt even need to use any Lovable credit for this, but updating your website info can turn your website from amateur to professional. š
Click on the Publish button and open the Website Info tab. By default, the logo and image used on social media and Google results are Lovableās. So before you publish, itās worth replacing these with your own branding.
Well, thatās it, folksā¦
Next, Iāll share what I created from the free 35 Lovable credits in 10 hours, along with some hiccups and learnings.





