An anti user private API violation retraction in an update.
They missed the feature in the original approval, then took something away from people who already bought the app. They should be required to offer refunds when they force antifeatures on users such as this.
Surely not everyone would take them, but some will
Do you think it would be preferable if the application broke (or broke another application) unexpectedly at a later date due to an otherwise innocuous system software update?
It'll be interesting to see how the "duplicate functionality" rules of the App Store play out once Apple's ebook reader is available. They'll have to pry Eucalyptus from my cold, dead hands.
iBooks is not part of the system software. There is no reason to believe that the duplicate functionality rule would apply, even it its most extreme interpretation.
They missed the feature in the original approval, then took something away from people who already bought the app. They should be required to offer refunds when they force antifeatures on users such as this.
Surely not everyone would take them, but some will