Mobile Ministry Magazine

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