How do you know when it’s finally time to pull the plug on a dead side project?
by•
The graveyard of unfinished domains is the most relatable part of being a maker where buying a domain is easy but knowing when to let go is the real challenge. I have been pondering over my half-built apps this week because deleting months of late-night coding feels wrong yet keeping dead links feels misleading. The simple rule I set for myself is to shut down anything that hasn't made me excited to open the codebase in three months. This leaves my active list small keeping only the tools that truly matter. How do you choose whether to keep everything alive open-source the code or quietly pull the plug?
7 views
p/aperture-7
p/runevr
p/producthunt
p/google-cloud-platform
p/raycast
p/kuc-kuc
p/lasso-11
p/offiai
p/kodlo
p/ai-context-flow
p/many-displays
p/reso
p/dino-kids
p/dex-by-exmergo
p/htmldrag
p/jev
p/supabase
p/murror
p/nexupira
p/jot-2-0
Replies
Ours was decided by a dependency rather than by excitement. Our 2024 app generated songs through an unofficial wrapper around another company's service, and it broke when the wrapper did. We replaced it with a new app built on official APIs only, and kept the same bundle id so the existing store listing carried over to the new one. The old code sits in a private repo. Has one of your projects ever had the decision made for it from outside like that?