Mobile Ministry Magazine

Great article over at Christian Computing Magazine (CCM) talking about Digital Bible Studying and how its evolved with now a near-digital/mobile-native approach that's able to be taken towards Bible studying. Here's a snippet:

...It is truly a great time to be a student of God's word. If you use a computer, smart phone, or book reader, then you have more tools available for studying the Word of God then at any time in history. And I think the best thing this does for us is not cut the time it takes to do our studying, but rather it helps us go much deeper. If your primary goal for doing Bible study on any of these platforms is to cut minutes or hours off your time in the Word, then you are missing the greatest benefit. Instead your goal should be to go deeper in the same amount of time...

Read of the rest of Digital Bible Study Is Breaking the Banks of the Personal Computer at Christian Computing Magazine (CCM).

In terms of a comment from MMM's perspective, I'll repeat a question that was stated in a post a few weeks ago:

So what does it mean to have believers who have instant access to multiple resource and communities, who seek answers to the questions of faith and life, evaluating sources in real-time through online and offline relationships, instead of waiting for a sermon or preacher to smooth the message.

If you will, we've got the ease in getting to the resource now. So what does the Body do in terms of teaching those analytical and spatial-search skills that will enable believers and non-believers alike to engage the Bible, and the people of the Bible, in God-edifying ways? Yes, these are indeed exciting times, but the implications of being able to do digital Bible studies means that we've also got to tweak our methods of teaching and living with one another. Are we up for the challenge, because, its for these implications that these times are exciting too.

Labels: Bible, CCM, communication, community, software, study

This was emailed to me personally some weeks ago, but thought that it was a good enough idea for a Bible application that it should be posted here:

..a bible reader a [device/software] that reads you the bible every time you push a button, so say you listen to the bible every time you wake up. you can set the reader to 5-10-maybe even 30 minutes at a time. you could have it read to you front to back or you can have it read to you by topics like happiness or by forgivness "you know what i mean"...

Now, the person who emailed me this wants to bring this idea to light. If you are a developer and would like to get in touch with this person, contact us via the MMM Contact page and we'll get you in contact with that person so that this innovative and needed application can come to light.

Labels: accessiblity, developer, development, software

Ah, now this is some cool software that's really work chatting some about - Covenant Eyes has released for iPhone and iPod Touch mobile devices.

Basically, this is an alternate web browser that replaces Safari and uses the Covenant Eyes service in order to foster accountable web surfing between accountability partners. I've got a friend who's recently downloaded this and he's said that its been a great addition to his mobile lifestyle.

Covenant Eyes for iPhone and iPod Touch is available via iTunes. The application is part of the paid service and cannot be used without it. You will also need to read the follow-up instructions via the Covenant Eyes user guide after installing.

As a side note, MMM is interested in hearing about how software such as XXX-Church and Covenant Eyes has helped your spiritual lifestyle choices. Its not easy to overcome the temptations of web life, but when you have, those stories can encourage others. So do comment here towards your victories and let's hold up one another in this area.

For more information, visit the Covenant Eyes website or connect with them on Twitter (@CovenantEyes).

Labels: accountability, Covenant Eyes, discipliship, iPhone, iPod Touch, software

I'm probably a lot less of an authority on the subject of choosing Bible software these days moreso than in times past because of the increasing (good) quality of offerings, and the very different paradigms of use that I've had. Where I'm very mobile, others might not be as much when it comes to choosing Bible software for.

I can only imagine what kind of difficulty that biblical schools can have here. On one side, you want to minimize support issues by using one or very few variations in software. But, much like choosing which Bible versions to read, you really want to teach people how to evaluate all so they can come to an educated opinion. There aren't courses for choosing the right bible software though, so what are schools to do?

After reading Karyn's views on the subject (at Boulders 2 Bits), I'm more convinced that there needs to be better data models with Bible software so that content and features can be easily shared between Bible softawre platforms. And I mean more than just the same Bible formats for the Bibles themselves, but similar usage flows for things like creating search filters, parsing languages, etc. If the companies can come together in this, then the idea of choosing the right Bible software moves more towards the effectiveness of the brand to give the best experience, not necessarly proprietory features. Because we don't think about how to click links and save bookmarks when we use different web browsers, why should things be so different with Bible software that we have to choose (and get stuck after so long in one system or another).

When you choose your Bible software platform, think not just about what you can do now with it, but what things look like if you were to decide later that the platform no longer suits your needs.

~via Bible Software Review

Labels: Bible, software, stewardship, study

In my opinion, this is a great companion piece to the burnt toast piece from a little while back. The pressure is on publishers and bible software developers to respond though - consumers will vote with their attention and wallets. Check out this snippet from K. Purcell's piece:

...But the better Bible software engines do more to the book than they do to a dead tree edition. So it takes extra effort to make a Bible software copy of a book and it has added functionality. So why not make it cost more? Digits do not cost any money to reproduce after the original file has been produced. With a book, there is a cost witch every copy of that book that is sold. The cost is tied up in the actual paper and ink, the storage while the book is waiting to be sent to the customer or the store, and the cost of the sending. With an ebook you simple copy it to a new location...

Read the rest at KevinPurcell.com and watch those pennies.

Labels: Bible, cost, software, stewardship

LJ from Trailblazin Ministries has put together a nice overview of the new Logos 4 software and Microsoft OneNote 2010 software. Pretty neat stuff.

Labels: Bible, Logos, notes, software, study, Trailblazin Ministries

Imagine, if you will, that you bought a cloud-enabled toaster. And that one day, you got a sudden in-home upgrade to three toast slots from two. Then, just as suddenly, the new feature addition was rolled back. So you were left with two slots and some smushed toast. And then your toaster decided it wanted to start serving orange juice...

The quote above is from an article at GigaOM where a Harvard Law professor (Jonathan Zittrain) questioned the value of closed platforms on cloud-enabled services. The article points to cloud computing and some mobile devices, but I want to highlight one area in particular - Bible software - as the closed platform that's more likely to burn people, rather than keep them openly nourished.

I was told once that the current model of Bible software (dedicated readers and an inability to take books from one reader platform to another) is needed for the industry to survive. But I have never believed this. Personally, I think its a cop-out to a model of business that just doesn't fit the intentions of the Internet as a medium for commerce and information sharing. Its a hearken back to the times when there was only one source for learning and others needed to be approved by Rome to carry the scroll... teaching was a whole other certification process.

