The iPAQ 910 is going back tomorrow and then the other will be sent back soon too. It is almost a relief to box things back up and send them back since it reduces the phone clutter around my house and actually gives me a bit of a sense of freedom since so many can get overwhelming when trying to figure out what to pick up and take along.

That should be it for my mobile related trips this year as I have already burned half of my vacation time for CES and MWC.

Craig started off his presentation with a bit of his history related to Bible software that goes back 20 years when developed QuickVerse and eventually co-founded Laridian. He mentioned that 20th century Bible software focused on massive and expensive libraries contained on a user’s desktop PC. Today’s 21st century Bible software user is not tied to the desktop, wants their Bible on a portable device in many cases, and uses “disposable” products. User expectations include portability of their content and the ability to backup, print, and share the content they generate, such as notes, highlights, and bookmarks.

In regards to portability, Craig talked about the challenges of the different mobile operating systems (similar to what Olive Tree explained earlier). Like Olive Tree, Laridian has negotiated portable content licenses to help users that switch platforms. He posed the question about a possible universal content license that could be shared across vendors. The idea sounds plausible and as we move away from a world dominated by DRM this may become a real possibility. This could mean you buy the NIV version of Olive Tree’s Bible and then make a move to Laridian’s Bible application with the capability to receive a free or low-cost license to the NIV Bible compatible with Laridian’s application.

I found the next portion of his talk very informative as he explained the current situation at Laridian in regards to the different platforms. Laridian has eight readers from four different sources. The readers for Windows Mobile (touch and non-touch screen), Apple iPhone, iPod/MP3 player (audio), and Windows PC are in-house developed readers. The Palm OS MyBible application was actually written by a Palm employee who then moved on to Google and sold the code to Laridian. The BlackBerry reader is from Noah and Laridian only provides the content for the BlackBerry platform. This reader is also licensed non-exclusively so it makes for an interesting partnership. Laridian also purchased the Theophilos Windows PC desktop software last year.

The primary focus of Craig’s talk was on the synchronization of user-generated content. He showed a slide with columns for notes, bookmarks, and highlights to show what platform supported each of these types of generated data. If you have tried the Laridian PocketBible Windows PC version since mid-December then you may be familiar with their new synchronization provider and Sync Manager solution. The Sync Manager is PC-based and works with the sync provider plug-in to sync your user-generated data between mobile devices and the desktop. The current sync providers are available for Windows PCs and Pocket PCs (touch screen Windows Mobile devices). The current plan is to provide sync providers for other platforms in this order:

1. iPocketBible (preliminary version was demonstrated at BibleTech 2008)
2. PocketBible for WM Smartphone
3. MyBible for Palm OS

Craig gave demos of the PocketBible Pocket PC version and iPocketBible version. I am personally quite excited about how slick this tool works and didn’t think it could be done so well with the iPhone. Laridian is solving a MAJOR issue that I have been frustrated with for years. I used to backup my data, but I would either lose it or forget about integrating it when I switched devices and it just wasn’t a simple and easy solution. This new synchronization worked extremely well and I highly recommend you give it a try.

Craig went into the details of the logic behind the synchronization process and everything is related to time-stamps so they can determine what data is the latest and greatest. There is sound logic behind most all of the sync processes and Laridian includes a conflict resolution stage if there are apparent conflicts caused by data being changed in both locations or having time stamps different than the last sync time. Laridian may want to consider a skip or keep both conflict resolution option so that you can merge or edit your data if you previously added content on both the PC and mobile device. As a user of Windows Mobile, desktop, and iPhone Laridian applications it will be interesting to see how sync works with a PC and multiple mobile devices with different operating systems.

The Laridian Sync Manager utility can be used with providers other than Laridian as well so it may serve as a global data synchronization methodology. The details of the individual databases are isolated in the sync providers and provision is made for syncing of different formats. There are opportunities for synchronization across vendor products and any developer interested in this syncing functionality should contact Craig to discuss the future possibilities.

Technorati Tags: BibleTech08

