In a lot of respects, its rare to talk about Bible apps for one specific platform – there so many – the causality of Bible apps for the Symbian platform has been one of those questions that has gnawed at me a bit. Not so much even for the lack of applications, but the missed opportunities because of where the Symbian platform has been represented.

What is Symbian?

Symbian is a mobile operating system and platform that’s been used by Nokia, Samsung, Motorola, Fujitsu, and LG for mobile phones. To date, there have been over 600 million devices shipped and sold with the Symbian operating system, making it one of the most prolific  in use.

Nokia has been quite adept at making Symbian fit its needs. It has pretty much been selling Symbian devices longer than people have given credence to there even being a category called smartphones. To that end, Symbian has been deployed with more carriers and in more world  regions than all but the most basic of Java handsets.

Unfortunately, it is also considered an older platform that while stable and optimized for mobile devices, falls quite far behind some of the newer entrants in respect to ease-of-use, developer tools, and ease of finding applications. And so Symbian recently befell Nokia’s reorganization efforts (first spun into an open source platform, and now to be greatly minimized  over the next years  to be replaced by Windows Phone).

Symbian and Bibles

By accident of niche, Biblical software usually is a fairly easy one to fill. Find a publisher that has the languages that you want to address, write the application to deliver it, and then make it available. The issue with Symbian is that its actually a pretty difficult platform to build on. Without getting too technical, its just plain to say that developers have needed to had a certain type of older technical knowledge (previously) or invest in toolsets (Qt, Java, etc.) which required a good amount of patience before progress.

When I moved to the Symbian platform in 2008, there wasn’t much to find for Bible apps. Laridian, Olive Tree, Symbian Bible, and Go-Bible were pretty much your only options. And for a while, this was just fine and covered most of the Symbian devices that were in existence. When Symbian went to a touch-based user interface (UI), things got a lot fragmented, and Symbian Bible pretty much became the only option (Best eBible came on the scene later). Which was good and not good – a free application, using Bibles formatted for the Palm Bible+ application, and had no support for newer translations. Newer platforms ended up with a very easy “in” for adoption, they had what people could read, and could find.

A Missed Opportunity…

In light of all of that history, its easy to say that Symbian (and the companies associated with that platform) might have missed an opportunity to take a platform that has already made considerable inroads even further. But, it had a good bit going against it, and so it is now in the position it is in.

But does that mean that all potential opportunity for this platform have been lost? I’d say no, if technical aptitude is seen as a gift that can benefit the Body. When I say technical aptitude, a platform (like Symbian, but all qualify here) benefits by such knowledge as developer tools, device interfaces, language mapping, usage analytics, etc. A person who is skilled in any of these areas would be a suitable team member for a larger project creating an application, service, or refining a digital faith experience. These persons have to be looked for in “not normal places” as their gift isn’t something you’d find in Exodus on the way to creating a mobile altar (Exodus 25-27).

There’s also the benefit of much of Symbian’s assets being made available in open forums (for example Forum Nokia), through some open source technologies (for example Qt), and through the continued ownership of Symbian devices (installed-based analysis by Vision Mobile). In effect, there’s a lot of folks out there who can still benefit from a Bible solution on this platform.

The Lesson for Other Mobile Platforms

It is easy for the market, and popular (loud) opinion to state where you should place your development resources. Certainly, making plans for mobile software you’ve got to take into account devices, services, and experiences (the entire frame of mobile) and what is currently and what will be in the years to come.

When it comes to religious software, you also have the opportunity to always tap into the installed base of current users. Many times, your frequent fans and users of digital faith items will not splurge on the latest devices or services, though they will want to receive some of the same experiences that newer devices offer. It is in this that the opportunity lies, and where its possible to not just make a product, but help drive older platforms to a friendlier sunset.

Currently, there are several mobile platforms that have come and gone (Epoc, PalmOS, Windows Mobile), and some that are pretty much on their last legs (Symbian, older versions of Android and iOS, RIM’s BB OS 6 and earlier). Developers looking to cut their teeth on a mobile platform to learn and to provide experiences should not forget these platforms. And at the same time, you should go into any project with a clear (and simple) goal and definitive timeline. You  will not be able to support those devices for very long when the official support has faded.

Lastly, when you are a platform that has cultured a community of content, but you are no longer able to support that platform, utilize the open code and support communities of Code.Google, Forum Nokia, SourceForge, GitHub, and others as places to put your code and release notes. There might be someone willing to take up the project, or at least help you migrate your project’s contents into a newer platform. For example, MMM participated in an effort to update the Rapier Bible application for Maemo 5 devices, fixing some linger bugs, but that also set the stage to develop (and later release into widespread testing) a Bible application written in Qt from the ground up called Katana. The rewritten application leans on lessons of the former, but has a much longer viable life because of decisions made early on to support certain content and programming hooks.

For Symbian, it may very well be the case that the sun is setting for it as a leading mobile platform. It is also the case that there are some years and various regions of users that still haven’t been served with digital faith content though having a platform capable of supporting it. Do keep that in mind as you consider your mobile strategies, and remember to study the past platforms for what is probably going to happen to many others in a nearer-than-you-can-expect future.