I think it's way too early for an API, and here's why:
- API's are generally only interesting if there are already some users, accounts, etc. to interact with.
- API's are not a main feature of the site (I could be wrong here of course) and are quite a way down the list. Fix the obvious problems first. I searched for Dire Straits and got no results.
- API's aren't used by a lot of people.
Basically what I'm saying is that you should get your priorities straight: An API has no value before the rest of your site works well, and has a lot of users.
Building your app on your on API or at least having your API always on your mind while planning your app is not a bad idea. It will definitely help you to get a well structured app. Might be difficult to squeeze it into you app afterwards.
Yep, I see what you mean that most usefulness to the most people is most important.
However, I'm not really too worried about artists missing from the index. I am building up the list of included artists very slowly because I only use information sources that I think provide useful recommendations. Thus, the artists that are pulled into the index is somewhat random. The comprehensiveness will grow over time.
- API's are generally only interesting if there are already some users, accounts, etc. to interact with.
- API's are not a main feature of the site (I could be wrong here of course) and are quite a way down the list. Fix the obvious problems first. I searched for Dire Straits and got no results.
- API's aren't used by a lot of people.
Basically what I'm saying is that you should get your priorities straight: An API has no value before the rest of your site works well, and has a lot of users.