Hacker News new | past | comments | ask | show | jobs | submit login

The author has some relevant blog posts (in GitHub issues) too:

https://github.com/a327ex/blog/issues/35 - BYTEPATH Postmortem (2018)

https://github.com/a327ex/blog/issues/44 - One Year Sales Data for BYTEPATH (2019)




That's a very interesting way to use GitHub issues. I wonder what sort of problems can arise with vendor lock-in, though.


It's probably better to just make them Markdown inside the directory, you can export the Markdown files (since they're in git) but you can't export issues. Github renders both the same since, well, they're both Markdown.


I was not aware that Steam had changed their policy on sharing sales data. That is great! Are there any other indie devs that have shared the data about their Steam sales in a similar fashion? Better yet, is there a good list of links gathered somewhere for that?




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: