I haven’t posted here since Granny Bolstad passed away in April as I have been focusing on my family and other projects, including my two ZDNet blogs and Nokia Experts site. I am doing very well and was just promoted to the highest level of Senior Associate at my normal day job. My two ZDNet blogs are doing well and helping us get out of credit card debt, mostly built up over our 3+ year yard project. I am approaching one year with my Nokia Experts site too and even though that hasn’t been a money maker or anything it is a site I am passionate about and really enjoy putting together.

My wife slowed down in Party Lite to focus on our girls as they go through their school years and it has been great to have her home more evenings. BTW, did you know you can now order through her website without having a live show? We passed 16 years of marriage last summer and are heading to number 17 in June. My daughters are FABULOUS and doing well with school, soccer, basketball, and volleyball. My oldest will be 16 in April and she is the BEST teenager ever! I hear people talk about the teen years and moan, but so far they have been the best as my daughter is a wonderful young woman who is responsible, goal-oriented, and a pleasure to be with all the time. My middle daughter is also doing well and excels at soccer and basketball. As she continues to develop and grow I truly think she will earn at least one scholarship for college in athletics. If you follow Franklin Pierce sports you will see her name a lot in soccer and basketball when she hits high school next year. My youngest is a real Daddy’s girl and is my buddy. I coached her in basketball, soccer, and baseball and still coach her soccer team so we spend a lot of time hanging out with each other. She has a real heart for the Lord and is an amazing evangelist who has no fear or hesitancy in sharing the Word! Amen.

Project 365 in 2010

To kick off 2010 and to help me remember this year I am going to turn the focus of this blog primarily into a Project 365 site where I will post a photo a day (along with some thoughts on the photo) every day for the entire year, with most photos being taken by my Nokia N900 device. I will try to actually post the photo the day I take it, but if I am traveling or disconnected some how I may not be able to take it. I will have a Flickr set for this too so I can view the photos there and here on this blog and it should be an amazing way to chronicle my life. You will see family photos, work photos, sports shots, and much more and if it turns out to be as good as I think it will then I may try to do this in the future too.

I will also try to include some other more frequent posts here as well with the focus on my life and not necessarily on the devices and technology I am using.

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

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

Stephen asked the question, “How do we keep the Bible usable as we bump into technology?” He presented a bit of history and where we are at now and then had several slides (that you can see in the PDF document) showing their usability map that captures the demographics of people who read the Bible and then presents a multitude of answers for questions about everything related to people reading the Bible, such as:

• What are they reading?
• How do they annotate?
• What are the physical features of the Bible they read?
• Why did someone buy the Bible?
• Where do people keep the Bible when it is not in use?
• and many more questions…

They use these multitude of responses to try to figure out how to make the Bible usable for people. Stephen said that Bibles should work how people expect. This is the real challenge for electronic Bibles and the different tools we use to read these texts. You can check out the results and findings from their usability study at this site. It is definitely worth a look as it opens your eyes to all of the different situations involved with people reading the Bible.

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

Sean’s inspirations included his past manuscript study methods, treemaps (I found these fascinating and plan to check them out more), and zoomable interfaces (such as Google Earth and the iPhone).

The Zoomable Bible is a spatially-oriented view of the entire text of the Bible. You can then zoom down into it several times to interact with the text. There is also the possibility of embedding images, links, and more into this Bible so that if you zoom in far enough you can access this data. The Zoomable Bible uses zooming and panning for navigation rather than the old ways of interacting such as scrolling and moving your mouse all over the place.

The presentation should be posted on the internet in the near future and I’ll post a link to it here so you can check it out yourself. Here are a few photos of the prototype Sean created.

Almost full view of the Bible

Zooming in on the Book of Job

Zoomed in to read Job by verse

Technorati Tags: BibleTech08

1. Permanence: It is independent of hardware and software
2. Portability: The OSIS-XML format can be used across platforms, including mobile devices
3. Process: Again the open format can be used with different tools
4. Products: You can make products cost effective for the end user

The next speaker talked about a couple of ABS tools, including 28forGod.org and ShareYourStoryNow.org. The 28forGod.org site was created to support the Stand in the Gap 2007 conference in D.C. I actually attended Stand in the Gap way back in 1999 (I think that was the year) where they hope was to get 1 million Christian men together to pray for our country and there were hundreds of thousands there on site. It was an awesome experience and I will never forget it. The 28forGod.org site still works and was setup so that the men could listen to audio of the New Testament and get through the entire New Testament in 40 days. You can go there now and download audio versions of the New Testament.

The other site they setup is Share Your Story Now where Christians can share their inspiring stories of their Christian life with the community. It is great to see some positive news and stories with all of the negative press we are constantly fed and I plan to check it out and read some of the stories soon.

The final speaker talked about mobility, trends in mobility, software trends, personal trends, and more. The speaker was quite knowledgeable about the mobile world and I was impressed. He talked about how we are moving away from the distinction of being either offline or online and moving towards an “inline” life. I don’t know if this is good to always be online, but then again I personally am most of the time unless I am way out in the woods or something.

Technorati Tags: BibleTech08