Posts Tagged ‘bible software’

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?

 

Analyzing Mobile After Its Applied

Wednesday, June 8th, 2011

In the previous post, we talked about how innovation needs to be relevant for it to have some kind of initial impact. How about we look at things later? For example, one of the questions that we pose to groups that want to work with MMM is: what else are you expecting to happen after the introduction of ‘X’ to your community?

If you will, is it possible to look far enough down the road towards the application of mobile or web technology to see some of the implications that you just won’t be able to control? For example, a group decides to add mobile technology to improve the ability for people groups to communicate with one another. But, doesn’t see that down the line, it was the use personal communication devices (and no longer sharing a single regional phone line) that caused group conflict, sometimes on a major scale (see the testimonies of the introduction and implications of mobile in the book Where Are You Africa).

Is it right to ask someone/organizations to be cognizant of the effects of mobile that can be so far down the line that its not (technically) controllable? I think so. And I think it comes in how we approach the technology as driver towards some kind of intended outcome.

What is the intended outcome of having a device that takes someone attention to their mobile device for one hour, instead of 5 minutes (the time spent on a game versus checking email)? With heads down that long, are we expecting that they will become less attached to the technology and more attached to reflection? Or, are we expecting that what we are doing is simply replacing an analogy behavior that’s done already? If we had them head down playing our ministry game/watching our movie, they now have a need to charge their device in more places. So there’s a purchase to extra batteries, car chargers, etc. They are using it more often so we now have to add sermons and teachings on fixing one’s attention spans. And the list goes on.

I’m not necessarily of the thought that gadgets are making us stupider or stealing aspects of our humanity, only that we haven’t totally thought through the implications of using this technology. While we can start for ministry (good, serving) needs, the impacts are always further. Being honest with some of the projects and applications we’ve come across, we’ve not done as good a job thinking ahead of use. That’s going to cause some unintended consequences. Some of these we’ll be ok with, but others might cause problems much too large for an application (or Facebook revolution) to solve.

 

Addition of Ink Makes Tablet a Better Bible?

Wednesday, May 25th, 2011

HTC Flyer screenshot of Bible app with ink, via Mobile GadgeteerThis past weekend, Matt Miller opined that the new HTC Flyer Tablet might make for the right approach to being a digital bible replacement because of it’s inking ability. During this specific look at the HTC Flyer, Matt notes just how well the ability to ink on the screen adds to the experience that many Bible reading applications already offer.

Spending much of my reading time on a tablet, I can relate to how well this can work within many application environments and communities. And as Matt also shows, using a service like Evernote along with is could also pull some of those behaviors that some are used to (writing in margins, etc.) into a digital domain to take advantage of some of the capabilities that paper just wouldn’t have.

This is a use case more centric to tablet (and even laptop) use. And so we should be careful not extrapolating it to every mobile device that can handle ink. Inking, specifically as we are looking at it here, takes advantage of the larger screen spaces tablets offer, and could also blend some spatial interfaces not used as well on small mobiles.

If inking could work, what are some ways that you could see the exploration of Scripture draw someone into a better understanding of it, or even help a small community better understand how to study the bible together (a community sketchnote if you will)?

 

Using A Print (Paper) Bible Alongside the Digital

Tuesday, May 24th, 2011

LunchOver at the Laridian blog, a post about using a print bible alongside a digital bible caught my eye. Here is a snippet:

This year was different though. Maybe it was the fact that we were going through the book of Isaiah or maybe I’m not so rigid anymore, but towards the end of the year I dusted off my print Bible and started using it both in answering my lessons and in class, along with my phone. I really liked having the whole passage open for review. That is the one thing missing on my phone (although an iPad could help with that).

My secret weapon though is still my iPhone. While we can’t consult commentaries and reference material, I have a variety of translations installed on my iPhone. When the NIV leaves me wondering, I can quickly review a verse or passage in the Amplified, NLT or Message and I’m not cheating one bit. I also do that when I’m working on my lesson at home for the following week. And it is still much more convenient to look up related passages using my phone than to flip around the Bible.

Read the rest at the Laridian Blog.

How about you? Have you gone from print to digital to a hybrid mix of both? If so, what were your reasons?

 

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.

 

Camp Logos, Logos Bible Software, and the Difference Training Makes

Tuesday, March 15th, 2011

Over at Bill’s Bytes, Bill spoke about his experience with Camp Logos, and how its influenced how he now uses Bible software. Here’s a snippet:

…Morris Procter, official trainer (former pastor) of Logos, truly knows how to teach in a way that’s interesting and practical. He knows how to engage his students. I got more out of the first hour than I thought I would’ve gotten from the whole camp! The camp turns the slow clunky Logos software into a indispensible lightening fast Bible Software! I found myself completely blown away by the software and how EASY it is to use once you learn a few things. CAMP LOGOS vastly exceeded my expectations…

Read the rest of Bill’s experience at Camp Logos.

This is a story that we can get around since we are  usually on the side of training people how to use their devices or software. It really does make a difference when someone takes some time with you to go through things, whether that is an hour or a few days.

That difference of training  (could we even refer to it as a form of digital discipleship) has always had the ability to make or break how people use computer software. Bible software is even more influential here. What Logos is doing with Camp Logos fits well into stewarding not only their product, but also helping to alleviate fears about how a product can be used.

We’ve had some similar responses from people once they’ve had some time to learn software or a gadget. There’s something to be said for someone taking a tool, and explaining it to you in a way that’s relevant to how you learn and how you want to use it.

How many of you are doing similar training/discipleship engagements with others? Or, are you in need of a particular kind of training? Let’s hear what might be missing in your or other’s experiences and like Logos, get folks looking at these tools in a better light.