It's the desktop apps (other pedias) that make Amazon important. We want people to be able to *reliably* find information from the pedias using the Desktop apps. Right now, hate to say this, the most reliable and complete API out there is Amazon's. IMDb is great, but is not as complete and realiable as Amazon and makes changes to their site quite often, resulting in a support nightmare because each time something changes requires a new build (hence a new version) of the application. And it gets confusing really fast: "which beta of *pedia are we on now?"
Imagine if we multiply that times the number of other sites. DVDpedia right now has a number of sites it can extract data from, but my guess is Amazon is the one used by most users.
The tinkerers and hackers amongst us wouldn't mind fiddling with sites and adding things manually, but the truth is that the average user (as far as such a creature exists) just wants the software to work out of the box and find their entries. Right now that is done via Amazon searches (for the most part).
Bruji is a very small company, the time involved in just supporting many different smaller search sites means time away from development, from making the changes our customers want and from evolving the products to constantly make them better. It's a fine line between support and development.
In response to making Pocketpedia open source, that won't solve the Amazon issue. I'm not the developer, so Conor might have other things to say on the subject (always consult with the boss), but it doesn't matter if your app is open source or not, you still cannot infringe the Amazon policy. I know what you're saying: making it open source means that Bruji cannot get penalized on the desktop side of things because we didn't develop it and we have nothing to do with the App. But then that means we lose the ability to edit it and troubleshoot and support it and make sure it's actually useful to our customers. We end up with a "plugin" that might or might not work, or we end up heading the development of the app, hence infringing Amazon policy and now we multiply our development time by a factor of however many other developers are working on this app, making sure that our changes don't break theirs, etc.
Honestly, I don't know what the solution is and, again, I'm not the developer, I'm just the hired help (more like a glorified maid really
, so whatever I say here, take it with a grain of salt. We are looking into solutions to this, but making an Amazon-free version might be the way to go in the future. And, while I'm ranting, I'll also say that we're a bit put off by having thrown all our hard work and effort down the toilet not once, but twice, due to Amazon's inexplicable policy.
But fear not, we love Pocketpedia...