Posts Tagged ‘bible applications’

Looking at the Perspective Amazon’s Kindle Gives

Thursday, October 6th, 2011

When I am at a coffeeshop, I usually have my mobile to the side of me and my iPad in front of me -occasionally with my wireless keyboard. At times, at least when I’m typing on the keyboard, I’m stopped to ask if I like my iPad, or how I get along with the keyboard. On one particular day, a woman asked me my opinions on the iPad as she was considering one. It just so happened that less than an hour before she asked me that, Amazon announced its new slate of Kindle reading devices (Kindle, Kindle Touch, Kindle Touch 3G, and the (color/Android) Kindle Fire). I mentioned to her that she might want to consider the Kindle – and it was apparent that she had. And then showed her the image seen on this post – her expression and the conversation that ensued afterwards got me thinking about how leaders, technologists, and then everyone else tends to consider technologies like what is exposed with Amazon Kindle.

For instance, the woman asked me what it is that I do with my iPad (reading, drawing, then everything else was my response). I showed her my artwork, and then the notes that I’d written at a recent church visit. The notes impressed not just because they were handwritten, but because she could see the point in not just having an electronic bible, but an ability to write notes, highlight, and then have those available on any computing device she owned. It sounds almost normal to many of us, but the perception that you can disconnect content from the devices you read it on is still a new idea to many.

She asked about saving the data on my iPad and how much space it takes. I explained to her how I don’t save a lot on the device itself as I use the entire Internet as my hard drive. We talked about how Amazon, Dropbox, Microsoft, and others essnentially give you their servers to use as the hard drive. In that case, its not always a limitation of the space that you worry about, but how you are able to control access, security, and what you are comfortable with storing on another company’s hard drives (servers). She noticed that on the pages for the new Kindles that there was no mention of the size of the internal storage and asked why that could be. I told her how Amazon is positioning their servers to be your hard drive – essentially making the Internet your hard drive. Her expression again amazed at not considering before that you could take what seems to be a normal computer function and turn it on its head.

So what becomes of how we talk and demonstrate Biblical texts? Could we have moments where instead of simply telling people to turn to such and such a passage that we could have shared that bookmark via YouVersion or another Biblical service. Or, maybe as a minister who is an aspiring author, do we learn and utilize services like Amazon Kindle Direct Publishing and Lulu to disseminate our locally-created materials instead of or in addition to the traditional publisher route? Obciously, there isn’t a need to do these kinds of things all the time, but devices like the Kindle will mean that we do have to consider that our use of the technologies available will endorse the purcahsees that many are already making.

Or, we can choose to not see efforts like the Kindle as being useful or beneficial for our respective audiences. Which is ok. But, if you are in the business of content creation or teaching, what kind of perspective will that lend to those whom you say you lead?

~ picture via Gizmodo

 

After You’ve Gained the Knowledge, Then You…

Monday, July 25th, 2011

Image: Dual pane view of Bible+ showing KJV and ESVA recent tweet by the Folks at Audio Bible/Faith Comes by Hearing (@audiobible) got me thinking (again):

If u could carry the Bible around with u in more than 500 languages – like in your pocket – how would u use it? #Hmmmm #GreatCommission

Original tweet.

I used to carry 1, then 2, then 15, and at one time over 100 Bibles around with me on my mobile devices (thanks Bible+). At the time, I justified it because I was (a) reading/studying Scripture a ton more than I do now, and (b) I interacted with several people who “heard” the Scriptures best in the translation they most used. Being that I was also at college during this time, it felt like the right way to approach speaking spiritual matters in a clear and consistent manner (1 Cor 14:1-19).

I don’t carry as many Bibles with me these days. In fact, until recently I didn’t carry any versions on my mobile (still no app, but I’ve got a Bible), and the ones on my iPad are the same in each Bible app or website (ESV, KJV, NET, and a few others). I’ve got less a need to carry as many versions of the Word as I do the onus to live as much of the Word so that when asked, I can give the appropriate answer to my faith (1 Peter 3:15-16). That, and the consistency of being in or near connected spaces allows me to search quickly from a series of websites when needed, or just make a note for something to come back later to.

