Dispatch for Mac App Store research and launch workflow — Dispatch turns App Store research and launch work into a visible workflow we can explain and improve.

Most indie app updates disappear into the store because the maker announces a version number instead of a result. You do not need a large audience to test a better approach. You need one specific job, one proof asset, and one place where people are already discussing that job.

1. Name the job, not the version

Start with the user’s before-and-after. “Dispatch 1.5.12 is out” is a label. “Check your listing before you spend another week guessing which screenshot or keyword is holding it back” is a reason to care. Keep the version number in the details, not the headline.

2. Make one proof asset

Use a screenshot, a short screen recording, or a before/after listing line. The asset should answer one question in a few seconds. A polished image is useful, but a real workflow is more credible than a decorative announcement.

A small launch template

Problem → change → proof → question.

Tell people what was difficult, what changed, show the part they can verify, then ask one question that invites a useful reply.

3. Publish the explanation where it can compound

Put the durable version on your own site. Link the release recap from the product page, the blog index, and the relevant guide. That gives searchers a page that explains the change after the social post is gone.

Our Dispatch release recap and App Store checklist are examples. They are useful even to someone who never buys Dispatch.

4. Share one helpful answer

Choose a discussion about the problem, not a generic launch thread. Answer the question first. If the explanation on your site genuinely adds detail, include one link. A quiet, relevant contribution is more durable than posting the same announcement everywhere.

5. Measure the next decision

Use a tagged URL for each place you share the recap. Count pageviews as attention, product-page actions as intent, and paid orders as revenue. Do not combine them into one flattering number. The next update should repeat the channel that produced the strongest evidence, not the one that produced the most likes.

Our current loop

Dispatch Kun is live on the App Store, and the Mac product has a decision page that gives visitors three clear paths: the Mac toolkit, the free iPhone companion, or the launch checklist. Rank follows the same pattern with its public workflow demo and weekly growth log.

The goal is not to make every update go viral. It is to make every update teach us something about the people who might buy the next one.