thye chean wrote:
This is the new century, my friend. An eBook should works like an app, which can be updated with new info, bug fixes, new features, etc.
You are preaching to the converted
But we are learning the hard way that that team probably consists of members coming from the real publishing industry working the old way.
Not sure about that. To me, it looks more like a completely disorganized process where everyone is running around like headless chicken and the left hand doesn't know what the right hand is doing. Apps with "iBook" in both the name and the description are approved in the App Store, while books with "iBook" somewhere in the text are refused in the iBookstore. Titles that are approved in the iBookstore and that are selling well are pulled without explanation when the author commits the unspeakable crime of updating the images to higher-resolution versions.
This is clearly a case of a system that is completely overwhelmed by demand, and had sub-standard people design the submission and review process. The problems reported here in this forum are clear evidence of that. Newly-minted graduates in business management could do better than this. (Every trouble-ticketing system I have ever seen will automatically send an email when an item in a workflow undergoes a state change. Heck, even the forum software we are all using here sends email when a thread I have contributed to is updated. Not so for the submission of eBooks with Apple…)
The only redeeming feature for Apple I can think of at this point is that they were probably taken by surprise at just how popular publishing with IBA would be, and grossly under-resourced the submission process. Still, that's a poor excuse for someone who has a book selling in the store and then finds the book pulled for daring to make it better…
Michi.