Players want to play games today, not tomorrow.
Obviously us devs want to provide builds to players as soon as possible. The later we are in delivering builds or updates, the higher the risk of losing (potential) players. There's a huge checklist when you are about to deploy a game build, some things might just get missed!
Solution? Automate some/most of the steps, by setting up a CI/CD pipeline that eases your checklist tasks to a few, making sure you don't forget key tasks, and don't tire yourself repeating the same things.
Challenges when you're a broke indie dev?
I ain't broke. Not yet at least 😅. But if I am pushing only a few updates a month, it doesn't make sense to pay for things like Unity's Cloud Build, GitHub Actions, or other alternatives. Plus, Unity's license ToS is something to worry about. I don't want to get my account or organization banned. Especially after the install fees debacle, can't trust they won't pursue for using a personal license on a Github Action runner or a Gitlab runner.
Read my approach for solving the issue here.
Top comments (0)