[itsnoone]

The developer here- I didn't plan to release an app for android, or even linux. The android app just started out as a personal project. My plan was to make a service for linux that can talk to various headphones, and any UI can talk to the service. And this was supposed to be under AGPL. But, as I graudally reverse-engineered most of the protocol from the bluetooth stack on macOS, I decided to release the app for Android and make one for linux as well.

Going to change it to GPL, though. never paid attention to the license in use as I developed.

[throwaway2037]

Thanks for the direct reply. I didn't consider the SaaS angle when I wrote my original post. As a result, your initial license choice makes sense. Also, if you are in control of copyright for all of the source code, then you can easily change the license. I am still blown away by how you did it. It must have been a lot of reverse engineering! Hats off -- keep up the good work.