A Launch Channel Order, and the Reasoning Behind Each Step

I wrote the launch plan for Photo Sweep as a sequence, not a list, and the distinction matters more than any individual piece of copy in it. The governing idea is one sentence: every channel after the first asks "who is already using this?" — and if the answer is nobody, the post underperforms no matter how well it's written.

Six steps, each one built on proof the previous step generated.

Step 1: the Nextcloud forum

This goes first because it's the highest-conversion audience available — people on help.nextcloud.com already run a Nextcloud server, which is the one prerequisite Photo Sweep can't work around. Nobody there needs convincing that self-hosting photos is worth doing.

The plan was to reply to everything for the first couple of days. Not because engagement metrics matter for their own sake, but because that thread becomes the proof every later channel points at. Without it, step 3 (Reddit) and step 6 (blogs) both lose their strongest argument.

Step 2: the GIF

Ten seconds, one loop — swipe, swipe, confirm. This sits second because nothing after it works as well without it: the forum post benefits from having it, but the Reddit post depends on it, since a body of text with no visual is a much harder sell to a subreddit's front page. Making the GIF is a one-time cost — one careful afternoon — that every subsequent channel reuses for free.

Step 3: Reddit — but not all at once

r/selfhosted first, because it's far larger and it's exactly the right crowd. r/NextCloud a day or two later, deliberately not the same day — cross-posting simultaneously reads as spam, and the plan explicitly calls that out as something to avoid.

The other discipline here: be present in the comments for the first few hours. On r/selfhosted specifically, a responsive author is most of the difference between a dead post and a front-page one. And the plan anticipates the obvious pushback — "why not just use X" — and answers it in advance, honestly: this is for deciding what to delete, not for organizing what you keep.

Step 4: Fediverse

Posted with #Nextcloud #selfhosted tags and the same GIF, now with alt text. This is placed after Reddit rather than before it for a specific reason: the Nextcloud account itself boosts community apps reasonably often, and their app-store people notice new listings — but that boost is worth more once there's already a forum thread and a Reddit post for it to amplify toward, not a launch with nothing behind it yet.

Step 5: awesome-selfhosted

A pull request adding one line to a list. This is the one channel in the sequence that isn't about generating attention in the moment — it's permanent, and it's where people go looking rather than being advertised at. It comes after the noisier channels because the effort here is following the list's formatting rules exactly, and that's worth doing once the app has already been publicly validated elsewhere, not before.

Step 6: tech blogs, last — on purpose

It's FOSS, MakeUseOf, XDA and similar outlets all want the same three things in a tip-line pitch: a working link, a screenshot, and a one-paragraph pitch. By the time this step runs, all three exist, plus something none of the first five channels gave for free: a forum thread proving someone other than the author has actually run the thing. Pitching a blog before that thread exists means pitching on your own word alone, which is a weaker pitch than the same words backed by a link to real users.

The reasoning that generalizes

Strip away the specifics and the order is really answering one question at each step: does this channel's audience trust the previous channel's audience? Forums trust nothing but their own experience, so they go first. Blogs trust evidence of adoption, so they go last. Everything in between is ordered by how much borrowed credibility it needs versus how much it generates.

Series: Launching Photo Sweep.