And yet this is where we are. Logos on desktop and web and mobile. YouVersion web and mobile. Laridian mobile and mobile and mobile some more. Palm Bible+ on one mobile. And on and on. Publishers enable this through collecting licensee fees from developers and users alike (you didn't think you were actually getting the Bible did you; you are purchasing a license to read it, not own it). The market allows this, and we sit by because...

The features within these applications are chosen on the basis of need and market targeting. Some applications are more academic and have features befitting those audiences, others have features more for casual reading, and others still are a hodge-podge of features with no clear audience or goal. Regardless of the feature, they all serve the Bread of the Word. The same bread (content) in most cases. And yet, unlike the bread in your toaster, you can't just go to your neighbor's house and use their open source toaster to read your WordSearch-branded bread. You must toast it by WordSearch's toaster only. To me that's closed, and makes absoutely no sense given the intelligence and innovation that these Bible companies have at their disposal towards creating something... open, innovative, not necessarly free, but definitely sharable.

At some point, Amazon Kindle owners are going to want to move on past Amazon's system of ebooks and use others (Borders, Barnes and Nobles, an independent bookseller, etc.) And it will take all manners of governmental, private, and public pressure to get Amazon to open up. But nothing will change until those who are effected most will want to change it.

Which is why I think that for all the truth in the point that Bible software should be open to any device, any platform, at any time - where users purchase a license and can use it legally anywhere - we aren't going anywhere. At the intersection of faith and mobile technology, developers and users alike have forgotten to leave the cross (chains of locked platforms and marketing models) behind, and resurrect to something shared and usable by all. Nothing at all like how Jesus example was/is, nothing at all like moving forward past a locked intersection.

And that's ok, we have to protect the way things were - its only toast right?

Post-Script:: Eight (8) hours after composing this post, the Wall Street Journal published this article; I'm totally not the only one with these feelings about ebooks. This is a major issue that needs to be addressed by the entire industry, not just in the religious texts realm. The question is really simple though: is the Body going to be a point of innovation in technology here, or are we going to continue to follow the secular world with something we could do a lot better given our spiritual insight? I would hope innovation comes from the Body here, but I've been burnt by that expectation many times before.

Labels: Bible, developer, software

This past Saturday, I kept up with the Bible Software Shootout as many who were in attendance were tweeting about the happenings. One thing I can say about whatever that was happening there, it looks like a lot of the major software developers really got the point that the user interface of a Bible application means nothing if people cannot simply get in the Book.

This attetion to user interface design is totally a by produt of the impact that the iPhone has made on the entire computing industry. That's not to say that many software products and services don't suffer through feature-itis. Many do and will continue to. But, it is to say that there are some areas where people are getting it, and one of them just happens to be within the realm of mobile bible software.

So let me ask you this simple question: when you are ready to read a verse/passage in your Bible, how many steps does it take between you thinking about it and you getting there? How many steps after you've gotten to that verse/passage does it take for you to do the next thing (meditate, journal/bookmark, send it to a friend, etc.)? Its these kinds of questions that software developers think about often when they are developing the software that you like. And you know something, there are a lot of answers that they come up with. The simplest one though is always the hardest to pull off - keeping your eyes in the text.

This is something that paper books have a lock on. Its easy, you read, highlight, pull another book from the side to make a note, but the text is still there. No matter where you go, you must face the book in order to engage the text. The user interface is that simple.

And so here's my challenge and exortation to those who were at that challenge, and those who are developing other software Bible solutions: What can you do with your product to keep a person's eyes in the text of Scripture while still offering the featurs that enable you to differentitate from your competitors? Because if you can do that, then it won't matter what version(s) you offer, or even the cost of your product. People will be drawn to the text - and therefore to engaging with God. Drawing people to Him, will bring in the sales and solutions you seek.

Labels: Bible, innovation, reading, resources, software, UI

Here's one of those times where I wish that I was invited to take part inside of an event that would have been able to have a significant impact into the way that we use biblical software.

Specifically, I'm talking about the Bible Software Shootout that took place this weekend at the Society of Biblical Literature (SBL) Conference. The website This Lamp has provided the only> report of the event that I have seen - this despite the many tweets on the event which were very incoherent and disjointed. Here's a snippet about a surprising entry into the field:

...Although Olive Tree could not perform every aspect of the last two challenges, what they could do was very impressive, indeed. The representatives from Olive Tree showed that their "pocket" software can be used for very serious work if someone is so inclined to do so...

Now, without getting into the details too much, each participant was to use their software to complete 5 tasks, and then document the steps they went through. It seems (from This Lamp's reporting) that only Accordance was able to do this successfully, the others (Logos Systems, Stuttgart Electronic Study Bible, Bible Works, and Olive Tree) missed on one or several points.

It would also seem that not just the tasks, but also process documentation was a difficult piece to address. We've talked about it some here in terms of designing a Bible UI around the user, not so much around the features. And it would seem that some of the applications got caught up into the latter.

Another few things I noticed from this report were in those that were not present: Laridian, Word Search, Sword, and a few others. I would have thought that this would have been more about getting as many platforms here as possible for evaluation, not just those with certain name or reputation recognition. Nevertheless, there now seems to be some metric for some of these software platforms to be measured against in respect to academic (I refuse to use the word serious) biblical study on computing devices.

Check out the rest of the post at This Lamp, and be sure to give some feedback to your Bible software platform of choice if you would see these features better developed for what you've paid for. This will only make the field better for all, and hopefully, better students of the Word.

Other Posts on the Software Bible Shootout:

• OliveTree's Presentation at SBL
• #SBL (via Twitter Search)
• Report via Resources for Biblical Studies

Post Edit Note: If you've got a report from the Software Bible Shootout, post a link to it in this comment and I'll link it to this main post.

Labels: accordance, Bible, Logos, Olivetree, review, software

Kevin Purcell put together an early impressions review of the new Logos iPhone Application over at his website about a week ago. We are just getting to it now, but if you are considering the Logos iPhone App, then I definitely recommend this read. Here's a snippet.

...The other good thing about the Logos iPhone app is the overall interface. It is nice. It opens to the Home screen which lists reading plans and news information. Tap on Library and there are two lists, the bookshelf (pictured above) and the library. It is a little confusing to have a library tab on the library page. I wish they had made it more obvious that the bookshelf is the most used books while the library tab is all available books. Titles like Favorites and All would be more explanatory...

Read the rest of the review at Kevin Purcell's website.

Labels: Bible, iPhone, Logos, review, software

A topic that has come up with the discussion about Katana for Maemo 5 has been the issue of enabling an open source (and free) Bible reader to read paid (DRM-ed) formats. Its been a sticky issue within the electronic Bible realm for sometime, and I don't know that the discussion will go away anytime soon, but there are some aspects to this discussion that need to be stated so that all parties have the same starting point to move forward.

What is Copyright?

The first thing is copyright. Copyright is the defined as a:

...form of intellectual property that gives the author of an original work exclusive right for a certain time period in relation to that work, including its publication, distribution and adaptation, after which time the work is said to enter the public domain. Copyright applies to any expressible form of an idea or information that is substantive and discrete and fixed in a medium. Some jurisdictions also recognize "moral rights" of the creator of a work, such as the right to be credited for the work. Copyright is described under the umbrella term intellectual property along with patents and trademarks.

In most respects, this makes simple sense to all. Law designed to allow artists to profit from their work without fear of infringement by someone else. When it comes to mobile Bible software, there are several areas where copyright tends to rear its head:

• The coding used to transcode and format the Biblical text
• The Biblical text (per its translators or publishers)
• The code and user interface of the application that reads the Biblical text
• The systems used to develop or support the application or publishers' copyright

In respect to copyright, its a law. And laws are different for different regions. Some regions will limit a copyright for a certain amount of time to the original creator, whereas other areas might not limit it at all except in certain applications.

And while most of this is pretty simple, the idea of ownership throws all of this into several grayer-than-most areas.

Copyright and Licensing

The problem comes in enforcing copyright in a realm like the Internet where the concept of "regions" tends to get lost very quickly. Because something is attainable, the regional law needs to have a non-regional aspect to it if copyright is going to be skillfully applied. This is where the idea of licensing comes into play. Licensing allows the copyright holder to be compensated for their work, but also for the purveyor of the said work to use that item in a way that best fits them.

We see this in respect to music. When you purchase music (in the US), you are purchasing a license for its fair use. And in many cases, this fair use includes you being able to listen to that purchased music on any personal devices that you own.

Electronic Bibles

The same isn't exactly the case when it comes to electronic Bibles. Because of publishing rights and regional issues relating to literary works, licensing Biblical content for use across several devices or reader applications isn't something that's done from company to company.

This is why there are several Bible reader companies, and many of them do Bible readers for several types of software. Their licence to create and dissemenate only covers the material within their applications, not across it.

Where Ethics Comes In

Therein lies the issue of ethics for the mobile/electronic Bible user. Sure, you can purchase a Bible from "Company X," but you'd only be able to use it within their application. Because of the limited license (to you), to use that material on another device would mean that Company X would need to develop a container for you to read it.

Even if you are enterprising enough to take Company X's Bible and use it on Company Y's application, you still have the problem of licensing. Technologically, its not an issue to do that. Ethically it is. You are circumventing the license in order to gain accessibility. That's breaking the copyright, and therefore putting the law maker in position to execute justice for the copyright holder.

Solutions???

It would seem though that there are no solutions for issues like this. There are too many devices requiring too much custom code, and then so many versions of the Bible with so many owners of those copyrights. Its not an easy thing to make something available to all and then secure it for those who created it and deserve their compensation for time/resources.

But then again that just may be the problem worth fixing. Right now, companies license Bibles from creators/publishers, not individiual users. If users could also - inexpensively - license content, then maybe that license would have provisions for them to select which devices fall under that licensed use.

Bible software companies would then move into doing things to make their reader applications the selling point, promising compatibility with that licensing scheme, and value-adding whatever else would draw people to them.

I don't really know what a total solution would look like. But, in light of the many, many, people using mobile and other devices for a Bible, its clear that something different needs to be done so that copyright holders are rightfully compensated, but users don't have so many hoops to go through just to make sure they can use the materials they've created.

In the meantime, don't break a license just because you can. Follow the laws of your land, and work with those groups who are trying to enable change in a legal and God-affirming means. We all win when things are done in good order.

Labels: Bible, law, software, stewardship

There has a been a number of happenings in the area of mobile bible applications. Here are the highlights of what's come in the past week+:

OliveTree Releases Symbian S60v5 Beta and updated BlackBerry and Android applications

The folks over at OliveTree have been kicking it into high gear with mobile application updates. They've released an early beta of their OliveTree Reader for Symbian S60v5 devices (Nokia 5800XM and N97, Samsung i8910, and Sony Ericsson Saito). Testing is happening in this very public beta to get feedback before making this official. So jump in by downloading the reader and giving your feedback in the OliveTree forums.

There has also been an update to the BlackBerry and Android versions of the OliveTree application. Those too can be downloaded from the mobile-enabled download page.

Maemo 5 Bible App (Katana) Development Moving Forward

The topic of a new Bible application for Nokia's Mameo5 platform has continued with some really solid success. Already, there has been some movement by a number of developers to port the existing Rapier application to Maemo5 (testing on a live device only remains there). And then for the newer application - tentitvely named Katana - there's some work being done in a basic UI, and discussions about a plug-in approach that would enable the use of paid Bibles from folks such as OliveTree, in addition to the already planned for support for Sword and Palm Bible+ bibles.

If you'd like to learn more or join the development efforts, throw your eyes and prayers into the discussion.

Logos' Bible Software App for the iPhone

Logos has also jumped into the mobile application world with its Bible software application for the iPhone. This is a free application which allows its users to read, search, cross reference, compare versions, and even set up reading plans, all from an iPhone or iPod Touch device. As with many mobile Bible applications, this one requires a wireless connection as it connects to the Bibles featured at bible.logos.com. There's tap-and-hold functionality for viewing Hebrew/Greek, verse/text comparison, and linked cross references.

If you are looking at a Bible app to compliement your Logos library, this would probably be your best bet. For more information, visit Logos' iPhone software webpage or iTunes.

Got News?

Got news about a Bible application - new application, text, or public beta programs, shoot us a note about it so that we can help you spread the word.

Labels: Bible, iPhone, iPod Touch, Katana, Logos, Maemo, Nokia, Olivetree, Rapier, Samsung, software, sony ericsson

Just in case you've missed the posting over at Twitter, the chatter about developing an open source Bible reader for the newly announced Nokia N900 has started back up. Good comments in there, as well as some developers talking about what it would take to do so. Join the discussion, and maybe even assist in the effort.

And by the way of this discussion, if anyone knows of any open source (free or low-cost) multi-lingual dictionaries, please point out a few in the comments. There's a need for this for this Bible effort and other ministry efforts going on currently. Thanks in advance.

Labels: Bible, dictionary, Maemo, multi-lingual, N900, open source, software, twitter

Over at Talk.Maemo, I opened a discussion asking a few questions about a potential Bible application for the new N900 and other Mameo 5 devices. What I'm more interested in is creating momentum for the application than anything else, and from there, this community and others can be a point of reference for use-cases, testers, and developers who'd build something solid. Here's the questions posed at that thread:

• Is there anyone working on [developing] one? If so, I'd be up to assist in testing, UI, etc).
• If there isn't one under development, would this kind of application be useful and if so what features rank highest?
• If not a Bible application specifically, would a browser-extension that works with a Bible-based website be a suitable development target?
• What are some of the positives and negatives of Bible applications for Maemo 5 devices (pick the perspective that's relevant to you to speak towards)?

Hopefully, there can be something of some direction gained towards that effort and then developers and testers alike could move forward towards something of benefit for the Body and of highlight to the platform - can you imagine a Bible application being something that exploits the best nature of the platform and then profiled by the manufacturer? I can ;)

Add your thoughts here or the thread at Talk.Maemo.

Labels: Bible, Maemo, software, wireless application

This might be a bit late for some of you who've already left service today, but for those trying to get that MMM read in on your Google Android device before heading to service/fellowship, here's some good news for you: YouVersion now has a an Android application available.

This application is very similar to the iPhone version and you will find the same features throughout such as 40 different available translations, the One-Year Reading plan, viewing comments and contributions from others, and more.

Download YouVersion for Android devices from by typing http://youversion.com/download right from your mobile device (its free).

Just a note, you need to make sure that you have the 1.5 (Cupcake) version of the OS in order to use this application.

Labels: Android, Bible, Google, software, YouTube

In a conversation via Twitter (yes, I know that's a bit of an oxymoron) after yesterday's post, the idea that content needs to be independent was in some respects validated, but there's that aspect of publishers and developer rights that's rarely heard in this discussion. So I asked, what would this question of content independence look like if we didn't just say "we want it" but actually proposed a "how to do it?"

So let's try and answer that. And your feedback is key (especially those of you with some vested careers in this).

Here are some thoughts I have:

• Start with the content that is already within the domain of users (notes, bookmarks, etc.). This content should already be using an XML-based format that is readable in any Bible application regardless of platform (PC, mobile, Windows, Mac, Linux, etc.). This much should be done now. I'd say a commonly supported plugin that any Bible application can use that would unify formatting and content types would be enough for this.
• Concerning those newer translations which are already available in the public domain through publisher agreements (thinking ESV, NET, and a few others); where can open source developers and advocates join together in coding and marketing this raw content to whatsoever persons/orgs need it? In this way, we leverage open source not so much for the cost savings, but for the people-energy that it generates. Allow the push to use the software come from the grassroots angle (small groups, the pastorate, etc.) and then also the bigger angles (software and educational organizations banding together to promote code and/or study camps for example). Use that energy to create points of engagement and interest from those outside of those groups.
• Publishers have a vested interest in keeping their formats licensed, so how about instead of attaching the license to the Bibles, the license is attached to the user(s). Much like what some software companies do, publishers would allow a user or group of users to purchase a license which allows limited usage of that content; and a digital token is given that is simply asked to be reregistered a few times a year at no cost. Publishers get sales and metrics; people get content in as many ways as they can view it.

Those are some of my ideas. What about yours?

Labels: accessiblity, accountability, Bible, content, open source, software, tech

With the new version of the Firefox web browser (v3.5) released today, I thought that it would be great to bring back up that topic of content independence. Specifically, when it comes to reading materials (Bibles, commentaries, etc.), are these items independent of a particular browser or reading application?

I don't know that it is. Sure; there are more powerful and capable devices than ever before. And we can say that there's more digital content out there than ever before as well. But when it comes to moving that content from one device to another (for example from PC to mobile), a lot of times, we are locked into one method and don't realize it until we want to move.

I liken it to many of the desktop-grade Bible applications that are out there. All of them have some excellent content available; however, if you want to take that content with you, for many of these you would have to either purchase an entirely different library (software client and content), or manage some complex tasks before it can even be in a complimentary format.

And I don't want to say it to fault the publishers and developers; truly, they do a great work in building and supporting the breadth of languages, regions, devices, and content available to date. However, I do want to call them to attention - especially in light of the move to users becoming more and more independent of a PC-based computing paradigm.

Content should be just that; content. It shouldn't be attached to the presentation layer, nor should politics allow one silo to have prominence over another. If we are truly looking to good on teaching people to the ends of the earth, at the very least, content needs to be independent of the former ideas of reader/application.

This might look like Firefox, where mobile browsers take on an ability to utilize extensions which enable more functionality (this done at the developer or publisher level). Or this could simply look like more partnerships between publishers, developers, and users towards making content available, and sharing the load for marketing, management, and support.

Whatever is the solution though, I'm not sure that many Bible publishers and software companies will be able to stand pat as they are now: using dedicated readers, coding for specific browsers only, or limiting themselves to policial divisions in the hope of keeping marketshare. If the goal is to educate to the point of making disciples, then the content needs to be independent so that the accountability (individually and corporately) can take the primary focus of ministry activity.

Labels: accessiblity, accountability, Bible, community, content, software, tech

I had this thought... how do you (pastors, teachers, layleaders of small groups, etc) share your outlines and notes for your sermons and studies?

I've been playing with the idea of making my notes in HTML, and then using a combination of my website, Google Docs, and email to share these items. In this way, I'm doing some digital enablement, and for many folks, I'm leaving the cost (and admin) of printing and additional annotations to the listener.

Just wondering as I'm having some reasonable success doing this, and in some cases, its been an effective tool towards opening the door for other conversations that have led to better studies and discipliship situations.

Labels: annotating, notes, software, study

Caught this news a few days ago, Laridian Bible Software has released four new titles:

• AMG Concise Introduction to the Bible
• AMG Concise Bible Doctrine
• AMG's Encyclopedia of Bible Fact
• Reese Chronological Encyclopedia of Christian Biographies

Resources such as these can come in handy in the mist of discussions or smaller Bible studies. For more information and to purchase and download for your mobile device, visit the Laridian Bible Software website.

Labels: Apple, commentary, encyclopedia, iPhone, Laridian, Palm, software, Windows Moible

First there's good news of unlocked/unbranded Palm Centro devices going for $200, now there's some solid Bible software to go with it. Laridian has announced the availability of the MacArthur Study Bible Notes for their MyBible Bible Reader application. For those looking for a solid study bible solution for their PalmOS/GarnetOS mobile device, this seems like a great by. For more information, check out the Laridian website.

Labels: Bible, Centro, Laridian, MyBible, Palm Treo, software, study, Treo

If you want more people to purchase your software, you don't need an AppStore, you need to design your websites better.

Now that the important part of this post is out of the way, please, for the love of those people who are not using an iPhone and would like to purchase from you, if you run any kind of website where people can sell and download bibles and associated materials, please make sure that your websites have the following:

• A mobile version that is a three step process from the front page to having an installed bible on their device
• A conventional website that simply notes what's free, what's for pay, and what can be downloaded
• And a very visible search box that uses JavaScript to offer search suggessions so that a person would not spend a lot of time wandering through a site just to find the 'download for my device' link.

I say all of this after watching my mother stumble through three sites that I recommended to her to check out for a a bible for her Samsung Omina (a Windows Mobile smartphone). She still doesn't have a bible on her device. Aren't we supposed to have this down by now?

Labels: Bible, smartphone, software

Again with the BibleTech reflections... ok, so you are probably getting near tired of these, but really, there was a lot of good information that came through the presentations and networking. One of the conversations that I had was with a few of the folks at BibleTech (with the ears of other software and publishing houses nearby) in speaking about what users really want from electronic Bible readers.

There's one little problem, there are different buckets of users, and they want a different starting point. So I asked a question: since mobile is just one section of users, the paradigm of mobile use isn't the same as desktop or even book use, how about we start designing a Bible app from that different paradigm.

A few definitions so that we are all seeing this in the same (or as close to the same) light:

• Mobile: just speaking of devices that have a screen size smaller than 5in
• Mobile use paradigm: the goal is a task that can be completed quickly, and leads to other interactions that may or may not lead to a different technology or use (30 seconds versus 30 minutes)

So that be leveled, let’s start with what the process looks like:

Person sitting in a fellowship gets the call to open their Bible to John 3:16. There's some reading of the verse, then commentary. All the while, the only interface to the text is John 3:16.

Current Bible software says:

• Head the call to open bible
• Navigate to application
• Open book chooser, chapter/verse chooser
• Open another application (or feature to reader application) for notes
• Bookmark verse for later reference (notes usually not attached)

This sounds pretty simple. And in most cases, this is the process that we use when "thinking" about how to interact with content. Now, what if the user interface (UI) had us go into this differently:

• Navigate to application (or widget)
• Type in the reference(s) - yes, we can deal with multiple references at once here
• Select option to tag text (given preset tags of book, chapter-verse, date, and geolocation; can add custom)
• Small text field to write notes which are saved to an external file that can be read by other Bible, browser, or text applications

If you will, instead of starting at the point of "show me the text then go to where I want to go" (something how babes in Christ learn how to read the Word); we give folks a simpler interface (search box - think Google - and a list of recently used tags).

In speaking with those folks at BibleTech, the draw is that we want to expose people to that greater functionality such as commentaries, other languages, maps, etc., however the current user interface leaves a lot to be learned by users, which makes the user experience falter.

So my suggestion is that we simplify things. Starting from a search box (and this works for every mobile platform), from there, opening only the functionality that needs to be seen.

Now, this works for mobile devices better than it does for desktops (and to some degree laptops). When you are at those larger devices, you are sitting still for some period and working out something a bit more than casual reading. When the device gets smaller, the perception of functional time is different. You get on a mobile to get things done quickly, not just to read and browse. That being said, there are some elements of thinking like this which can be pretty powerful if given the attention to structuring data and simplfying.

I'll have to do some screens of how this would work out, but here and here are similar thoughts to what I've done on this meme previously. Who wants to take the first crack at doing something different?

And if you've read this far and think that this kind of approach might not be so good, take a look at what the Mozilla Firefox folks are proposing (Ubiquity/TaskFox). There's a lot that can happen when all we do is strip the conventional UI from the app, and start letting people use natural language to request functionality.

Labels: BibleTech, innovation, mobility, software, UI

Just a few more questions that came to mind:

• What kind of value do you see or not see in the types of Bible software used on PDAs and other mobile devices?
• Is there anything about current mobile Bible software that you'd like to see done better (or introduced)?

Labels: Bible, PDA, smartphone, software

Over at Palm Addict, there's a post about an application called MyHolyBible that has gotten an update. Some of the features include:

• Customizable User-Interface
• Enhanced User-Interface
• Variety of Font selection.
• Passage Reading of the day
• And more

Check out the rest of the post at Palm Addict and then download MyHolyBible for Palm OS devices.

Labels: Bible, Palm Addict, Palm OS, software

Go figure, apparently making a widget could be even simpler than waiting for a contest to be completed ;)

Matt over at Nokia Experts has written an article called Create your own Web Runtime widgets with Aptana Studio. . Basically a development environment for creating widgets, Aptana Studio makes it about as simple as possible for anyone to create a widget and get it deployed to a mobile device pretty quickly.

Now seeing this, I just need to get on a PC long enough to actually build this (unless someone else out there wants to take a crack at it). But it should be pretty easy to get up and going.

For more information and to try for yourself, visit the Aptana Studio website.

Labels: innovation, mobile, software, widgets

I was just looking at an article at Nokia Conversations about 2009 being the year of widgets and had the idea of a new widget. With the N97 Widget Compeition going on, this was quite timely. Then, I realized something, searching for a Bible verse, or saved bookmark, should really be this simple. I'd submit one for the competition, but then also share about its idea here and maybe get a few consolidation votes ;)

First off, when you think about looking up a Bible verse (whether print or digital) its always think and go. One of the frailties of mobile computers is the fact that in addition to thinking and going, you have to also open an application, and then navigate to some kind of search or index (book menu, bookmarks, or find).

Well, I started to think; what would be easier? Personally, a widget on my phone's front screen would be prefable. But that widget would have to make it really simple.

So I developed this with the idea that all you want to do is search, and it should not matter if you are looking for a verse from an application on your device or a Bible website that you prefer. That you might even have that verse saved as a bookmark somewhere like YouVersion, and all you want to do is retreive it.

Let's take a step back now. Widgets are simple programs. They do one thing only, and they are designed to minimuze the friction from thinkning about something to doing it. Many of us are familiar with widgets - Weatherbug, the clock on your desktop, etc. The idea being that when something happens, all we want to do is know about it. The more indepth things of making notes, bookmarking, etc. are left for full applications. Essentially, every Bible reader should start here, and then build the experience.

Now, about this widget. My ideal widget would allow for this to be configured to work with every Bible website and application that could be loaded on a device. That it would index all of the verses, bookmarks, and tags used, and only those would be searchable from this interface.

And if you think about 90% of the time you are sticking your hand out for a Bible, this would be it. You type the verse, it opens a popup to that verse with an additional button that says "Go to 'x' Application" or "Go to 'x' Website." That's it.

Now, for those who are students of the Word, and would like to do things like add the ability to mark a verse as favorite, add notes, highlight, etc. Nope. Not happening here. This is only meant to be short, simple, and to the point.

To developers, open your Bible application's APIs so that something like this could plug into it. You don't lose sales by allowing for something like this, and essentially, you open the door for more people to know about and learn about your application.

What are your thoughts? If not you, could you see someone really liking something simple like this?

By the way, the N97 Widget Competition is going on until February 27, 2009 (drawing on march 13th); winning prize is a new Nokia N97 mobile device. All you have to do is make an image of your widget idea and submit it.

Labels: innovation, Nokia, software, UI, usability, UX, widget

I wrote a few weeks back about my belief that the only thing I thought I needed to make my BlackBerry the complete mobile ministry companion was some form of GPS navigation. At the time I picked a model, I had to decide between having Wi-Fi capabilities or a GPS radio.

I picked wi-fi for the call advantages and the ability to have a second method to get internet access. Plus, third-party GPS pucks provide better (IMHO) functionality than current built-in radios.

I had an opportunity to see if TeleNav GPS Navigator would fill my needs.

TeleNav 5.1 promised to make my Blackberry a mobile GPS voice navigator, and I wanted to see it done.

After getting the software on my device, I was able to go throught the setup process, and pair it to my bluetooth puck via my phone's bluetooth radio. The program itself gives the option of Drive To, Directory assistance, Maps & Traffic and Tools/Extras. I went straight into the Drive To menu. I entered an address, and the program immediately queried the address and gave me the directions. The display showed clear 3-D arrows, and gave me the option of looking at the summary of the trip, or switching to 2-D. During the trip, I received close-to-live updates of the trip in progress, and estimated time of arrival.

You get to pick what type of voice you want; the voice prompts were clear and not given in a timely fashion. Any major deviations to the presented routes were met with ominous rings. After a few requests to turn round, it mapped an alternate route immediately.

I changed the inputs... the program can map your trip to accommodate fastest way, shortest, preferred route, or you can have the route optimized for traffic or pedestrian walking. The system continually polled for traffic, and located a major pileup before the electronic roadsigns noted it. It then gave the option of a segment-avoiding re-route.

All in all, I was surprised by the intuitive nature... every facet seemed to have been created to assist drivers in a very busy world. Even the little things, like the ability to search and input destinations by voice, or the integrated compass, are all very useful. The biggest treat is integration with desktop browsers. Telenav has browser plugins that integrate with Internet Explorer and Mozilla FireFox. These plugins help auto-populate your account with addresses that are synced to your device over-the-air. In other words, you can plan a trip on your laptop, and be ready to go when you open and sync the program to the servers.

While the volume was a bit low for my taste, it worked over my device's media player; so, even with music playing, the program "spoke" over the music at turns and such.

Another feature that seemed glaring in its absence was the inability to input trips with multiple stops. However, it does force better pre-trip planning, and since the Drive-To feature is fast, this can easily be used at every stop.

This program is juicy enough to be a homerun hit, but TeleNav does take it a bit further. The customer service was exemplary, and it was via the most innocuos of sources: Twitter. Within minutes of sending the most general of messages over Twitter, I was treated like royalty. Not bad in this day and age. Shockingly wonderful service.

Maps are upgraded quarterly; thus, you'll always have recent information.

TeleNav is available in different packages. You can purchases a one-yr, two-yr or four-yr licence, or you can do a monthly subscription plan. They also offer a 30-day free trial period. They also have standalone units, GPS receivers, and solutions for business as well.

For the peace of mind, I highly recommend it.

Software was tested on 8-hr trip with Freedom Bluetooth GPS Keychain receiver and BlackBerry 8320 running OS 4.5.

Labels: BlackBerry, GPS, review, software

This application is one of my rant 'n' rave items.

SplashMoney is yet another component of SplashWallet from SplashData, and is aimed at being a mobile financial manager. And boy, does it deliver...

Just like its sister app SplashID, it comes in a dual package: a handheld utility and a syncable desktop companion. Both are full-fledged and combine to give the user the ability to manage financial matters on the go.

To start, SplashMoney serves as a secure, password-protected repository of your sensitive data. Each account you have can be entered by type and account number. In this sense, it is the complete financial ledger; you can input financial transactions as they occur. Instead of carrying a check register, you can do it electronically on your smartphone, as this is a complete check Register.

Now, what really sets SplashMoney apart is its online capabilities. SplashMoney, on both the desktop and the handheld (with online access), has the ability to go online and retrieve complete banking information from some major banks. This is a very useful feature for a few reasons. If you bank with an institution on the list, you can set up the account automatically over-the air if you know your weblogin information. Also, with the view transactions feature, you can balance every transaction from these banks, and check them against entries you made yourself. To expand a bit, I seamlessly converted all my banking information to the electonic sheet, and I was good to go in minutes.

When I say complete, I do mean complete. The Budget feature allows you to create and maintain your budget within the device. The budget utility is integrated with the transactions, so you can easily keep track of your overall financial picture. The Reports feature allows you to summarize all the info in easy-to-understand textual information or pie charts (I really loved this). These reports and color-coordinated pie-charts can be printed.

Syncing the handheld with the desktop is independent of the Blackberry Desktop Manager.

I'd love to see the list of online banks increase, even though the list does arguably include every major bank there is. The ability to share databases in a seamless manner between, say, a couple would be a nice enhancement.

All in all, despite my experience with this software on another platform, I was just as impressed. I am an unabashed fan. The features can be expanded beyond just personal finance; I used it to create a mock ministry budget that I could have with me at all times.

SplashMoney is available on every major mobile platform (and for Windows ) at the SplashWallet site. Of course, there is a 30-day trial and a 60-day money back guarantee.

Labels: BlackBerry, review, software, SplashData

I've neglected to do this for some time, but here's a small attempt to rectify to those of you who have been using the Google Android operating system on the T-Mobile G1 (and soon to come other devices).

Here are a few Bible applications found:

• AcroBible for Android
• CadreBible

Please reference the Mobile Bible Downloads page which is updated with these and other Bibles for other mobile devices.

Labels: Android, Bible, open source, smartphone, software

Saw this some time ago at AnthonyCoppedge.com - a new service called MinistryGive that enables people to give to ministries/orgs via a website or mobile device.

This seems like an ideal solution for a lot of giving campaigns, or even as an additional "offering line" service for those who might not carry checkbooks or have PayPal accounts.

For more information, visit the MinistryGive website.

Labels: donation, giving, MinistryGive, software, web application, website

A poster at Palm Addict recently spoke a bit about a software application for Palm PDAs and smartphones called MyVerses for Scripture Memorization and Meditation 4.0. Basically, its designed to help you memorize Scriptures, and can serve as a bit of a reminder for a daily devotional or reading list.

Download MyVerses for Scripture Memorization and Meditation 4.0 from PocketGear.

Labels: Bible, Palm Addict, Palm OS, software

Olive Tree has released an electronic version of Dr. Wayne Grudem's Systematic Theology for iPhone and BlackBerry devices. As with other Olive Tree releases, you would need to also have the Olive Tree Bible Reader to read this.

Systematic Theology for iPhone and BlackBerry also comes with the complete Bible in ESV format with cross-references and bibliographies.

For more information and to download, visit the Olive Tree website.

Labels: Bible, commentary, ESV, Olivetree, software

I was asked by the folks at Internet Evangelism Day whether I had or knew of a list of mobile electronic Bibles and remembered the post we did some months ago.

Would you be so kind as to check out the Mobile Bibles list and add to the comments any that we are missing. Thanks.

Labels: Bible, mobiles, software

Was talking to a new coworker today and got a chance to play with the new BlackBerry Storm. A really neat device, it got us talking about mobile devices and specifically some features that I use with mine. Besides the 5 megapixel camera, which usually gets a lot of attention, my co-worker was a bit enthralled with the idea of instead of hitting a button to snooze an alarm or hit "ignore" for a call, that I could do those actions with just a simple motion of the mobile.

As I spoke with her, I realized that there are some aspects of mobile devices that really have to be seen to believe. Sure, one can do things such as have a touchscreen or a nice camera, but its another thing to reduce (amplify?) interactions to actual motions.

Think about what the Nintendo Wii and what it has done for casual gaming. The people who want and use the Wii are not people who are "into gaming" but who see the ability to wave the controller and become a part of the game. To these people it is not about specs and the shiny stuff, even though the PS3 and XBox 360 get that look, its about those simple things that one never thought of before when it came to gaming.

Now go back to that interaction with my coworker. I received a phone call as I was talking with her and simply flipped my phone over to ignore it. Simply speaking, she was excited. It was so much a simple activity - ignoring a phone call - but to her it meant a simple activity that was made even more natural by the use a simple behavior.

Besides FlipSilent, which does this simple snooze/ignore technique, I also have an application called RockNScroll which takes that idea of using motions a lot further. With RockNScroll, I am able to not only change the orientation of my phone from landscape to portrait by flipping it, but I can also do things such as scroll web pages and select items by "pushing" or "pulling" the mobile.

If you will, my mobile phone has become more than just an input device, but its an interactive one. And just like my co-worker who chose the BlackBerry Storm in part for the advanced touchscreen, I am using these simple motions as a means to just add a bit of interactivity to my mobile-enabled life.

When you think about it, this is more the future of computing than specs and shiny stuff. And when looked at like this, its going to be something very hard to ignore, and something a lot of folks will be willing to pick up and answer.

This post was previously posted on my personal website, but I'm following a solid request to have it posted here for further discussion and thought.

Labels: BlackBerry, innovation, mobility, N95, sensors, software

The developers over at Palm Bible+ have been plenty busy over the holidays and have produced a release candidate for the next version of the free and popular Palm OS bible reader. Here's a summary of what's going into Bible+ 3.4

New Features Inculde:

• Night mode support. It has own set of colors in font preferences. Look for the additional row; use the shortcut 'i' to activate/desactivate; can be configured via Define Controls.
• Status Gadgets for Treos: Bluetooth, Signal bars and Battery.
• Keys with built-in function can be overridden.
• Memo Pad's category selection in Export personal notes.
• Bookmarks will try go to the current bookmark if any. If the bookmark is in a category other than the current category, select 'All'; close and reopen the bookmark form (if you are in Jhon 3:16 it will try to select that bookmark in the bookmark's list)
• When adding a bookmark it checks if already exist. If so it uses that bookmark. (You can not have two bookmarks for the same verse)
• Popup list when the stylus goes up after sometime.
• 5 way navigation support on Snapshot screen
• Treo 650/TX navigation support.
• Support Jog Up/Down/Back in Book/Chap/Verse choose
• Multi-book versions. Like commentaries.

Improved Features Inculde

• Snapshot's navigation
• Made fast search faster on devices with more free memory, especially ARM-based devices

Fixes Include

• Major search bug (the fast search on ARM systems would sometimes miss a number of hits)
• A problem with the built-in hi-res Hebrew font
• A little bug in the Search results
• Fatal error displaying a starting verse footnote when Equal-Width Verse Numbers and Minimize Space After Number are ticked in Options, Preferences, Layaout.
• Fatal error in Search's menu.
• Fatal error when the title was too long.
• When copying a verse more than one time.
• Some memory leaks
• Selecting a Bible for the upper/lower part when in the lower/upper part the selected book is not available
• Verse Chooser only goes to 219
• Choosing books in the row 12 when there are more books than can be displayed on one screen.
• Navigation in goto Chap/Verse

As you can see, this is a pretty through list of fixes. Download the Bible+ 3.4 Release Candidate. And make sure that you download a Bible (or two or a lot more) to read with it.

Labels: Bible+, free, open source, Palm OS, software

Now this is what I call cool, Go Bible is a Bible reader that works with non-smartphones, think Moto RAZR like phones.

A free and Java-based application, Go Bible 2.2.6 Features:

• Christ's Words in red
• SMS scriptures
• Bookmarks
• History
• Coloured themes
• Fast search

The best thing about Go Bible is that its just simple and straight to the point. Can't beat that. And with some recent support by the Crosswire folks, you can bet that Go Bible will do more than just make a dent on phones. Looking forward to seeing that mobile ministry.

For more information and to download, visit the Go Bible website.

Please do keep this ministry in your prayers. Go Bible has a reach that can make it hard for developers and ministries to support the effort. If you have the ability, just drop the developer and Go Bible team a note of encouragement, or just lift them in your prayer today. Thanks folks.

Labels: Bible, Go Bible, phone, software

CrossComm, Inc. has released Bible Touch for the iPhone/iPod Touch. Bible Touch is basically a single edition Bible application in which the ability to read the Scriptures is not limited to needing an online connection.

Bible Touch is available in four editions: Bible Touch NASB, Bible Touch ESV, and Bible Touch LBLA and Bible Touch NBLH offer the La Biblia de las Américas, and Nueva Biblia Latinoamericana de Hoy Spanish text translations.

Bible Touch is available as a download from the iTunes App Store for $9.99 USD per edition. For more information and to download, visit the Bible Touch website.

Labels: Apple, Bible Touch, iPhone, iPod Touch, software, wireless application

Those might have moved from an iPhone to a BlackBerry might be delighted in this news. YouVersion has released the initial version (1.0) of their BlackBerry Bible Application.

From the YouVersion Blog:

Biggest [user interface] change is an upgrade to a more elegant design, while also integrating sleek carousel navigation in the interface. Other features include the ability to email verse to a friend, view contributions from YouVersion users and compatibility with a wider range of Blackberry handsets. Models included in this update are: 9000, 87xx, 88xx, 83xx, 8220, 7130, 81xx...

According to the post, there will be a version of the Blackberry Bible Application for the newly released Storm/Thunder (touchscreen Blackberry) as well.

Seems pretty slick of an application, especially for something free. Download it and let MMM know what you think about it.

Labels: Bible, BlackBerry, software, YouVersion

In the rise of mobile devices as capable Bible reading and studying devices, the ability to support multiple languages and character sets nearly rivals the need to support multiple Bible versions.

The website owner over at This Lamp has been playing with a beta version of Olive Tree's Bible Reader on the iPhone, and in a recent post/screenshot shows a Hebrew search as something that's coming.

This is pretty cool, and reminds me of when Palm Bible+ got a similar feature. Makes it fun to study the text in terms of seeing the direct Hebrew (if you speak it), or to learn it (side by side with the English).

Labels: ancient languages, beta, Bible, Hebrew, Olivetree, software

I'm late on this news (taking a week off from posting will do that to you), but wanted to post about some new books and an update for Laridian PocketBible4 (Windows Mobile devices). Here's a snippet of that PPC post:

• New books: MacArthur Study Bible Notes, MacArthur Topical Bible, Find It Fast in the Bible, Where to Find it in the Bible. Women's Study Bible, and the On This Day
  The NIV Study Bible (2008 update)
• Updates for PocketBible 4 for both the PPC and Smartphone versions.

PocketBible 4 is compatible with Windows Mobile 5, 6, touchscreened and non-touchscreened models. You can also purchase bundles that add several Bibles and commentaries to the mix with the application purchase. For more information and to download, visit the Laridian PocketBible 4 website.

Labels: Bible, Laridian, PocketBible, software

Palm Addict recently posted about PearBible. Here's a bit about Pear Bible from their website:

PearBible (BBE & KJV) is a pretty electronic version of the Bible that lets you enjoy the truths of God`s Word anywhere you go. You don’t need to carry heavy books with you any more, now everything you need is in your PDA! It also includes a few religion holidays. You can export these holidays into the DateBook, when you want to set reminders on them. If you prefer reading in Memo you can export texts of the Bible and descriptions of holidays there as well. PearBible (BBE & KJV) includes both Bible in Basic English and King James Version.

For more information and to download for Palm OS devices, visit the PearBible website

Labels: Palm OS, PearBible, software

One of my bros asked me why I'm not running MMM on the Mobile Web Server, and I told him it was because its still beta, and that's something of a large decision (I currently run the an MWS site as my personal website, and dig keeping content separate). Nevertheless, it did remind me that I did not post about the recent update of the MWS to version 1.5. Here are some of the new features to be found in this version:

• A new Access Rights web page highlights some of the site administration updates. This new page makes it easier to see and control access to MWS pages.
• RSS has been addressed with a new configurable RSS feed. Instead of just taking all the content, RSS feeds can now be separated into several feeds for the different aspects of the MWS.
• Finally, developers now have the ability to add their own Python web applications. By using the MWS SDK and framework, developers can create external applications which, when added to the MWS, will show up in navigation similar to the built-in applications.

This new version of the Mobile Web Server has also been tweaked to take advantage of the Destinations feature in Symbian devices using the latest 3.2 (Feature Pack 2) operating system.

Nokia's Mobile Web Server is compatible with Symbian S60 devices and can be downloaded for free from the Mobile Web Server website. As a note of advice, it would be smart to have an unlimited data plan with this. Its not bandwidth heavy, but you would want to keep the site up :)

For those who are still wondering about MMM and the Mobile Web Server, you can read the MMM Mobile Web Server Experiment Report (PDF, April 2008) to see some of our findings. Maybe we'll revisit it with a newer device and near-final software to demonstrate and push the envelope a good bit more ;)

Labels: mobile, Mobile Web Server, mobility, software

I was in a conversation with a bro over IM and said this in response to a piece of our conversation talking about mobile devices and trying out new operating systems/devices:

...there are positives and negatives to all platforms, and none are perfect...but you can and should get to a place where the strengths of the platform becomes your strengths to show Christ with it.

Do you agree or disagree with this statement? And for those who are looking for a new gadget, is this something that factors into your decision process?

Labels: education, function, Hardware, minister, software

When I got started with the Bible side of PDA life, it was really hard to find or create a digital version of modern translations. Due to publishing rights, this was frankly an impossible task unless you had the tools and knew the rights-laws for your region.

Since then, mobile Bible reading has been seen in a more favorable light and its been folks like Crossway (ESV) that have done a lot of this pushing into mobile media.

In a recent announcement, "Crossway has partnered with the leading digital software providers, including Accordance, Biblesoft, Laridian, Olive Tree, and WORDsearch, to make the ESV Study Bible available with all of its notes, articles, and features."

What does that mean? Well, no matter if the ESV is your cup of tea or not, there's no excuse, no matter what mobile device that you have, towards having a solid Biblical reference on your person.

The ESV Study Bible contains more than just the Biblical text, it also has the translator notes and references that makes for a better understanding as to why certain words/phrases were used. Basically, this makes it so that you don't have to understand Greek to know why something was used, but can use some textual analysis of your own to decide whether the translation is speaking correctly.

The ESV Study Bible will be available from electronic distributors such as Laridian, Olive Tree, and more. I'm not sure if Palm Bible+ will get it, but that would be pretty cool. There's also an offer going on where if you purchase the print edition of the ESV Study Bible that you'd get the online edition free. This is a nice way to bundle and shows some forward thinking for those who still need to touch the leaves when feeding the Spirit :)

Labels: Bible, Bible+, ESV, Laridian, mobile, Olivetree, software

Ok, so it doesn't exactly fit into the pocket so easily, but Logos Bible Software for Mac is now released, and for those with the smaller Apple models, this is indeed a mobile Bible solution worth looking at.

These are the base packages for the Logos Mac product:

• Bible Study Library for Mac
• Leader's Library for Mac
• Scholar's Library for Mac
• Scholar's Library: Silver for Mac
• Scholar's Library: Gold for Mac

According to the blog posting, "current Logos users who want to crossgrade and move their existing Logos Bible Software digital library over to our new Mac software can purchase the Logos Bible Software for Mac engine for only $59.95."

There's also a promo where if you spend $250 at logos.com or over the phone in a single order during November, they'll send you the Mac engine for free as soon as it’s ready.

Sounds like a pretty good deal to me. For more information and to see a demo, check out the new Logos Bible Software for Mac at the Logos website.

Labels: Apple, Bible, Logos, software

So the big question is... "Brian, are you happy that you shelled out the cash for this device?" My answer is of course... yes! I can see you scratching your head already so I'll go ahead and preemptively address your questions and confusion (because I'm a prophet and can read thoughts. Duh). I purchased this device for $200, which is way less than the current asking price of about $400. I think for what I paid, I'm getting a good amount of usability for my money. I work with spreadsheets all day long, in an emergency I have a perfect way to email edits to word and excel documents while out and about. While the browsing is less than satisfactory, at least it's there, and if you sign up for LogMeIn (which is free) you can take advantage of a full computing experience, including browsing, whenever you need one with some obvious rendering speed drawbacks, but they're not significant with the right settings.

The real benefit to me is the larger screen and keyboard with portability. This IS available with netbooks, but I don't want a 3rd computer to have to sync my data with. I want to take my notes, bring them home and have OneNote import them without me thinking about it. I want to be able to have all the files on all my computers synchronized without any extra steps. A third computer would likely draw me to abandon using one of them eventually because of this. Also, a netbook is $400 vs. the $200 I paid. Extra features like USB and VGA-Out ports are very nice, but not likely to see much use from me save for the occasional emergency file transfer or mouse usage. For me, the idea was to get something that would allow me to type faster and more accurately, rendering apps and data on a larger screen making them easier to use, while not creating an additional place to store data. For those of us who are tech savvy, one thing we will always be if we keep multiple devices, is tech redundant (i.e. Always having more than one device that can play mp3s, videos, store files, type documents, browse the web, or clean your shoes…. Ok... I'm wishing with the last one).

What I needed, was a cheap way to do my emails, blogging, note taking, and reading. While leaving some things to aspire to, the Redfly fit the bill… quite literally.

Labels: ceilo redfly, Hardware, review, smartphone, software, wireless application

Check out Part One of the MMM Celio Redfly Review to get up to speed.

There isn't any software on the Redfly itself to speak of, so what I want to address here, is how the software on the smartphone takes advantage of the hardware. Things like resolution, video playback, keyboard response times, sound emulation, and the like are all issues that books can be written on. Some things work perfectly, and others, way less than stellar.

First I'll talk about video playback. At the present time, there isn't any. In my limited experience with this, it seems that once the Smartphone is attached to the Redfly, all video processing is done via the onboard processor, which no developer has written anything for. This unfortunately isn't limited to just videos. Most of the games I play (Warfare Inc. for example) will not render on the device, or even boot up for that matter. All video players that I've tried will boot and render sound, which by the way only renders via your smartphone's speakers as the Redfly doesn't have any built in, but the players don't render any video. To its credit, most of the other applications take full advantage of the increased resolution. All of the Microsoft Pocket Office applications, Palringo IM, EReader, Pocket e-Sword, Olive Tree Bible Reader, the picture applications, and the file explorer for example, all worked without problems.

Internet browsing does leave something to be desired, unfortunately. While Pocket Internet Explorer does take advantage of the full screen, it doesn't improve the page rendering very well at all, and because of the video processing issue already mentioned, currently, alternative browsers like Opera and Skyfire also do not work. This is very unfortunate as most of what users will be doing will involve internet browsing.

The current version of the Opera browser (8.65) does, however, work very well. Web pages were snappy and rendered nicely as if this were a full fledged desktop browser. I love the Opera browser and hope issues with the 9.5beta version are resolved quickly as this is the version being included with a lot of the newer HTC devices like the HTC Diamond and Diamond Touch Pro.

I also tried the device with remote desktop services like LogMeIn, and it performed above and beyond what I thought my cell phone was capable of. I was even able to set the color and screen resolutions up so that it was optimal and fit pretty snugly on the screen with great readability. Now there's a great use for that 3G connection! The web page rendering speed really doesn't have much to do with the Redfly itself because it's all done on the phone, so tests on how fast web pages load won't be much different than if you were using the phone on it's own.

Speed, however, is a factor in typing. Even using the Bluetooth connection, there is no noticeable lag behind keystrokes and letters on the screen, unless you're typing a text message. I have used the Redfly every Sunday to take notes in both the new members' classes and sermon notes for the last 3 weeks. I've used applications like MS OneNote Mobile, Pocket E-Sword, and Pocket Word with much success and satisfaction.

One thing I dread using it for is typing text messages. Emails type fine however, but text messages are another story. At first I thought it may be a problem with the threading (I use Windows Mobile 6.1), so I deactivated threading and tested again to no avail. It's quite an annoying issue. I type at about 60-70 wpm (I'm sooo sloooow), and the rate the words appear on screen is utterly ridiculous. Imagine typing a message, let's say around 100 characters long, completing your thought, and ready to send… but you have to wait to see if you made any typing errors for up to a full 10-13 seconds after you finished typing (I actually counted… and it was only 82 characters.). As I said, this can be quite annoying.

As I mentioned, the reading tools I use (Pocket E-Sword, Olive Tree Bible Reader, and EReader) all work wonderfully. For consuming electronic reading material, the Redfly really does a great job with its larger screen. And with a rated 8 hour battery life, that's a lot of reading for me! I have yet to have this thing die on me when I really need it. I don't use it for long periods of time most of the time (except if I'm in a bind and really need to get some web browsing done), so I always have plenty of juice to get done what I need. On average I'd say I end up charging this device maybe two or three times a week. And mostly to top it off if I know I'm going to be using it the next day. I love to be able to listen to a sermon while tabbing between programs like pocket word and E-Sword while reading and keeping notes.

This device has taken typing to a whole new level. I didn't use Pocket word much until I got the Redfly. OneNote was another useless application to me until the Redfly showed me how useful the app could be, especially when paired with OneNote syncing. I'll save my doting over OneNote for another time and just say that I love that program, both on the Tilt and the PC. Yet, even with all of these great uses, if you're ever side by side with someone on an Asus (as I was on a recent trip to a conference with a friend who uses an Asus 1000H), you'll find that your experience in comparison with theirs… is less. While I am happy that the Redfly does in fact make using a smartphone better, it does not make it better or equivalent to the experience of using a full fledged computing platform.

While not an exhaustive list of issues I have with the Redfly, it's definitely a list of my big concerns. Given that they're promoting this device (at least on their site) to IT groups as a replacement for work laptops, I would definitely throw a fit if I was handed one of these by my local IT guy and told that this was the device I had to work from. For spreadsheets and word documents, it's excellent, but not for much beyond that.

There's still more to come! Come back tomorrow to get Brian's final thoughts on the device and get info on how he uses it in his day to day life.

Labels: ceilo redfly, Hardware, performance, review, software

Here is a (small) list of some of the places to get free (and low-cost) electronic Bibles (mobile, smartphone, laptop, and desktop):

• Laridian
• Olive Tree
• YouVersion
• Logos for iPhone
• eBible
• eSword
• Bible Explorer
• Palm Bible+
• Symbian Bible Reader (previous called S60 Bible Reader
• Mantis Bible Reader
• Rapier
• Berean Bible Study
• BibleTouch
• GoBible
• mbible.com (Online Mobile Bible)
• Touch Bible LE
• Several iPhone Bibles and Bible Widgets
• AcroBible for Android
• CadreBible
• Arabic Bible
• Best eBible (Symbian S60)

Are we missing one that you use? Add it in the comments.

Image via Palm Bible+

Labels: Android, Berean Bible Study, Bible, Bible Explorer, Bible+, iPhone, Laridian, Mantis Bible, Olivetree, Rapier, S60 Bible Reader, software, WordSearch, YouVersion

A good friend shot me an email about some coming updates for Olive Tree's iPhone/iPod Touch Bible Reader detailed in a post at Painfully Hopeful. Here's a snippet of what's coming:

...Well, I can happily say that personal libraries are now present beta release, and I was privileged to be shown a screen shot of what Hebrew support is going to look like on the iPhone/iTouch. Folks, you will be pleased, I am literally drooling over how Hebrew looks in the screenshot. The new version's UI differs some from the current release in the App Store, apparently from some work the gang at Olive Tree did with Apple's "UI Evangelist." The browser-like bar is gone from the top of the screen, which has been replaced by two buttons - one for selecting a book out of your library and the other to open the verse chooser (which has remained unchanged from earlier releases)...

Check out the rest of the post at Painfully Hopeful and then download Olive Tree's iPhone/iPod Touch Bible Reader and see the updates for yourself.

Image via Olive Tree

Labels: Bible, iPhone, iPod Touch, Olivetree, review, software

A post from the website Every Square Inch reviews a few Bible applications for the iPhone and offers some solid insights. Here's a snippet:

One of the best reasons I love having an iPhone is that it provides a quick, easy way to read the Bible. It's amazing when you stop to think about it. I always have the entire Bible right in my pocket! I can take 10 minutes to read a chapter any time I have the opportunity. I can search for a word or phrase in the Bible whenever I have need. All right there with me at all times—carrying nothing more than the iPhone I'm already carrying.

Personally, my favorite time and place to read my Bible is early in the morning on my front porch (while my dog Tucker walks around looking for rabbit droppings). An important morning custom for both of us. And often at that time, especially this time of year, it's still dark outside. That's when reading the Bible on my lighted iPhone screen is particularly handy...

Check out the rest of the post at Every Square Inch (link via Palm Addict).

Labels: Bible, iPhone, iPod Touch, review, software

A post caught in the weeds of Google Reader has been rescued :)

The folks at LifeChurch.TV have released a free Bible application for Blackberry users. A connected application, the YouVersion Bible App for the Blackberry opens the YouVersion Mobile site where one can pretty much do anything: read several Bible versions, search for words and phrases, catch up on the One Year Reading Plan, and even share with other YouVersion users.

Check it out and leave your thoughts here or at LifeChurch.TV (but tell them we sent you).

Labels: Bible, BlackBerry, software, YouVersion

A previous post about Bible readers got me thinking again about the idea of Bible formats and the fact that content is very much unmovable from one appliation to another. In some respects, I really have won out because with my current phone, even though its not Palm OS, it can use the Bible+ Bibles formatted for that application.

Because of this, there's extra value to not only having a Bible on my device, but the content that I've collected over the years. Needless to say, I've got a ton of Bibles (and other content), and much of that I didn't want to have to reacquire for another application and publishing scheme.

And in previous posts, we've talked about this conflict with publishers needing to (rightly) control the content they make available, and the Bible software developers who make all of our Bible readers possible. I don't want to rerun too much on previous discusisons, but I do want to ask the community here a question:

How important is it to you that the electronic Bibles that you have for whatever application you are using now are compatible with another Bible application you may choose to use in the future?

This is a pretty valuable question. Some don't consider the free or low cost Bibles, but those as well as the very expensive bundles can be very tedious to move from one applicaiton to another. What are your thoughts? And is this something that we should change?

Labels: Bible, Bible+, content, reading, S60 Bible Reader, software

Rocking through RSS feeds, Bible Softwrae Review linked to a Olive Tree BibleReader Beta Review at Touch Rundown. Pretty neat to see what Olive Tree has done. Check out this snippet of the review:

...One more feature that makes this a well-rounded app is the powerful search capability. You can perform a standard search, specifying where to search in the Bible, how to match your query, and how to display results. There is also an advanced search syntax that allows you to get very, very specific. You can match partial words and specify “ANDs”, “ORs”, or even get as detailed as to tell it how close to each other you want your search terms to be. You can also nest searches (create searches within searches). And that only scratches the surface. The bottom line is that the search capabilities of BibleReader for iPhone rival that of even desktop software...

Read the rest of the Olive Tree BibleReader Beta Review at Touch Rundown, then take a trip to Olive Tree to download it and try for yourself.

Labels: Bible, BSReview, iPhone, iPod Touch, Olivetree, review, software

One of the new aspects of play that I have had with mobile devices lately has come through the Nokia N95 and a piece of hardware/software called the accelerometer. The Accelerometer is basically a sensor within the device that senses when it has changed positions on the X, Y, and Z-axis and then orients the screen accordingly.

Those of you with the iPhone will know this feature as being the same thing as when you hold the device in its normal portrait mode, but then tilt to landscape for web or email viewing. The N95 also has this feature, and its something that when I unlocked it with a few applications, it got me thinking again about mobile Bible readers.

One of the common issues I hear with mobile bible readers is the screen resolution. For many people, the text is too small to read, but just right to look up a phone number (go figure). For some others, the buttons are designed for quick presses and therefore are uncomfortable for a reading mode.

Some browsers have seen this issue and have adopted a pan and zoom feature. For example, Opera Mini, Nokia's S60 Web Browser and Apple's Safari Mobile have this feature where you can view the whole of a web page as it would look on a desktop, but then zoom in to a section that you'd like to read.

The benefits of this is that you get some of the feel of the large page, but the compactness of the content fitting the screen that you are looking at. Now, what if that same idea, plus the accelerometer were applied to a mobile bible reader.

Let's give a usage case and then hear some thoughts from you:
- Open the Bible Reader and you are presented with two panes: last read verses and recent bookmarks
- Clicking on Last Read Verses you are taken to a zoomed out page with the focus square (the area that you can zoom into) on the verse that you chose
- The view is a nearly traditional four column, 42-line view (mimicing the page view that many are familiar with)
- Zoom in and the content is reflowed to fit the mobile screen for that specific verse with a line from the previous verse and a line from the next verse if the screen permits
- To scroll one tilts the device up or down, moving the Bible a verse up or down (an optional setting to allow it to move an entire screen, multiple verses, or off)
- For added fun, tapping the camera will indicate that a bookmark is to be made for that verse and a new screen pops up with that specific dialogue

Again, this is just a thought after having played with the programs FlipSlient and RockNScroll on my N95. What do you think of immersing the electronic bible reading experience with a few subtle actions such as described above?

Post created with alpha version of WordPy for Internet Tablets (please excuse any formatting issues)

Labels: Bible, iPhone, iPod Touch, N95, seminary, software, UI