The new Aibo is available to pre-order in Japan today and will go on sale on January 11th, 2018; there aren’t any plans yet to release it outside of Sony’s homeland. It costs 198,000 yen, or about $1,700, as well as the monthly subscription — but what price can you put on cloud-powered robot companionship?
I’m feeling more and more like the library equivalent of John Gruber these days.
“We have not changed our developer terms or guidelines,” Apple spokesperson, Trudy Muller, told The Loop. “We are now requiring that if an app offers customers the ability to purchase books outside of the app, that the same option is also available to customers from within the app with in-app purchase.”
This is a change from previous Apple requirements, and will require existing apps to make changes to the way they behave. It also puts Amazon, B&N, and other retailers far more under Apple’s thumb in regards to pricing and profitability. More than anything, it puts them in a confrontational position with other retailers, instead of being simply a competitor. It will be very interesting to see how this shakes out.
There has been general alarm this morning on the Twitter and in the blogosphere that Apple is going to start killing off non-iBook eBook stores. Phil Bradley blogged about the New York Times article on the rejection of the Sony eReader app by Apple, saying:
Well, this is an interesting development. Sony have had their iPhone application rejected by Apple. Moreover, they’ve been told that they can no longer sell content, like e-books, within their apps, or let customers have access to purchases they have made outside the App Store.
That is what the NYT article says as well:
The company has told some applications developers, including Sony, that they can no longer sell content, like e-books, within their apps, or let customers have access to purchases they have made outside the App Store.
But if you read the next two lines:
Apple rejected Sony’s iPhone application, which would have let people buy and read e-books bought from the Sony Reader Store.
Apple told Sony that from now on, all in-app purchases would have to go through Apple, said Steve Haber, president of Sony’s digital reading division.
Notice that Steve Haber did NOT say that non-in-app purchases were disallowed. I can’t tell from the sloppy reporting if that second clause actually came from the Sony interview, or from other sources. So here’s the deal: Apple has never allowed in-app purchases that bypassed Apple. It’s the reason that when you are in the Kindle app, and you go to buy a book, it pushes you out of the app and over to Safari and the Amazon website.
There seems to be no indication that the Kindle app is in jeopardy…Phil’s headline notwithstanding. It works exactly the way that Apple has told people it wants apps to work, and if Sony submitted an app that didn’t follow the rules, they knew good and well it would get rejected.
There is another explanation…Apple might be warning app developers behind the scenes that things are going to be changing. Tomorrow marks the announcement of The Daily, Rupert Murdoch’s new experimental tablet-only newspaper. With it is expected to come a new method for in-app subscriptions, which might signal the availability of a new infrastructure for app developers to take advantage of (and for Apple to force the use of).
But for now, this story is nothing but poor reporting on the NYT’s part, combined with a bit of over-excitability on the part of librarians. Amazon’s Kindle app, along with the literally thousands of other apps that rely on web-based purchasing and then web-based updating, isn’t going anywhere. Apple would have many, many, many more problems than Amazon if they just eliminated outside purchases wholesale.
This morning I got a tweet from Bobbi Newman that said:
Can someone explain to me the tech reasons Kindle doesn’t work with library ebooks, know its DRM, want more specific plz & thnx @griffey
More than you ever wanted to know about filetypes, DRM, and eBooks…here we go.
There are two different things going on when someone tries to open an eBook file on an eReader. One is filetype…how the file itself is organized internally, how the information contained within is encoded. This is analogous to the difference between a Word file saved as a .doc file, a Word file saved as a .docx file, and an Powerpoint file (.ppt). All are different filetypes…the program involved in the creation, editing, and display of those files describes the information contained inside. Right now, there are two main filetypes being used to describe eBook files: the Amazon eBook standard, or .amz file, and the ePub file (.epub) that is used by just about every other eBook vendor.
Amazon purchased Mobipocket (an early ebook vendor/distributor) way back in 2005, and used their format as the basis for their current proprietary .amz filetype. ePub, on the other hand, is an open, XML based eBook standard, and is used by a huge number of eBook vendors…indeed, it’s easily the standard for current ebook publishing.
But filetype is only half the battle. In addition to the way the file is organized/structured internally, there is also Digital Rights Management to deal with. Think of DRM on an eBook as a lock, with your eReader having the key to open the lock and display the file. Without the lock, the eReader can’t open the file at all…can’t even see what it is. And if it has the key, but can’t read the filetype, that’s no good either…in that case, you can view the contents of the file, but will have no idea how to render it on the screen properly.
Amazon, in addition to using a proprietary filetype, also uses a proprietary DRM mechanism. This means in order to read an Amazon-purchased eBook, you have to have an eReader with the right key, as well as the right interpreter for the file. So far, that means that you have to be using a Kindle, or alternatively, using the Kindle software provided for any number of other devices (Windows, Mac, iOS devices, Android devices). This doesn’t mean that’s the way it has to be. Amazon could choose, tomorrow, to remove all DRM from their files. This would mean that you’d still need a program to interpret the .amz, but you wouldn’t need the key anymore. Conversely, Amazon could license their DRM to other eReaders, in effect handing them the key…but it would still be up to the eReader itself to be able to display the .amz file.
Vendors that use the ePub format have chosen different sorts of DRM to lock up their content. Apple and their iBook app use the ePub format, but wrap it up with their Apple-specific Fairplay DRM. This means that while the file itself would be readable by any device that can interpret an .epub file, without that particular key on their keyring, the eReader can’t do anything. Sony, Barnes & Noble, Overdrive, and other eBook vendors have chosen a shared DRM solution. They license their DRM from Adobe, and run Adobe Content servers that provide the keys to epub files that they sell. This means that if an eReader has the key to one of those stores, it has the key to all of them…think of it as a shared master key for any Adobe DRM’d file.
This illustrates why, although both Apple and B&N use epub as their filetype, you can’t buy a book from the B&N store and then move it over to your iBook app on your iPad. Conversely, you can’t buy something on the iBook store, and then move it to your Nook. Same filetype, different lock.
Overdrive, in supporting Adobe DRM’d epub files, work with Sony eReaders as well as the B&N Nook…same filetype, same DRM key to unlock them.
With all that said: any eReader that will read a given filetype will read said filetype if the file doesn’t have any DRM. So if you convert an existing document to an epub using software like Calibre, Sigil, or InDesign, that file will able to be read on a Nook, Sony Reader, AND the Apple iPad/iPhone/iPod Touch. If you have some text and you convert it to, say, a Mobipocket file (.mobi or .pdb) then it would be readable on the Kindle AND the Apple iBooks app…but not on the Nook. For a complete list of eReaders and their corresponding filetypes, there is no better place than Wikipedia’s Comparison of eBook Formats article.
While a DRM free eBook ecosystem would clearly be the best for the consumer (choice of device, free movement of files from device to device, etc), the second best option is an ecosystem where the DRM is ubiquitous and the patron doesn’t even realize it’s there. This was the case with Apple and the early battles for music sales on the ‘net…they had the store and the distribution network (iTunes) as well as the device used to access the content (iPod). All of the content was, originally, DRM’d, but largely no one noticed since it was completely invisible for the average user.
The biggest issue with eReaders and library patrons is that this chain isn’t seamless. The content providers and their DRM servers are huge headaches for the average eReader user. My hope is that publishing goes the same way that music did, we we find both a common filetype and lose the DRM. But it took digital music years and years to get there…so I’m not holding my breath.
I hope that helped, but if it didn’t and you still have specific questions about your situation with eReaders/eBooks, ask away in the comments and I’ll do my best to answer them.