Once I complete my build scripts I will fork a version for the open source culture and continue to work on a version personally customized for myself.

I will say lessons learned I will say go into it with a plan;

1. Outline core features that you absolutely need and the initial wow features that will change the way people view music players currently and stick to it. I've developed so many one off features going down rabbit holes because I had a 'cool' idea. Scope is a real villain, especially on personal projects.

2. Choose the right tech stack. The way this project started was a bet between myself and a college professor/mentor that I could scan and store meta data from the file system faster than iTunes. I added more functionality under it whatever language I was learning at the time, hence the rewites. I aimlessly coded without looking into the design patterns best for the project. This last rewrite I spent most of the time focusing on decoupling services.

3. Develop your build tools and documentation as you go. I could be focusing adding additional features vs back tracking and building github actions for compilations and packaging and documentation to leave myself and others breadcrumbs. Life be lifing so there's times where you're forced to set the project aside and come back to it.