I've been giving this thought here and there. I was planning on making a decision by the end of the year but I guess I can expedite the decision.
Below are some very disorganized thoughts I have. I will reply later when I'm more available or make a separate post later today maybe.
So I think I am more ok with open sourcing the project (however it will not accept PRs), but there are some action items I need to get done before I can get there. There is also competing priorities between these three projects:
- Implement a sharing system that allow users to share their app settings with others to make setup easier. Also offer some default setting templates.
- Implement more user requests.
- Open sourcing the app.
As for action items, the main one I need to get done is to replace Firebase. So I did some research a few days ago on this and unfortunately there doesn't appear to be any FOSS alternatives to Crashlytics which is unfortunately. However, my thoughts here is that I should still move away from Crashlytics because it's reliant on Google Play Services and the community seems pretty divided on it.
I could also just open source the app and ask questions later. I need more time to gather my thoughts.
P.S. I had a twisted joke idea to announce that I was going to open source the app on April 1st (April fool's day) and then actually open source it on April 2nd.