Posts Tagged ‘definition of mobile ministry’

No Longer the Age of Bible Apps, Now the Age of Bible As Applied

Monday, November 21st, 2011

A friend and I were talking about a project he and his company were working on and while it was great that they were working on it, I had to be direct and ask him, “why are you building another Bible applicaiton?” According to he and his team, having a Bible application would put them on equal footing with other companies in this space who have applications and have (apparently) made the successful transition from a PC-based product model to a mobile/web-based one.

I shook my head at his flawed logic. “You don’t run to where the puck is, you run to where it would be,” I told him (quoting Wayne Gretzky). The problem with their approach, and many within this mobile ministry (#mobmin) space who are looking for their innovative solution to take the religious world/church/tech world by storm, is that they keep looking to copying current products in order to make a dent or shift in perception. That’s just not how this works.

For this group, I asked why didn’t they go the route that other Bible applicaiton companies haven’t gone, but that very few secular companies would dare go: the Boston Globe/Boston responsive web, subscription web approach (several articles talked about this)? He looked at me with disdain, as he heard some about that project, but didn’t know how far reaching that it went. You see, their team is savy enough to build something like that, but their company isn’t visionary enough to figure out why that works.

Hence the title of this article: the age of bible applications is over; it is now the age of bible as applied in digital spaces.

Am I saying that there is no need for any company to create, recreate, or innovate on top of the paradigm of reading, searching, bookmarking, and collections with Bible apps? No. But, I am saying that if you are a content publisher who bases your content on any of those Bible app paradigms, then you are better off pushing your energies towards developing a product somewhere else besides “let start with a Bible app.”

Antoine: you aren’t even a developer, how can you say such things?

Easy actually. Go have a conversation with someone. Tell me, did you start in the Bible or was the conversation dipping in and out of the Bible at various points with other contexts as the backbone to the conversation? I’ll address a recent conversation from a coffeeshop. The pastor/missionary and I started talking because I asked about his wide-margin NASB that he was carrying. The conversation went into church history quickly from that, then into cultural perspectives of various regions of the USA. Would a Bible app have helped there, or an application that was able to search on topics related to church history which also referenced Bible verses, noted authors, theological paradigms, and denominational statements of faith that added context to the situation. Of course, innovation here would be turning on said app while in the conversation and as it “listened” it would pull a Google/Britiannica/Wikipedia/Wolfgram Alpha and search then display all of the relevant content streams, statistics, and opinions available online or in accessible scholarly collections. If you will a Shazamm for Biblical conversations.

It prbably makes sense why I can say that you can bend beyond Bible applications when I phrase the context like that right? But that’s called research and analysis, specifically, anlaysis of cultural behaviors of communication that rarely go into the development of these kinds of applications (this is how reports like Mobile Lens 2011 were framed). And that’s why we end up with a situation such as what I described with my friend at the start of this article. If you want your product(s) to be of earthly good, then you have to move beyond the age of simply offering just the text. Develop an app that engages the application of Biblical (religious) knowledge first, and then grounds the user in a growing (maturing) understanding of Scripture, church history, and culture as they grow in faith and knowledge.

Anyone want to bet on “Bible as Applied” being the space in which faith-based/religious apps show the most potential for growth in the coming years against simply offering the text in increasingly siloed services?

 

Understanding and Differences Between Internet Ministry and Mobile Ministry

Wednesday, November 16th, 2011

Am writing this a few hours after listening to Dr. Markus Pfeffier from Regent University give a talk on the implications of the Internet and virtual environments. Much of this talk I’d already known, but both the speaker and audience were more unfamiliar (association and generational differences). As I listened, I wrote a bit of notes on items covered and not covered and realized by the end that much of what has been, and will happen, when mobile is added to the list for many of you, is that you will draw mobile into the same body of work as you do Internet ministry activities. There is some overlap, but not quite the same.

Let me summarize by restating the tweets (@mobileminmag) that relate to this point published before the writing of this piece:

This morning, listened to chat about the 6th mass media (web) & the need for a ministry response; good to hear others in this space…

Despite talk, still feel that simply shooting for web and social media is a miss for all but a few economies & generations, mobile is better… Mobile includes what we know (& are learning) about Internet as media/medium. Some of us would be good to skip to mobile, then bridge back…

For many, Internet ministry is stuck as a visual/screen ministry; mobile by nature moves well beyond that to spatial experiences… When media moves beyond screen, we get audio, behavioral (gesture), & even potential for smells to augment reality of faith experiences… But, to think like that means you need to know how your biological body functions; that’s the key to understanding mobile… Remember, currently the reach for mobile (individual accounts) is just under 4 billion; reach for net is 1.2billion, unique cross-overs here… But that’s just numbers, mobile = personal = accountable, Internet doesn’t do that w/o analytics, tracking, or optional disclosure…

So, depending on how you see ministry = discipleship, that accountability piece plays a huge factor into where you put energies/resources… If ministry = broadcast then teach/disciple, Net is nearly perfect for channel… Then, net ministry should embrace what makes it unique for the effort… to whom it’s most suited for.

Yea, that was a lot of tweets. And if you saw that stream in the middle of it going up, things might not have made as much sense. But, now looking at the whole statement, we can start to draw some of those needed conclusions that lend towards understanding both Internet and Mobile Ministry efforts.

First, know that there is already a Body of discussion happening about Internet and mobile ministries. Web efforts such as Internet Evangelism Day, Jesus.net, eDot Geek, ministries such as Every Student, Cru, and LifeChurch are some of those voices, and associations such as GCIA, ICCM, the Center for Church Communication, and Catalyst do a great effort towards enabling and facilitating the discussion about Internet ministry (evangelism, marketing, discipleship, etc). On the Mobile Ministry side, there’s MMM, IE Day, Cybermissions, Mobile Advance, and the groups partnering within the Mobile Ministry Forum.

Second, Internet and mobile ministries are subject to cultural, contextual, and generational differences. I don’t subscribe to the terms digital native/digital immigrant (mainly because there is no validated research to prove it, and it’s an assumption based on 100% equal access and ability which is totally not the case). I do subscribe to the differences which can be and continue to be understood when we look at economic class, gender differences, cultural transformations, urbanization/environmentalism, commodities management, change management, and other social sciences which tend to do a decent job of describing the differences that lead to our different uses and applications of communications technologies (yes, that’s supposed to be communications with an ‘s’). You have to understand those pieces in respect to the unique qualities of Internet or mobile. Generally speaking, mobile builds on what you understand about Internet when viewing both as participatory/event communication mediums. Trends point to being able to understand this data, then creating the avenues for appropriate products and services to be developed/enhanced.

About Internet ministry being visual: I am being mean, but truthful. Curent Internet ministry efforts start with visuals. This is either the readability needed for engaging in text-driven Bible apps, social networks, or multimedia streams (ever wonder why audio ministries rely on you needing to read text to download an audio message), or the implementing of the structures which foster digital story creations. Unfortunately, this leaves out those who might have access, but cannot read. Or, leaves out those who don’t have access because they don’t have the terminal with which to engage Internet-first ministries. Mobile, being that it has built on the Internet as a participat-media channel, does much of the same. However it’s not, nor should it be limited to visual-first efforts. That’s worth another article to dive into. But it starts at a basic question, whom are you limiting access to the Gospel to because of what you know or don’t know about those who touch that channel? And if you are going to go visual, at least follow accessibility best practices for the web.

The global reach for mobile is currently almost 3x that of Internet. The purchasing power of mobile is collectively greater than that of Internet. The logistical savy of Internet-based efforts is more mature than that of mobile, as are the tools, services, practices, and standards that make those happen. This means that specific engagements on the Internet have a better chance of success towards some groups more than others. However, you are limited by being online. Unless the effort starts online and is able to get offline, it can only have an effect in that virtual space (the Kiosk Evangelism Project, Door 43, and Open Church projects actually seeks to address this specific limitation/opportunity of Internet efforts).

Therefore, how you (your culture, your generation, your bias) defines minstry will determine how Internet or mobile ministry can play a part in your efforts. It’s possible to do both, but not possible to pigeon-hole yourself so long into one that the other isn’t relevant.

Taking from Dr. Pfeffier and Tomi Ahonen, Internet is the first participatory mass media in the history of humanity (you can argue the performance stage was its precursor), mobile is the second. What Internet ministry cannot do in terms of personalized (not algorithmic) attention, mobile can. What mobile cannot do in terms of being standardized across every device, Internet evangelism efforts can. They aren’t the same. Yet, in order to see digital spaces here and beyond (augmented reality, virtual reality, and cybernetics for example) as opportunities for ministry efforts, knowing this is key to making the most of your time and resources.

 

Charting an Efficient Path Thru Mobile Ministry Initiatives

Tuesday, October 25th, 2011

Mobile Ministry Mindmap Segment - Share on OviOne of the ways that MMM has been able to help organizations is in respect to breaking down and rebuilding points that influence mobile and other parts of communication events. We do this in part by working every communication issues thru a methodology born out of how we look at the layers of mobile: devices, services, and experiences.

Devices

Devices are agents and windows. What is most important to them is that ability for anyone to use devices for their most efficient and effective communicative purpose. That means that handheld mobiles (PDAs, phones, media players, etc.) speak towards a context of communication events that other mobiles (tablets, laptops, etc.) might not. Knowing the built in abilities and the perceived biases people have towards these gives one layer towards efficien communication. In a very real sense, if you don’t know the device’s abilities, then not much else matters for mobile ministry initiatives.

Services

Services are enablers. Look at services as a channel towards that expected end. They can exist in and of themselves, but the devices and experience design constrains their relevance and effectiveness. What’s usually the challenge here is knowing the bounds of the service inside of your communications needs, and then if it scales with the organic nature of communication behaviors. If it scales, or constrains, favorably, then the chance of a service becominng an integral part of your effort grows. However, service relevance is important here; what’s relevant to the IT administrator is not relevant to the stakeholder (except for cost and time to implementation). Don’t get trapped into making the more important than the other layers, don’t miss that it needs to be working for the Experience layer to be met positively.

Experiences

The Experience layer can be summarized by simply stating, “what are your goals?” Why is this technology, behavior, initiative, or function important to the overall mission of the organization? Is it an experience that is going to govern how others perceive your mission, Christ, etc.? What is the goal of the media transferred to the device? Can that media meet that goal, or is this a matter of planting and watering so that something later can manifest? Are you reaching too far trying to drive the experience? Or, are you not reaching far enough? Once that experience happens, are the persons or their devices evangelists for you, Christ, or something else?

Answering these three layers allows you to chart a path to a solution that’s more efficient than it is amazing. Sure, mobile ministry endeavors want to always “reach the world for Christ.” But, the reality is that the reach of any effort has constraints that you have to identify and then play within. If you will, the path is more narrow than wide, and your efforts have to respect those constraints to see the nets filled.

 

The 10 de’s of the Bible Also Describing Mobile

Monday, September 12th, 2011

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)

Wednesday, May 18th, 2011

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)

Friday, May 13th, 2011

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.