I built this game mostly alone. Here's what I learned about sustainable solo dev.
The Reality of Solo Development
The Ascendant Continuum is a solo project built directly by me. No outsourcing and no paid external production team. Solo development requires strict prioritization: not every idea ships, so I focus on the highest-impact work first. Many planned features are intentionally cut so the core experience stays coherent and finishable.
Tools and Automation for Efficiency
Automation saves solo devs from drowning in busywork. I use GitHub Actions for build automation (push to main triggers WebGL, Android, and iOS builds), Firebase hosting for zero-config deployment, automated testing via Unity Test Framework, and automated social media posting (this blog, daily social updates). These systems let me focus on high-value creative work instead of repetitive tasks. Initial automation setup took 40 hours; it's saved 200+ hours since. For solo devs, automation multiplies your effective team size.
Preventing Burnout Through Sustainable Practices
Solo dev is marathon, not sprint. I track time strictly: 25 hours/week maximum, never weekends, mandatory 1-week vacation every 8 weeks whether I feel I need it or not. I use Pomodoro technique (25-min work, 5-min break) to prevent hyperfocus burnout. I maintain separate hobby projects (not games—woodworking, painting) to prevent creative depletion. I've declined partnerships and funding that would require unsustainable crunch. The game will take longer this way, but it'll actually ship. Most solo projects fail from burnout, not technical challenges.
DIY Scope and Constraints
Working solo means accepting tradeoffs. I choose techniques, assets, and workflows I can personally maintain over the long term. That means avoiding scope that would require external paid help, and focusing on systems I can actually ship and support. The priority is reliability and continuity, not chasing maximum complexity.