That’s not the case for all folks. Many of the frequent travelers and missionaries I’ve met would jump at the ability to have Bibles and other texts in as many languages as needed, and at a moment’s notice. Their interactions almost require it of them. And when they are able to have something that speaks right to their audiences, it makes living among mixed groups that much easier to manage. When they don’t have that content, or even the ability to get a clear translation, their relationships to people and environments suffer.

But such use speaks to that end of things – where the tweet asked “how would you use it?” Many of use have libraries of Bibles and other content in print on bookshelves (digital and otherwise), but what have we done with it besides making it decorative? Have we taught someone to read, or took the time to use those resources to tutor people who are studying those subjects we’ve collected? Have we engaged the cultures beyond the pages and held the kinds of conversations that would amplify or change our opinions of those cultures, people, and events? Or, is it just a number?

In grade school, many of us learned about the terms kinetic and potential energy. Kinetic energy is identified by its impetus to move – the energy immediately before movement happens. Potential energy, on the other hand, is energy that is stored and is usually static due to its position or configuration. You’ve got that neat Olive Tree, Logos, YouVersion, or Bible.is app with hundreds of Bibles and other materials ready to be used. Are you in the process of transferring that energy into the lives of others, or are you configured simply to display the potential of what can be?

 

The Casualty of Symbian Bible Apps

Monday, May 16th, 2011

In a lot of respects, its rare to talk about Bible apps for one specific platform – there so many – the causality of Bible apps for the Symbian platform has been one of those questions that has gnawed at me a bit. Not so much even for the lack of applications, but the missed opportunities because of where the Symbian platform has been represented.

What is Symbian?

Symbian is a mobile operating system and platform that’s been used by Nokia, Samsung, Motorola, Fujitsu, and LG for mobile phones. To date, there have been over 600 million devices shipped and sold with the Symbian operating system, making it one of the most prolific  in use.

Nokia has been quite adept at making Symbian fit its needs. It has pretty much been selling Symbian devices longer than people have given credence to there even being a category called smartphones. To that end, Symbian has been deployed with more carriers and in more world  regions than all but the most basic of Java handsets.

Unfortunately, it is also considered an older platform that while stable and optimized for mobile devices, falls quite far behind some of the newer entrants in respect to ease-of-use, developer tools, and ease of finding applications. And so Symbian recently befell Nokia’s reorganization efforts (first spun into an open source platform, and now to be greatly minimized  over the next years  to be replaced by Windows Phone).

Symbian and Bibles

By accident of niche, Biblical software usually is a fairly easy one to fill. Find a publisher that has the languages that you want to address, write the application to deliver it, and then make it available. The issue with Symbian is that its actually a pretty difficult platform to build on. Without getting too technical, its just plain to say that developers have needed to had a certain type of older technical knowledge (previously) or invest in toolsets (Qt, Java, etc.) which required a good amount of patience before progress.

When I moved to the Symbian platform in 2008, there wasn’t much to find for Bible apps. Laridian, Olive Tree, Symbian Bible, and Go-Bible were pretty much your only options. And for a while, this was just fine and covered most of the Symbian devices that were in existence. When Symbian went to a touch-based user interface (UI), things got a lot fragmented, and Symbian Bible pretty much became the only option (Best eBible came on the scene later). Which was good and not good – a free application, using Bibles formatted for the Palm Bible+ application, and had no support for newer translations. Newer platforms ended up with a very easy “in” for adoption, they had what people could read, and could find.

A Missed Opportunity…

In light of all of that history, its easy to say that Symbian (and the companies associated with that platform) might have missed an opportunity to take a platform that has already made considerable inroads even further. But, it had a good bit going against it, and so it is now in the position it is in.

