Browse by category
All categoriesBrowse by platform
All platformsResources
Latest postsFree tool
Answer five questions and get a dated app launch checklist: what to do in the weeks before, what to do on the day, and the follow-up almost everyone skips. No account, no email.
What you get
Every item lands on a real date counted back from the launch you picked, and only the items that apply to what you are shipping appear at all.
An iOS launch gets the App Store review window, the 6.9 inch screenshot set and the 100 character keyword field. An Android launch gets the closed test Google requires before production access opens. A browser extension gets the Chrome Web Store review lead time, which is the longest pole in most extension launches. A command line tool gets registry publishing and a README rewritten around the first 60 seconds.
Pre-launch is where launches quietly fail, usually by running out of runway on a store review. Launch day is a short list with no build tasks on it. Post-launch is the part almost everyone skips, and it is the reason some products get a second week of traffic and most do not.
Download the plan as Markdown to paste into your issue tracker, or as a calendar file where every dated item becomes an all-day event in the calendar you already use. Both are built in your browser from the plan on this page.
Method
You give it five things: the platforms you ship on, your category, the date you want to launch, whether the app is free or paid, and whether you already have an audience. Nothing else, and no account.
The bank behind it holds 99 items. Each one carries a lead time in days, and each one is conditional, so an iOS launch gets App Store review and screenshot sizes, a browser extension gets the Chrome Web Store review window, a command line tool gets registry publishing and a README rewrite, and a developer tools app gets a Show HN. Paid apps get the payment and refund items; apps launching without an audience get the two weeks of community work that has to happen first.
Every item is dated backwards from your launch day, in order, so the plan is a calendar rather than a pile of advice. When the launch date is close enough that an item would land in the past, it is pulled forward to today and flagged, because a short runway is a real constraint and hiding it does not help.
The result lives at a permanent link. Send it to a co-founder, paste it into a thread when you ask for launch advice, or download it as Markdown for your issue tracker and as a calendar file where every dated item becomes an all-day event.
