Contributed by guest blogger Ken Ristau

Rubén recently identified one of the areas that he felt needs real improvement in bible software: greater attention to being pedagogical. Personally, as my response in the comment thread indicates, I’m not so sure this isn’t already being done as well as it can be done by, at least, three of the leaders: Accordance, BibleWorks, and Logos. For me, the real area of deficiency I see is innovation.

When iLumina emerged on the market, it was a breath of fresh air. Finally, a program that dispensed with the prevailing paradigms and went for a completely different, interactive experience. Albeit it was different only in the bible software market; it’s been done before with Encarta. Still, it was exciting to see a company think outside the paradigm that is QuickVerse, Pradis, Logos, BibleWorks, Accordance, and the like. Now, it’s time for these companies to step up.

Perhaps, one of the best products on the market by the traditional software makers is Accordance’s Bible Atlas. Though best is actually relative… and seeing as no one has actually produced a competing product, there’s reason to wonder. Still, it’s potential is awesome. OakTree did a lot of things right with this product: cool layers that provide information about roads, empires, and such; actual coordinates and measurements for the entire map; an excellent “Find” feature; and so on. At the time it was produced, the program was truly remarkable. Sadly, its development remains stagnant–though I’ve heard rumours–and no company has anted up with something even remotely comparable. Yet, think about the potential: Imagine an Atlas that incorporates satellite technology; includes an array of archaeological and topographical maps or picture and video of important sites; or, uses 3D imaging as deployed in iLumina. Imagine zooming in on Jerusalem in an Atlas and a city map emerges with possible configurations of the city in various biblical periods. First, click on parts of the city to see where important archaeological discoveries were made, drawing on, e.g., the City of David excavations by Shiloh or the Jewish Quarter excavations by Avigad. Then, click on the temple mount and see a 3D model of the First Temple or Herod’s Temple. Imagine being able to do similar things at other biblical sites throughout the Mediterranean. Now that would be a resource!

There are also a host of other areas that bible software producers could explore. I desperately want to see innovative products that far outdo the multimedia encyclopedias and edutainment software available in other subjects. I want to see products that rival games in terms of ingenuity and graphics. iLumina was a definite step in the right direction but more can and should be done. Plus, quality of information needs to remain forefront because, in the end, that is what makes the product usable for a long period of time. So, innovation… that’s my take.

I have added a new updated review of MacSword 1.2, which supplements the one previously available on version 1.0.

David Lang has also posted a review over at CMUG. Good timing!

A new drop of MacSword has been released. It includes a number of interesting enhancements. Two that stand out, in my opinion, are the new and greatly improved search syntax, and the ability to see different Bible versions and/or commentaries in parallel.

UPDATE (21:00 PM): I emailed the developer (Will Thimbleby) and pointed out a few bugs I had found (e.g., Strong’s searches didn’t work). He fixed the problems and posted a corrected version (1.2a). I plan to update my review of MacSword soon.

It is a well-known fact that some of the most brilliant minds in any given field of human knowledge are not necessarily articulate and understandable when they try to explain the ins and outs of their work. This is particularly true in the world of software development.

I know a few Bible software developers. Most of them are excellent programmers. A handful are really geniuses. However, not all of them are able to offer clear explanations on how to use the software they develop in a truly pedagogical sense. That’s why it is so important to have someone around who can write clear, extensive notes on the philosophy behind the software, as well as the different practical applications of it. This is one of those areas where, in my opinion, there is quite a bit of room for improvement.

I look at literally dozens of Bible software packages, and I am worried by the increasing decline in the pedagogical nature of their manuals. For one thing, many products lack a truly comprehensive user manual, which is very unfortunate. Speaking for myself, it would be a lot easier to review a program if I had a decent, updated, detailed manual to refer to. But in general terms, albeit with rare exceptions, all that is usually available is some sort of quick (read “rushed”) setup guide. Now, this may be enough for someone who wants to shoot some nice pictures with a brand new digital camera, but it is far from adequate for people who buy Bible software in order to apply it to the study and exegesis of the Scriptures.

More information is needed (and, BTW, audiovisual helps are fine too!), but also more pedagogical information, tips, etc. The fact that some of the most sought-after threads in the various user forums have to do with the day-to-day “how-to’s” clearly indicates that there is a need that is not currently being met by the average manuals.

The improvements in programming and content should be coupled with some serious enhancements in teaching how to use the software more effectively. Test cases, adapted to different levels of users, are always welcome. Admittedly, this takes time, and it is not usually appreciated as it should, but it is something that goes in everybody’s interests. I mean, what’s the use of a wonderful program if only its developers and a select few can really make the most out of it?

I learn more by reading some notes on what the developers think their software should do, and the approach they have followed in order to accomplish it, than by browsing hundreds of pages of mechanical steps that do not care to the needs or interests of Bible students. So here’s my vote to have developers do some pedagogical work besides their programming, book building, and so on. And if you cannot do it yourselves for whatever reason, please find someone with the skills to do it for you. Your software and your users will be glad you did.

It is not a rumor anymore. Apple has finally announced that it will be switching to Intel processors starting in 2006.

Now, while I am not in a position to assess the real implications of this strategic move for Mac-based Bible software, I do want you to notice a few of the responses I have come across. The first comes from a secular Mac developer. The second is from Brandon Staggs’ blog, who, let’s remember, is currently developing a Mac version of SwordSearcher. Finally, I found Joe Weaks’ words on the matter quite interesting (as usual).

Time will tell what happens next, but Intel-based Macs are bound to change quite a few things in the coming couple of years or so. God willing, we’ll be here to tell you about it.