But does that mean that all potential opportunity for this platform have been lost? I’d say no, if technical aptitude is seen as a gift that can benefit the Body. When I say technical aptitude, a platform (like Symbian, but all qualify here) benefits by such knowledge as developer tools, device interfaces, language mapping, usage analytics, etc. A person who is skilled in any of these areas would be a suitable team member for a larger project creating an application, service, or refining a digital faith experience. These persons have to be looked for in “not normal places” as their gift isn’t something you’d find in Exodus on the way to creating a mobile altar (Exodus 25-27).

There’s also the benefit of much of Symbian’s assets being made available in open forums (for example Forum Nokia), through some open source technologies (for example Qt), and through the continued ownership of Symbian devices (installed-based analysis by Vision Mobile). In effect, there’s a lot of folks out there who can still benefit from a Bible solution on this platform.

The Lesson for Other Mobile Platforms

It is easy for the market, and popular (loud) opinion to state where you should place your development resources. Certainly, making plans for mobile software you’ve got to take into account devices, services, and experiences (the entire frame of mobile) and what is currently and what will be in the years to come.

When it comes to religious software, you also have the opportunity to always tap into the installed base of current users. Many times, your frequent fans and users of digital faith items will not splurge on the latest devices or services, though they will want to receive some of the same experiences that newer devices offer. It is in this that the opportunity lies, and where its possible to not just make a product, but help drive older platforms to a friendlier sunset.

Currently, there are several mobile platforms that have come and gone (Epoc, PalmOS, Windows Mobile), and some that are pretty much on their last legs (Symbian, older versions of Android and iOS, RIM’s BB OS 6 and earlier). Developers looking to cut their teeth on a mobile platform to learn and to provide experiences should not forget these platforms. And at the same time, you should go into any project with a clear (and simple) goal and definitive timeline. You  will not be able to support those devices for very long when the official support has faded.

Lastly, when you are a platform that has cultured a community of content, but you are no longer able to support that platform, utilize the open code and support communities of Code.Google, Forum Nokia, SourceForge, GitHub, and others as places to put your code and release notes. There might be someone willing to take up the project, or at least help you migrate your project’s contents into a newer platform. For example, MMM participated in an effort to update the Rapier Bible application for Maemo 5 devices, fixing some linger bugs, but that also set the stage to develop (and later release into widespread testing) a Bible application written in Qt from the ground up called Katana. The rewritten application leans on lessons of the former, but has a much longer viable life because of decisions made early on to support certain content and programming hooks.

For Symbian, it may very well be the case that the sun is setting for it as a leading mobile platform. It is also the case that there are some years and various regions of users that still haven’t been served with digital faith content though having a platform capable of supporting it. Do keep that in mind as you consider your mobile strategies, and remember to study the past platforms for what is probably going to happen to many others in a nearer-than-you-can-expect future.

 

Revamped and Updated – Mobile Bible Apps Listing

Friday, January 7th, 2011

image of BibleReader 5.0 from Olive Tree, via the water is alive...This past weekend, we were updating the Mobile Bible Apps page and noticed that the list was getting a bit out of hand. So, we redesigned it a good bit.

First thing that you’ll notice is that the applications are now broken down by the mobile or web platforms. We’ve got all mobile platforms covered with iOS, Android, webOS, Symbian, Maemo/MeeGo, and Windows Mobile.

We’ve also highlighted SMS Bible ServicesJava/Non-Smartphone, and Audio Bibles as there’s a big push happening to get bibles and other content in these areas.

For most of the platforms, in addition to highlighting some applications, we’ve pointed to the application store for that platform (where possible) with a search page that highlights not only Bibles, but other content such as themes, reading plans, and more.

We’ve also added a very important section that’s been often asked for - Accountability Software – featuring Covenant Eyes and X3 Watch’s software for iOS and Android devices. Hopefully, other mobile platforms can be addressed and we can get those added here as well.

This page was redesigned to make it easier for you to find and use mobile and/or web Bibles and other software that will encourage your faith walk.

If you are a ministry or developer with software for one of these platforms (even if its just an update), let us know about it so that it can be added here.

It’s 2011, no excuse to not have your mobile and web untouched by Biblical software now.