The 10 de’s of the Bible Also Describing Mobile

hourglass by Dave Hayward-Naked Pastor, via FlickrToday, it seems a foregone conclusion that mobile (and what mobile connects you to) disrupts life. But, before mobile became something easy to see, you can imagine the fun we had in talking about its disruption. If only we had Naked Pastor’s list back then:

  1. de-stabilize
  2. de-nationalize
  3. de-centralize
  4. de-culturize
  5. de-colonize
  6. de-religiousize
  7. de-textualize
  8. de-intellectualize
  9. de-theologize
  10. de-spiritualize

Check out Naked Pastor’s post for the definition of these ideas. And then consider this:

every change in communications technologies has also reset the actualities and expectations of the relationships we have towards one another and the industries that broker our relationships

Mobile is more than just a channel. It a reseting of the description(s) of realities that are relevant.

Image from Naked Pastor

Mobile Ministry is More Than Devices (Part 2)

This is continued from Part 1, posted previously.

Nokia Astound at Caribou Coffee - Share on OviI mentioned earlier that the services layer is where we’ve seen the most work happen in mobile ministry. Part of that is because of the maturity of that layer, the accessibility of that layer due to (simply) the existence of the Internet, and the (usually) generous offering of compatible APIs between services and some families of devices. This allows the ministry/organization/individual developer to focus on making sure things plug together neatly, and they can put more energy towards the experience that is to be gained from using their application.

But what if you want to focus on the device layer? What are you in for? Let’s just look at a few device platforms that you could support:

  • iOS (Apple)
  • RIM (BlackBerry 5, 6, and 7)
  • Android (1.6, 2.1, 2.2, 3 (Honeycomb), and now Ice Cream Sandwich which has no version number and spans several device form factors both mobile and not)
  • Windows (WM 6, 6.5, Phone 7, and Phone 7.5)
  • Nokia (S40, S60 Feature Pack 2, Symbian^1, Symbian 3, Qt 4.5)
  • Brew (incompatibilities across carriers)
  • HP (WebOS 2, 2.1)
  • Samsung (Bada, Bada 2)
  • And several mobile devices which use proprietary OSes that cannot be developed for directly, but are sometimes enabled on the carrier-level for some services (see the graphic in this Vision Mobile article for details)

And that’s just what I could name off the top of my head.

You can’t focus on the “mobile = devices” meme. You can’t even let that maintain more than 1/3 of your thoughts on mobile. When you do, what happens is that you start to make smaller the addressable persons who would be able to successfully utilize produced content, or even enable them to produce content for themselves.

Let’s say that you want to focus on the services layer. What are you in for here? A small list again:

  • WAP
  • HTML (4 and 5; devices support different and mismatching pieces of these)
  • SMS (MMS, shortcodes, carrier-specific rules, analytics that matter, etc.)
  • APIs to default applications (requires platform-specific SDK)
  • APIs to web services such as Facebook, Twitter, etc. (read the terms of service for what you are able to access and what compromises you or consumers might have with these).
  • Content Management Systems

Again, just a few pieces. But you can’t just say “go SMS” and not also be cognizant of the fact that SMS broadcasting rules are different in various countries/carriers. You also need to be able to scope carefully what your entire workflow will be for that communication from the creation of the message, to what happens with the data about that consumer, to expectations for them and your organization.

I’d go into experiences, but you might be getting it now – you can’t just think about mobile as some isolated channel. It isn’t isolated, and the entire mobile definition is predicated on the synergy of devices, services, and experiences.

The potential of mobile is that there are 5.3 billion accessible persons who can be touched in some way by a carrier of the Gospel. The realistic assessment is a lot smaller, and requires more than just a passion for the theological command. Our passions also have to account for the ability to get to the message in an accessible manner. That’s more than a device. And ultimately, it requires us getting on a deeper level than the channel itself.

Mobile Ministry is More Than Devices (Part 1)

Nokia Astound at Caribou Coffee - Share on OviIt is clear in several conversations (online and offline) that mobile ministry is one part understood for its potential, and another part misunderstood at how mobile can best be applied in ministry contexts. I think that this opens a can of beans by stating it like this, but its better that its just stated now since mobile ministry is still at its infant stages.

(Refined*) Definition of Mobile

Communication and computational events facilitated through the use of handheld devices which expand personal contexts to mediated and shared life experiences.

(Refined*) Definition of Mobile Ministry

The use of, and application of devices, services, and experiences classified as mobile to experience the fullness of religious faith traditions.

*Both of these refined definitions were taken from our GCIA 2011 Presentation Deck; you can refer to our other discussions on the definition of mobile ministry by using the tag reference to our articles on this subject.

There are a few pieces to note within this definition key to my position on this. First, mobile isn’t about having a certain kind of mobile device. Mobile devices are considered to be any computing device that is portable. That means laptops, tablets, PDAs, phones, music players, personal media players, gaming systems, and even calculators are mobile computers. What you do with them doesn’t yet drive the definition, these are all devices which process several types of input and output another type of data without physical tethering by either the user or the computing device.

Next, there are three parts of mobile which aren’t exclusive to mobile, but do drive the understanding towards how to proceed forward. Mobile is made up of three layers: devices, services, and experiences. Devices include all of those which I described in the paragraph above. However, when you hear “mobile devices” in marketing and similar communications, it is implied that you are speaking of computing devices that have screens between 5in and 2in in diameter. This doesn’t mean that other devices aren’t mobile, only that the marketing term for mobile has been constrained to this type of device form factor only.

Portable devices without a screen that also facilitate computing-style interactions are also mobile computers, but again, marketing or functionality determines their name, and therefore their perception. This includes how we think about portable computing devices for those with disabilities.

After the idea of devices, we have services. Services include those applications, wireless networks, applications (and their frameworks and development tools), and those tools of analysis and monetization that enable the devices to perform/facilitate communications or describe/analyze events. On this layer you have the fun of mobile platforms, cellular frequencies, developer tools, regional idiosyncrasies towards using a device (SIM, no SIM, MVNOs, etc.), SMS, etc. It is in this layer that much of what has happened to date in terms of the application of mobiles in ministry has taken place.

Lastly, you have experiences. Experiences include “soft” aspects of mobile including design, marketing, intended effects (education, salvation, discipleship, etc.), and the environments effected by mobile (politics, psychology, theology, etc.). The experience of any mobile device, for example, how hard is it to call up a verse in the Bible when listening to a preacher, overall determines how we judge the device and service layers of mobile as an entire experience.

One of the many difficulties that organizations (not just in terms of digital faith) are having with mobile is that they are letting the device layer direct the application of mobile to their intended audiences. Unfortunately, when that happens, especially when you take smartphones out of the equation, is that the development of consistent experiences and integration of services becomes very difficult. Engaging any mobile audience requires a clear understanding of how these three layers are going to be effected, and decisions need to be made very early in the process as to what layer you will most focus on, and how you will craft your expectations around that layer.

This continues in Part 2 next week.