The App Launch Checklist: 47 Things Before You Ship

You built the app. It works on your device. You are ready to ship. But are you actually ready? After watching dozens of app launches, we have compiled the 47 things that matter most. Skip any of these and you risk a rejected submission, a bad first impression, or a silent launch that nobody notices.

Print this list. Check every item. Then ship with confidence.

## App Store Preparation (Items 1-12)

**1. Apple Developer Program membership ($99/year).** You cannot submit without it. Sign up at least a week before launch because approval can take 48 hours.

**2. Google Play Developer account ($25 one-time).** Same deal. Set it up early.

**3. App Store Connect: create your app listing.** Fill in the app name, bundle ID, primary language, and primary category.

**4. Google Play Console: create your app.** Set up the store listing with the correct package name.

**5. Privacy policy URL.** Both stores require it. Host it on your website. Include what data you collect, how you use it, and how users can request deletion.

**6. App icons.** iOS requires a 1024x1024 icon (no alpha channel, no rounded corners). Android requires adaptive icons (foreground layer + background layer). Test how they look at small sizes.

**7. Screenshots.** iOS: at least 3 screenshots for each required device size (6.7" and 6.1" at minimum, 6.9" recommended). Android: at least 4 screenshots. Make them count. Show the app in use with descriptive captions.

**8. App preview video (optional but recommended).** A 15-30 second video showing the app in action. This increases conversion rates significantly on the App Store.

**9. Keywords field (iOS).** 100 characters of comma-separated keywords. No spaces. No duplicates of words in your title. Research competitors and find gaps.

**10. Short description (Android).** 80 characters. Include your primary keyword and core benefit.

**11. Full description.** Write for humans. Lead with the benefit, not features. Use bullet points for scannability.

**12. Content rating questionnaire.** Both stores require it. Answer honestly. Getting this wrong can delay your review.

## Technical Readiness (Items 13-25)

**13. Test on real devices.** Simulators miss performance issues, gesture bugs, and hardware-specific problems. Test on at least one physical iOS and one physical Android device.

**14. Test the full user flow.** Sign up, complete onboarding, use every core feature, make a purchase, log out, log back in. Do this end-to-end without shortcuts.

**15. Test on slow networks.** Turn on airplane mode. Turn it off. Switch between WiFi and cellular. Your app should handle network transitions gracefully with loading states and error messages, not crashes.

**16. Test with no data.** New users start with empty states. Every list, every dashboard, every profile should have a meaningful empty state that tells users what to do next.

**17. Error handling.** Try to break things. Enter invalid data. Tap buttons rapidly. Rotate the device. Dismiss the keyboard. Every error should show a user-friendly message, not a crash.

**18. Deep links work.** If you use deep linking for auth callbacks, email verification, or shared content, test every deep link path on both platforms.

**19. Push notification permissions.** Test the permission prompt timing. Test that notifications arrive. Test notification tap behavior (does it open the right screen?).

**20. In-app purchase flow.** Test the complete purchase flow in sandbox/test mode. Verify that premium features unlock after purchase. Test restoring purchases on a fresh install.

**21. Analytics events fire.** Check that your key events (signup, onboarding complete, feature usage, purchase) are being captured correctly in PostHog or your analytics tool.

**22. Crash reporting enabled.** Sentry, Bugsnag, or a similar tool should be configured and receiving test events. You need to know about crashes before your users report them.

**23. Performance audit.** Check app startup time (should be under 3 seconds). Check scroll performance (should maintain 60fps). Check memory usage (should not climb indefinitely).

**24. Accessibility basics.** Screen reader labels on buttons and images. Sufficient color contrast. Touch targets at least 44x44 points. These are not optional. They affect real users and app store reviews.

**25. Remove all debug code.** console.log statements, test credentials, development URLs, debug menus. Search your codebase for TODO and FIXME comments.

## Backend and Security (Items 26-33)

**26. Production environment configured.** Separate from development. Different database, different API keys, different analytics project.

**27. Row-Level Security enabled.** If using Supabase, verify that RLS policies are active on every table. Test that users cannot access other users' data.

**28. API rate limiting.** Prevent abuse. Rate limit authentication endpoints especially (5-10 attempts per minute per IP).

**29. Input validation.** Server-side validation on all user inputs. Never trust the client. Check for SQL injection, XSS, and oversized payloads.

**30. Database indexes.** Add indexes on columns used in WHERE clauses and JOINs. Missing indexes are fine with 10 users but cause timeouts at 10,000.

**31. Backup strategy.** Automated daily backups of your database. Test restoring from a backup at least once before launch.

**32. SSL/TLS everywhere.** All API calls over HTTPS. No exceptions.

**33. Secrets management.** No API keys in source code. Environment variables or a secrets manager for all credentials.

## Monetization (Items 34-38)

**34. RevenueCat (or equivalent) configured.** Products created in App Store Connect and Google Play Console. Entitlements mapped. Offerings configured.

**35. Paywall tested end-to-end.** In sandbox mode, test monthly subscription, annual subscription, restore purchases, and cancellation.

**36. Receipt validation.** Server-side receipt validation if applicable. Do not trust client-side purchase confirmation alone for premium features.

**37. Pricing displayed clearly.** Show prices in local currency. Show what is included in each tier. No hidden costs or surprise charges.

**38. Subscription terms visible.** Both stores require clear disclosure of subscription terms (auto-renewal, cancellation policy) near the purchase button.

## Marketing and Launch (Items 39-47)

**39. Landing page live.** A page on your website that describes the app and links to the store listings. This is where you send traffic from social media, press, and ads.

**40. Social media accounts created.** At minimum, a Twitter/X account for the app. Post a few times before launch so the account does not look brand new.

**41. Launch day content prepared.** Product Hunt listing drafted. Reddit post written. Twitter thread outlined. Do not write these on launch day.

**42. Email list (if you have one).** Draft the launch email. Include screenshots, a clear call to action, and download links for both platforms.

**43. Press kit ready.** App icon, screenshots, a one-paragraph description, and your contact info in a folder. Journalists and bloggers need these assets.

**44. Support channel established.** An email address at minimum. A way for users to report bugs and request features. Respond within 24 hours.

**45. Feedback mechanism in-app.** A "Send Feedback" button in settings that opens an email compose or a feedback form. Make it easy for users to tell you what is wrong.

**46. App store review prompt configured.** Trigger the rating prompt after a positive user action (completing a task, achieving a streak). Not on first launch. Not during a critical flow.

**47. Launch date set and shared.** Tell someone. Tell your email list. Tell Twitter. A public commitment creates accountability and builds anticipation.

## After you ship

The checklist does not end at launch. Within the first week, watch your crash reports, respond to every review, check your analytics funnels, and talk to your first users. The data from week one shapes your roadmap for the next three months.

Our [growth engine](/features/growth) automates many of the marketing items on this list, from ASO metadata to launch content generation. But the technical and security items require hands-on attention regardless of how you build your app. Check out our [pricing plans](/pricing) to see what is included for launch support.

Ship when the checklist is clear. Not when the app is perfect. Perfect does not exist. Ready does. Check the boxes and launch.