Archive for August, 2011

Implications of Amazon Kindle Cloud Reader

Tuesday, August 16th, 2011

Many of you might have seen the news last week, and for those of you who didn’t, please consider this a really small summary – Amazon released a web-based version of its Kindle application last week. Unlike the previously existing effort where you would be able to read your Kindle books in a PC/Mac web browser (Chrome, IE, Opera, or Firefox), Kindle Cloud (accessed by going to the URL https://read.amazon.com/) is designed so that mobile devices with HTML5-compatible web browsers – currently the iPhone and iPad Safari Mobile browsers – are able to essentially work similar to the Kindle application.

In a very simple sense, you don’t need an application to read your Kindle books. And outside of the initial connection, you don’t even need to be online as you can utilize the feature of HTML5 local storage to read selected books when offline.

Sound great right? Well, its a jump ahead for sure, and with many analysts predicting that there could be over 2 billion mobile devices with HTML5 browsers by 2016, it would seem to speak more relevance to the days being numbered for native applications.

Now, I’ve moved to using Kindle Cloud Reader and have to say that with the exception of page animations and copy/paste, I really don’t miss the native app much at all. Its good enough for my needs, and considering that I normally am using my iPad in a connected setting (I have a WiFi-only iPad), its not a bad idea to use for this kind of application.

So here’s the question, and the implication that people are going to ask if more applications go this route – what Bible readers are conductive to this approach? Are Bible readers conductive to this approached?

Many Bible applications have taken the approach to having a native application that has some Internet connected pieces (Facebook/Twitter sharing, downloading on-demand, backup, etc.). Would it make sense at some point in the near future for them to go the route of HTML5-like web apps like Amazon’s Kindle, Financial Times, etc. are not simply niche publications that are trying this, they have considerable followings and in many cases people willing to pay for increased access to greater depth of content and coverage – its literally a similar palette.

If this begins to happen in critical mass – given Apple’s rules for subscriptions with iTunes, Android’s fragmentation concerns across device types, and increasingly cheaper connectivity options for some mobile users – will your mobile Bible/religious publication approach stay with a native approach, or go this route? Will your users care and stay with you or move to someone else, even if it means they lose your support or content offerings?

 

[Infographic] Global Mobile Data Costs

Wednesday, August 3rd, 2011

This infographic was put together by Android Tablet Fanatic by aggregating publicly available data sources. For those of you looking to travel, these are some of the costs that you’ll be looking forward to. Click on the image to view it full-sized.

Whether you are traveling domestically or internationally, check out the latest pre-paid rates and keep those data costs in mind.

 

Raising the Bar for Bible Apps

Monday, August 1st, 2011

logos bible app screenshotWe come down pretty hard on Bible apps here at MMM. Either they aren’t focused enough, or they have so many features that people get lost in using them (a product focus issue). Nevertheless, there’s always room to talk about what they do well and what can improve from there.

What Mobile Bible Apps Do Well

Its well agreed, even when comparing leading Bible apps to other eBook readers/applications, that Bible applications are well developed for their target. From the handling of notes, to offering different views to compare content. Bible apps seem to run in the lead in respect to having the kind of user experience (UX) that is responsive to many of the needs of the Bible reader.

Footnotes, cross-references, and some even integrate image support better than you’d see on the Nook, Kindle, or other electronic reading devices. Add to that, an large body of content (usually priced appropriately), and you basically have a niche in mobile Bible apps that can pretty much sustain itself – for a little while longer at least.

And then you just have availability. Just look at our Bible apps listing – there’s at least one Bible app (and therefore several Bibles and other religious literature) available for nearly any mobile device. There are even SMS and audio-only options for those folks that would prefer something a bit more responsive to those reading and learning styles. I’ve been around mobile devices and software for a very long time, I don’t know of any genre outside of games that covers such a diverse range of devices and usage types.

What Mobile Bible Apps Don’t Do So Well

Where mobile Bible apps falter, and this is true for just about anything attached to the publishing world, is in two specific areas: access and consistency.

In respect to access, we still have the situation with Bible applications that content is locked to specific applications. Though we are getting better with this – just recently, we saw the release of Simple Bible Pro for HP webOS devices which uses Laridian’s licensed content. Instead of a situation such as a single vendor needing to making an application for (and then support) various mobile platforms, another company has made the application, and there was some cross-licensing able to be done here. This doesn’t happen enough, and therefore Bible software companies are dealing with access the hard way – building platform-centric silos. And in most cases aren’t even taking advantage of respective platform strengths when doing so.

Then there’s consistency. I’ll let Kevin Purcell from Christian Computing Magazine take it form here:

…While all of these are good apps, they have one thing in common. They lag behind their iPad/iPhone counterparts running on iOS in features and sometimes in stability. Let’s take Olive Tree Bible Reader as an example. The iOS version is rock solid and has a lot of great features. It has split screen capability and markup features like book bookmarks and notes. The most recent stable Android version only recently added some of these features, but not all of the iOS features are present yet. Logos has a good iOS app. They haven’t even re-leased an Android version yet, but do have a public beta (see link above). Their beta is little more than a book reader. You cannot compare translations, there is no Passage Guide or Word Study Guide and like the iOS version it has no note taking feature, bookmarking or highlighting. Laridian’s Android app is an alpha, not even a beta. I downloaded it and they have a great start, but it is definitely missing most of the great features of the iPhone version…

Read the rest of his July 2011 article (PDF)

Feature parity is important whether you are doing simple reading, or diving into a more in-depth study with your community. This aspect really hits folks who move to another mobile device and have gotten used ot a specific feature.

How Then to Raise the Bar

This is the part where you make the call. Being that mobile Bible apps have this base, where do they need to improve or become better in your perspective? Let’s hear what you have to say, and maybe the voices can get some of these excellent companies to consider tweaking their offerings in that direction.