|
I am well aware of the Adobe/B&N collaboration, but it is certainly B&N that pushed the new form of DRM and convinced Adobe to adopt it. It was the same style DRM B&N was already using for ereader books and didn't want to give up. But it also meant that by getting Adobe to adopt it, B&N would do less work getting the Nook out the door since they would have the DRM work done for them.
And the thing is, I don't believe support is automatic, or that you have to go out of your way to disable it. The SDK doesn't include UI. So to support B&N ePub, they'd have to add UI to be able to input that username and password. This is simple reality of SDKs.
The iOS reader apps are ironically written by one company and rebranded. The RMSDK writers will happily sell you their iOS/Android app with the SDK for you to tweak and rebrand. That is probably helping adoption when Adobe's partner is the one writing mobile apps for everyone.
But I still blame B&N for being stubborn enough to push this and then go quiet when it isn't adopted quickly by everyone because it requires work to adopt it. When companies are cutting core features, rewriting their reading apps and more just to be relevant, are they really gonna care about their competitor's choice of DRM? Yeah, Sony could adopt it, but what feature should have been cut, or set of bugs left in so they could do it? They already left out OTA delivery to make it out in time for holiday.
|