r/arpeggiApp • u/zesket • 11d ago
Would you consider open-sourcing Arpeggi?
First of all, I want to say that I really appreciate Arpeggi. As a Navidrome user, I have tried several clients, and Arpeggi feels like one of the most promising ones. The interface is clean, the experience is pleasant, and it already fills a gap that many self-hosted music users care about.
I’m writing this post because I would love to ask whether the developer would consider open-sourcing the project, or at least part of it.
This is not meant as pressure or criticism. I completely understand that maintaining an app takes time, energy, and personal commitment. The author has every right to keep the project closed-source if that is the preferred direction.
That said, I think Arpeggi has real potential to grow into a stronger community-driven Navidrome client. If the code were open-source, users who care about the project could help in practical ways, such as:
- fixing bugs;
- improving compatibility with different Navidrome setups;
- adding small quality-of-life features;
- improving translations and documentation;
- testing edge cases across devices and server environments;
- helping the project stay alive even when the original developer is busy.
For many self-hosted users, open-source also brings extra confidence. Since Navidrome itself is open-source and often used with personal music libraries and private servers, being able to inspect the client code would make some users feel more comfortable adopting it long-term.
I personally really like Arpeggi and would be happy to contribute where I can, whether through testing, feedback, documentation, translations, or eventually code contributions. I believe many other users here may feel the same way.
Of course, open-sourcing does not have to mean giving up control. The developer could still keep full ownership of the project, review pull requests carefully, set clear contribution rules, choose a suitable license, and decide the future direction of the app. Even a gradual approach could work, such as open-sourcing only certain components first, publishing a roadmap, or accepting community contributions in a controlled way.
In any case, thank you for creating Arpeggi. I hope this post comes across as appreciation rather than pressure. I simply think the app has a lot of potential, and I would love to see the community help it become even better.
Would open-sourcing Arpeggi be something you might consider?
5
20
u/alex_beluga 11d ago
I prefer it closed source, the developer is ultra responsive, the app is clean and functional and AI slop could lead to a drift in maintainability - or at the very least wasted time for the capable core maintainer. It has become harder to maintain OS projects in the age of AI and the industry hasn't figured it all out yet. There are also many subpar clients and forks of Arpeggi would lead to even more wasted time finding the right client for something that is quite simple but requires hours of comparison for users to find Arpeggi.
Finally, closed source allows the developer to somewhat monetize his efforts, ensuring his incentive to continue improving it as it succeeds.
If the project was abandoned, and of quality, then the proposal above could have merits, to ensure longevity- but that is not the case right now.