I am a huge fan of Beets and what it can do to organize a music library. As someone who has a massive music library and uses several streaming services to keep track of and discover music, I consider myself a great example of someone who would benefit from Beets (and I have). However, having used Beets for some time, I feel that beets is missing out on a huge opportunity.
There are two distinct challenges that users face as they curate and manage their own music libraries: 1) organizing (including tagging, organizing, etc.) and 2) discovery (recommending music to play).
Beets is very good at organizing the library (tagging, sorting) and that is how it “acquires users.” However, I feel that beets is not very good at discovery and that is a massive missed opportunity that beets can easily address. Currently, users do not benefit much from beets after the initial organization, i.e., there is no ongoing use for beets once the initial library is organized. Thus, they are likely to move on to other tools to benefit from their well-organized library.
It seems to me that this is low-hanging fruit for beets since it already has most of the information. Here are a couple of things that Beets could do that would keep users engaged even after the initial sorting:
1. Transfer and sync playlists: There is a great bit of interest in services that sync playlists across services (e.g., https://soundiiz.com/, https://songshift.com/, https://freeyourmusic.com/, https://musconv.com/). This is not surprising given that many of these services are great tools to discover music or play music. The number of new tools that have come up in this area is not surprising. Beets could definitely contribute to this area. A simple tool to transfer/sync playlists between a few services would be a great addition. I personally use Plex and Spotify and both of them are already included in Beets. I cannot imagine this being a difficult feature to implement.
2. Generate smart(er) playlists: Beets already does this to some extent, but the current approach does not incorporate the popularity of tracks/albums. There are several services that provide popularity information - Spotify, LastFM, Plex user ratings, etc. Including this popularity information in the beets database will significantly improve discovery.
I am not a programmer and I am not sure if these features are beyond the scope of what the devs have in mind for Beets, so feel free to ignore all of these if it is not relevant.