- July 23, 2012
Something funny happened to me late last week, and it’s changed my opinion of native vs HTML5 apps.
I was working on a comparison of the various graphic novel formats on Friday when I kept having trouble with the Kobo app on my iPad. It was supposed to be able to display graphic novels sold by Kobo, but I kept not being able to get the app to download and open the one I bought.
This was a little weird, so I tried a couple times on Friday to troubleshoot the app. Other ebooks would download just fine (and I could read them) and I confirmed that the iPad app supported graphic novels. I could even get more ebooks from Kobo – just not that particular ebook.
This is a little embarrassing, but it took me some time to realize that I wasn’t using the Kobo iPad app. I was actually reading ebooks in Kobo Instant Reader, the new HTML5 based reading app which Kobo released in May.
I don’t use Kobo’s apps all that often, and since KIN doesn’t have an obvious label identifying it I didn’t cotton on until I checked the settings menu and noticed that I was reading on version 0.9 of the app.
Okay, there are obvious differences between the 2 apps, but like I said I don’t use Kobo’s apps very much. That’s why I missed things like the Facebook integration and Reading Life (not to mention the completely different menu design). TBH, I don’t give a damn about the social options for the Kobo iPad app, so it never occurred to me to notice their absence. I was really just focusing on the reading experience, and from that alone I couldn’t tell that I wasn’t using a native iPad app.
While that endorsement doesn’t sound like much, it’s a marked change from when Amazon launched the Kindle Cloud Reader last fall. I didn’t like the KCR back then, and as I sit here using it I still don’t like the Kindle Cloud Reader app. But the Kobo Instant Reader is a different case. It looks like Kobo might have taken my old complaint to heart when they designed KIN:
If you’re going to make a faux app based in HTML5, it needs to act like an app. If you can’t accomplish that then don’t make a faux app.
What’s even more amazing about this app is that even though it is still in a beta release, it’s already a decent alternative to the iPad app. I’m planning to stick with it even though it doesn’t support graphic novels or many other features. I simply like reading in it far more than I like reading in Kobo’s iPad app. The cleaner menu design is also nice, but it’s merely a cherry on top.
This is a relatively minor tech story, but there’s an important detail here. I’m sure you know that the Holy Grail of HTML5 apps is designing one which will let a developer get out from under the tyrannical thumb of Apple. The Financial Times is the only publisher that I know of who has accomplished that goal, and they’ve even gone so far as to shut down their IPad app in favor of the HTML5 app.
Guess what? Kobo is not too far from following suit, and they are miles ahead of Amazon and B&N. If and when Kobo finishes the Kobo Instant Reader they will be able to steal a march on B&N and Amazon. Having the only reading app with an integrated ebookstore (besides iBooks) inside the app could become a decisive advantage – if the cards are played right. (And that goes double for B&N, whose cloud reading app doesn’t even work on the iPad yet.)
Things are about to get really interesting.
Kobo Shows That HTML5 Reading Apps Have Come of Age is post from The Digital Reader