While Drew touched on some of the global challenges in the mobile landscape, Stephen went into more detail in regards to the programming challenges faced by developers. Olive Tree currently supports 14 builds of BibleReader on 5 platforms (4 for the Palm OS, 2 for Windows Mobile, 6 for Symbian, 1 for BlackBerry, and 1 for J2ME). If you haven’t visited the Olive Tree Bible Software site in some time, then I highly recommend you check it out as they have completely redone it and made it MUCH easier for you to use and find resources for your particular device.

Stephen stated that he spends more time on cross platform development than on Bible software development. I personally appreciate this cross platform focus as it allows me to use BibleReader on S60 and Windows Mobile devices. BibleReader is actually one of the only options I have on S60 so I appreciate their work. I also learned that Olive Tree acknowledges and understands that many of their users switch platforms and devices regularly so nearly all of their Bible translations and texts have a common database shared across all platforms. I talked with Stephen after his talk and this means that you can buy a translation or text and then “own” that forever so if you switch devices or platforms your purchased content goes with you. This was a GREAT relief to know so I can now purchase content without any worries about which device I am using.

Stephen presented possible solutions to the issue of cross platform development and the large number of mobile devices. Some possible solutions were a common database layer, common text rendering engine, shared data structures, and the use good cross platform coding practices. A vendor could limit themselves to one or two platforms and avoid this cross platform issue, but it is good to hear that Olive Tree plans to continue their multi-platform support.

There are also many challenges when it comes to development tools since there is a wide range and quality of tools available. He mentioned that 3rd party software developers have less priority for wireless carriers than getting a new phone out the door. There are issues with tools (such as Metroworks and PRC Tools) and issues with emulators. I mentioned before that Windows Mobile offers good support for the developer with Visual Studio. Testing and debugging are issues to address since emulators don’t always emulate the actual device and it is quite costly to purchase all of the latest and greatest devices for thorough testing. Olive Tree does add debugging information into their software so they can try to address any issues that may arise on your particular platform.

The different programming languages and content delivery methods were mentioned in my coverage of Drew’s talk, but Stephen did go into a bit deeper detail. Often a problem is that users do not even know what device they have so they do not know what software to purchase or download. Stephen also mentioned that there are issues rendering complex scripts and fonts (like Hebrew).

Stephen had some thoughts on the future of mobility that included the merger of the desktop and mobile device. Hey, has Stephen been brainwashed by Nokia and their idea that their phones are really mobile multimedia computers? (Just kidding) Will social networks have an impact or serve as a mechanism for sharing in the Christian environment? The “in the cloud” strategy may be the future, but Stephen said it will most likely take a while since getting data over the air is not as fast, is expensive, and coverage is not universal. However, I have been using Laridian’s iPocketBible that works over the network and Laridian has optimized the functionality for the iPhone and the web to make it a very similar to a stand-alone experience that I am enjoying.

There are new UI paradigm’s such as touch (thanks to the iPhone and Microsoft Surface) and Nokia gestures. There are different display technologies to consider, like eInk and foldable displays.

I completely agree with Stephen that the mobile world will continue to explode and there will not be a clear winner that captures more than 50% of the market anytime soon. Olive Tree may have to create 3 to 4 more platform versions over the next couple of years. Collaboration between software vendors may help with some of these future challenges, but that too will be a challenge moving forward.

Technorati Tags: BibleTech08

Drew then spent some time talking about the history of Olive Tree, which he started as a student project back in 1984. In August 1998 the first version of BibleReader for Palm OS devices was released and they have since moved on to supporting the Pocket PC/Windows Mobile, BlackBerry, Symbian (both UIQ and S60), iPod (text only), and other cell phone formats. It is currently available on 12 platforms and they see something like 50,000 downloads a month of their texts.

The common theme in regards to programming language was that C or C++ was on many platforms (Palm, Windows Mobile, Symbian, and maybe the iPhone). I was a bit surprised to hear that development support and tools were the best for Windows Mobile and wonder if this fact has helped propel Windows Mobile past Palm these last few years.

Drew talked about some challenges that they face in development and selling mobile Bible texts. These challenges include:

1. Different programming languages
2. Data location (local, external memory, “in the cloud”)
3. Installation methods (over-the-air, SMS, desktop syncing)
4. UI systems (touch, stylus, non-touch)
5. Publishers and licensing content
6. Customer expectations (desire a desktop experience, users move to different devices often)

