<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Indie Need</title>
    <description>The latest articles on DEV Community by Indie Need (@indieneed).</description>
    <link>https://dev.to/indieneed</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4231536%2F53461d59-fbc7-405e-97d8-0d246f051fcd.jpg</url>
      <title>DEV Community: Indie Need</title>
      <link>https://dev.to/indieneed</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/indieneed"/>
    <language>en</language>
    <item>
      <title>The launch-readiness checks behind IndieNeed's review process</title>
      <dc:creator>Indie Need</dc:creator>
      <pubDate>Sat, 07 Nov 2026 06:10:23 +0000</pubDate>
      <link>https://dev.to/indieneed/a-launch-readiness-checklist-for-show-hn-and-developer-communities-1eai</link>
      <guid>https://dev.to/indieneed/a-launch-readiness-checklist-for-show-hn-and-developer-communities-1eai</guid>
      <description>&lt;p&gt;IndieNeed is a small launch site for indie makers. Free listings are reviewed by a person before they go live.&lt;/p&gt;

&lt;p&gt;As of November 7, 2026, the site had 702 products live, 112 scheduled and 54 rejected all-time. We haven't published an analysis of why each rejection happened, so this post doesn't guess. It sets out the rules a listing is checked against, which are public, and the practical check each one implies for any launch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It must not deceive or harm.&lt;/strong&gt; IndieNeed's content policy rules out malware, phishing, scams, products "designed to deceive or defraud", IP or privacy infringement, and hate or harassment. Practical check: your landing page should say plainly what the product does and what data it collects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Regulated claims need care.&lt;/strong&gt; Products in finance, health or security "must be described accurately and must not make unsupported claims." Practical check: remove any number or guarantee you can't show evidence for.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A relaunch needs a real change.&lt;/strong&gt; A product can launch again for meaningful updates, but "repeated launches with no real change are not allowed." Practical check: before a relaunch, write one sentence on what's actually new.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Votes must be earned.&lt;/strong&gt; Makers may tell their audience they launched, but "may not buy, trade, or incentivise votes"; attempts to game votes or reviews remove the launch from ranking. Practical check: share the launch without buying, trading or incentivising votes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Be there on launch day.&lt;/strong&gt; The guidelines ask makers to "be present to answer questions" and to keep the listing accurate. Practical check: block an hour after going live for replies.&lt;/p&gt;

&lt;p&gt;Which of these do you find hardest to get right before a launch?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This post was drafted with AI assistance from IndieNeed's published policies and a database count, then checked against those sources. Sources: indieneed.com/legal/content-policy and indieneed.com/legal/launch-guidelines.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>indiehackers</category>
      <category>startup</category>
      <category>webdev</category>
      <category>sideprojects</category>
    </item>
  </channel>
</rss>
