Distribution log · App Store launch
Dispatch Kun is a mini-launch, not a silent release
Every release gives us a chance to explain one job, show the workflow, and invite the right person to try it.
July 21, 2026 · Michael at Yuzool
Publishing an app is not the same as launching it. An App Store listing can be live and still be invisible, misunderstood, or aimed at everyone in general. Dispatch Kun is now live on iPhone, so I am treating the release as a small distribution experiment rather than a one-day announcement.
Start with one job
The first explanation is intentionally narrow: Dispatch Kun helps a maker keep launch tasks, follow-ups and the next action visible when a release is already moving. That is more useful than saying it is a complete productivity system.
Launch card
One job. One link. One question.
Job: make launch work easier to act on from an iPhone.
Proof: a focused native app connected to the wider Dispatch workflow.
Question: which part of launch follow-up do makers keep losing after release day?
The mini-launch loop
The loop has four steps and can be repeated for every meaningful update:
- Explain the problem. Write the user situation before naming the feature.
- Show the smallest proof. Use one screenshot or a short recording that makes the job obvious.
- Ask a real question. Invite people to describe their current workaround, not just to click.
- Record what changed. Save the language, objections and click path before editing the listing.
This creates a useful distinction between attention and evidence. Views are encouraging, but the valuable signal is a person describing the problem in their own words or taking the next step toward trying the app.
What we are measuring
For this launch I am watching a small funnel:
- visits to the Dispatch page and launch recap
- App Store link clicks
- questions or replies that mention the job
- installs and purchases when the source can be identified
I am not treating a spike in impressions as product-market fit. If people click but do not understand the job, the next change belongs in the explanation or screenshot. If they understand it but do not need it, that is a positioning signal rather than a reason to post louder.
Different channels need different language
A launch post should not be copied unchanged into every community. A founder forum can handle the behind-the-scenes workflow. A productivity discussion may care about the moment after a launch when tasks become scattered. An App Store audience needs the job and the first screen immediately.
The link stays the same, but the opening sentence should answer the question already being discussed. That keeps the post useful even for people who never install Dispatch Kun.
What happens next
After the first conversations, I will update the App Store screenshots and the landing page only when the evidence points to a clearer promise. Then I will publish a short follow-up with the change and what happened after it. The aim is a trail of decisions that another indie developer can copy, not a sequence of empty launch announcements.