I enjoyed listening to Drew and learned quite a bit about the perspectives of the mobile market from a developer/vendor working in this space. I can’t imagine how difficult it must be to keep up with the latest operating systems and the various programming languages used by so many different platforms. Unfortunately, I am afraid it will just continue to get even more complicated as Symbian, Windows Mobile, and Apple (with the iPhone) continue to evolve while Google’s Android joins in along with the possibility of a new Palm OS based on Linux. I doubt there will be any consolidation of mobile operating systems and platforms anytime soon as there are too many dynamics in the market with wireless carriers, hardware vendors, software developers, and much more that are not going to go away or combine.

Technorati Tags: BibleTech08

I have the Rapier application loaded on my Nokia N800 and it uses the SWORD project modules for the texts. Prior to this conference I was confusing the SWORD modules with e-Sword which are two completely separate products. Make sure you first install Python 2.5 on your N800 before loading up Rapier. It is currently a great Bible reading application and I hope the developer continues to work on adding features and functionality.

In terms of mobility, Troy also mentioned the Palm Bible+ application that used to be an open source project and SWORD Reader for Pocket PC. I have tried the Palm Bible+ application before, but it has been a few years since I looked at it. This was the first I heard of the Pocket PC SWORD Reader and I’ll have to take a look at it. There are also some other mobile resources like the QPSword application for Sharp Zaurus Linux-based devices and I do still have an older 5500 I could try this on.

Troy’s first live demonstration was for the online OSIS Bible Tool that lets you access text via a web browser. I was very impressed with the Parallel Bible Tool and plan to use this for the study of different translations side-by-side.

Troy then showed something from their labs that was quite impressive, but something that was WAY over my head. He showed how you can take a papyrus image and use tools with a Google Maps-like UI to annotate and add transcriptions to mapped areas of the papyrus document. These can then be shared like Google Maps with a link to the page where you actually added content and notes. This may be quite handy for academics and those who study the original Word.

A colleague (sorry I did not get his name) then showed the SWORD project in action in both Windows and Linux formats. The Linux Bible, GnomeSword, actually can run on a Windows PC too. It was quite functional and very feature-packed for a free application.

I also learned that these amazing CrossWire tools are all written, updated, and managed by volunteers in their spare time and I praise the Lord for these developers taking the time to make these tools readily accessible for all of us.

Technorati Tags: BibleTech08

I take my Stowaway BT keyboard with me and try to use the TV-out on S60 devices, but many times hotel do not have the ports available to turn the mobile device into a traveling computer and the Foleo would allow you to always have a display and keyboard with you. I think the device may be a good companion for the business traveler who needs to get some basic work done on the plane and needs a device that lasts longer than the 2-3 hour battery life on most all laptops. Granted, there are micro laptops out there with long battery life and good performance, but they cost 3 to 4 times what the Foleo will cost you.

I need to get a hold of one and see for myself. What do you think of the Palm Foleo?

UPDATE: After some more thinking about the device, I just don’t think there is a need for the Foleo as I stated in my ZDNet blog entry.

An HTC Vox is out for delivery to my house right now and this may be the next device. I am also thinking about the Nokia E61i, Nokia E90, or Palm Treo 750v. Which one, or even other model, would you purchase if you had a bit of cash?

We also picked up a new desk at Costco so I could have a “real” place to work at home and I uncovered all my devices. I found the Fossil Wrist PDA that is Palm Powered and decided to charge that up and give it a go as my Palm device of choice to test out and play with.

You can check out my Treo 650 ad if you are interested. Treo 650 is SOLD!

I am also selling my palmOne Bluetooth headset on TreoCentral. I put the two WiFi SD cards (SOLD the SanDisk WiFi/256MB card) and GN Netcom BT headset on ebay to help raise some funds. I may also have a T-Mobile MDA up for sale shortly, but have to first check it out on Wednesday and see if it is going to be a keeper or not.

Feel free to email me at palmsoloATgmailDOTcom if you are interested in any of these deals and if you mention this blog then I’ll give you a bit more savings.