DEV Community

Indie Need
Indie Need

Posted on AI-assisted

What “scheduled” means on IndieNeed before a product goes live

IndieNeed is a small launch site for indie makers. A launch is tied to a specific day: the product is prepared ahead of time, then shown to the community on that date.

As of November 7, 2026, an evening read of IndieNeed’s launches table showed 702 products with status LIVE and 112 with status SCHEDULED. Those numbers are row counts by status. They do not measure traffic, interest, or how many of the scheduled products will stay live.

Choosing a date. IndieNeed’s published launch guidelines say makers choose a launch date, and that “Scheduled launches are reviewed and then go live automatically on that date.” For anyone building a release queue, that split matters: the intended calendar day is data, and “live for visitors” is a later state change driven by that day—not the same field.

Relaunches need a real change. The guidelines allow a product to hold new launches for meaningful updates, but “repeated launches with no real change are not allowed.” If you add relaunch support, gate it on a documented change, not only on booking another slot.

Presence still matters. On launch day the guidelines ask makers to be present to answer questions and to keep the listing accurate. Auto-publishing on a date solves the clock problem; it does not answer the comments.

If you are designing a similar board, keep three things explicit in the data model: the target date, the rule that moves a row to live, and the human work expected after it opens. The 112 scheduled rows are waiting on that clock, not on a vague “soon.”

Written with AI assistance using the sources linked above. Source: https://www.indieneed.com/legal/launch-guidelines

Top comments (1)

Collapse
 
alexshev profile image
Alex Shev •

The target date versus live state distinction is the important modeling boundary. I’d add an explicit transition receipt—scheduled job ID, evaluated-at time, rule version, and resulting state—so support can answer whether a launch was skipped, delayed, or blocked by review without inferring it from timestamps. That also makes automatic publication idempotent when the scheduler retries.