<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Senommu’s Notes]]></title><description><![CDATA[Personal notes by senommu on building software, launching side projects, and finding customers. Practical lessons from developing and growing my own products.]]></description><link>https://senommu.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6a633ff8592abc2969fd5dc5/f7d495a4-6bbf-4758-a4ce-80428f2851c5.png</url><title>Senommu’s Notes</title><link>https://senommu.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 17:43:32 GMT</lastBuildDate><atom:link href="https://senommu.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[A developer’s checklist for launching a side project]]></title><description><![CDATA[A practical checklist for launching your side project: choose relevant platforms, prepare your submission, track visits, and learn from real feedback.]]></description><link>https://senommu.hashnode.dev/side-project-launch-checklist</link><guid isPermaLink="true">https://senommu.hashnode.dev/side-project-launch-checklist</guid><category><![CDATA[side project]]></category><category><![CDATA[Web Development]]></category><category><![CDATA[startup]]></category><category><![CDATA[marketing]]></category><category><![CDATA[Product launch]]></category><dc:creator><![CDATA[senommu]]></dc:creator><pubDate>Wed, 18 Nov 2026 10:21:23 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a633ff8592abc2969fd5dc5/91b5ea17-a865-4b36-a516-8560bcdc18f6.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>You’ve deployed your side project. Authentication works, the main feature is usable, and the landing page is live.</p>
<p>Now you need to put it in front of people who might use it.</p>
<p>I’m at this stage with llaunch, a product launch platform I’m building. It also includes Directories, a paid database of places to launch and promote products.</p>
<p>While preparing my own distribution, I’ve been putting together a repeatable process for choosing channels, preparing submissions, and recording what happens.</p>
<p>Here’s the checklist I’m using.</p>
<h2>1. Check the journey from a stranger’s perspective</h2>
<p>Before sharing your URL, walk through the experience without relying on what you already know about the project.</p>
<p>Start in a logged-out session and check:</p>
<ul>
<li>Can someone understand the main use case from the landing page?</li>
<li>Can they see an example, preview, or demo?</li>
<li>Is it clear what is free and what requires payment?</li>
<li>Does the primary action work?</li>
<li>If they get stuck, can they find a way to contact you?</li>
</ul>
<p>Then try one complete journey: landing page → signup → first useful action.</p>
<p>For a paid product, check the purchase flow as well.</p>
<p>The goal is to catch issues that would prevent someone from evaluating the project after you’ve earned their attention.</p>
<h2>2. Write down who needs it and when</h2>
<p>Use a sentence with a person, a task, and a situation:</p>
<blockquote>
<p>This project helps [person] do [task] when [situation].</p>
</blockquote>
<p>For example:</p>
<blockquote>
<p>This tool helps developers notice failed background jobs when they’re running a small app without a dedicated operations team.</p>
</blockquote>
<p>That description gives you something specific to look for: discussions about scheduled tasks, deployment reliability, and maintaining small applications.</p>
<p>For my directory database, I’m looking for founders who have a working product and are deciding where to promote it.</p>
<p>Keep this sentence next to your channel shortlist. Use it when deciding whether a platform’s audience is relevant.</p>
<h2>3. Choose a format for each channel</h2>
<p>A product listing, a tutorial, and a community discussion require different material.</p>
<p>Imagine you’re launching the background-job monitoring tool from the example above.</p>
<h3>Product listing</h3>
<p>Explain what it monitors, how alerts work, what setup requires, and how much it costs.</p>
<p>Include a demo or screenshots that help someone understand the workflow.</p>
<h3>Technical article</h3>
<p>Walk through a problem readers can solve.</p>
<p>For example: detecting a missed scheduled job, deciding when to send an alert, and avoiding duplicate notifications.</p>
<p>Include enough detail for readers to apply the ideas themselves.</p>
<h3>Community discussion</h3>
<p>Share a specific problem or implementation decision and invite relevant feedback.</p>
<p>For example:</p>
<blockquote>
<p>How long do you wait before treating a scheduled job as missed? I’m working on alert thresholds and would like to understand how others handle jobs with variable runtimes.</p>
</blockquote>
<p>Ask a question you actually need answered, and explain your connection to the project.</p>
<h3>Answer to an existing question</h3>
<p>Address the person’s setup and constraints first.</p>
<p>Mention your project if it helps answer the question, with a clear disclosure that you built it. The answer should still be useful if they never open your link.</p>
<h2>4. Read the requirements before preparing a submission</h2>
<p>For every candidate platform, record:</p>
<ul>
<li>Accepted project types</li>
<li>Rules on product promotion</li>
<li>Account requirements</li>
<li>Submission price</li>
<li>Review process or queue</li>
<li>Required images, text, badges, or backlinks</li>
</ul>
<p>Save the source URL and the date you checked it.</p>
<p>This avoids preparing a launch for a platform that doesn’t accept your project or requires something you haven’t budgeted for.</p>
<p>It also makes “free” more useful as a planning label. A submission might cost no money while still requiring a badge, an editorial review, or time spent participating in a community.</p>
<h2>5. Prepare a small launch kit</h2>
<p>Keep the core product information in one document:</p>
<ul>
<li>Product name and URL</li>
<li>One-sentence description</li>
<li>Short description</li>
<li>Intended user and use case</li>
<li>Current pricing</li>
<li>Demo or preview URL</li>
<li>Logo and product images</li>
<li>Contact details</li>
</ul>
<p>Use this as the factual source for each submission. Adapt the final text to the platform.</p>
<p>For an article, lead with what the reader can learn. For a product page, make the workflow and offer easy to understand.</p>
<p>Check that descriptions and pricing remain consistent across both.</p>
<h2>6. Start with a batch you can follow up on</h2>
<p>I’ve selected five platforms for my first round.</p>
<p>That gives me enough room to prepare each publication and respond afterward. I can also make changes between submissions if early feedback exposes an unclear explanation.</p>
<p>For each platform, I want to know:</p>
<ol>
<li>Why is this audience relevant?</li>
<li>What am I publishing?</li>
<li>What do I hope to learn?</li>
<li>When will I review the result?</li>
</ol>
<p>A useful outcome might be a purchase, a signup, or a conversation that reveals why someone wouldn’t use the product.</p>
<p>Write down which outcome matters for the experiment before publishing.</p>
<h2>7. Keep a lightweight distribution log</h2>
<p>A spreadsheet or Markdown table is enough to start:</p>
<table>
<thead>
<tr>
<th>Field</th>
<th>What to record</th>
</tr>
</thead>
<tbody><tr>
<td>Channel</td>
<td>Platform or community</td>
</tr>
<tr>
<td>Publication URL</td>
<td>Direct link to the post or listing</td>
</tr>
<tr>
<td>Date</td>
<td>When it went live</td>
</tr>
<tr>
<td>Format</td>
<td>Listing, article, discussion, or answer</td>
</tr>
<tr>
<td>Time spent</td>
<td>Preparation and follow-up</td>
</tr>
<tr>
<td>Visits</td>
<td>Website traffic you can attribute</td>
</tr>
<tr>
<td>Conversions</td>
<td>Relevant signups or purchases</td>
</tr>
<tr>
<td>Feedback</td>
<td>Questions, objections, and suggestions</td>
</tr>
<tr>
<td>Next action</td>
<td>Repeat, revise, investigate, or stop</td>
</tr>
</tbody></table>
<p>Where the platform permits it, use a distinct campaign URL:</p>
<pre><code class="language-plaintext">https://example.com/?utm_source=hashnode&amp;utm_medium=article&amp;utm_campaign=first_launch
</code></pre>
<p>Verify that your analytics captures the parameters.</p>
<p>A tagged visit doesn’t automatically give you purchase attribution. Depending on your setup, you may need to preserve the source through signup or checkout.</p>
<p>Keep the limits of your measurement visible when comparing results.</p>
<h2>8. Review the questions as well as the numbers</h2>
<p>After each publication, look at what people needed you to explain.</p>
<p>Repeated questions can point to changes worth making:</p>
<ul>
<li>“Who is this for?” may mean the audience is unclear.</li>
<li>“Can I try it?” may mean you need a better preview.</li>
<li>“How is this different?” may mean the existing workflow needs more explanation.</li>
<li>“Does it support my setup?” may reveal a missing compatibility detail.</li>
</ul>
<p>Record the actual question before interpreting it. One comment is a lead to investigate; several similar comments give you more reason to act.</p>
<h2>How I’m using this checklist</h2>
<p>I’m applying this process to <a href="https://llaunch.dev/directories">llaunch Directories</a>, my database of places to launch and promote products.</p>
<p>Disclosure: I’m the maker. Access costs $19 once for lifetime access, including future updates. The page includes free examples.</p>
<p>I’m using it to build my own shortlist, then checking each platform’s requirements and preparing material for its audience.</p>
<p>I don’t have conversion results from this campaign yet. My first goal is to complete the initial batch and collect enough evidence to choose the next one.</p>
<p>If you’re preparing to share a side project, you can use the checklist above with a shortlist of your own.</p>
<p>What did you discover after putting your last project in front of people outside your usual circle?</p>
]]></content:encoded></item></channel></rss>