Mobile Ministry Magazine (MMM)

Posts Tagged ‘mobile in media’

story4all – Heart Languages and Faith by Ears

Monday, January 23rd, 2012

story4all (logo)Last week, we spent some time with Renew Outreach talking about missions in remote areas, literacy, and how mobile is making its way into these very unlikely environments profitably for the Gospel (we’ve got a bit about those folks coming). One of the groups tossed out during one of several conversations was story4all, a podcast-based Christian media group which uses audio streams in the heart/native language of those being preached, spoken to.

A bit more about them from their website:

…We believe deeply that the Message Jesus delivered was not only brought by Him “wearing our skin” (becoming like us and embodying the Message), but it came in a style best understood by His audience, and in a language of the heart.

It has been estimated that only 8% of people living in Israel during Jesus’ time on earth were literate. However, He came and taught everyone (literate Pharisees, etc., as well as the mostly non-literate populace) through the medium of stories. Mark chapter 4 says “He was never without a story when He spoke”. Jesus saw fit to deliver truths to the literate and non-literate alike through the medium of stories. He demonstrated through this that to be effective and to promote recall in the minds of those who hear, most of our communication should be housed in stories.

Ironically, 90% of all Christian ministry today occurs through literate communication styles…

For those of you who’s mobile and ministry pursuits need to start with audio stories (not visual stories), story4all seems like a great place for connection and content. Check out their website and subscribe to their podcast RSS, iTunes). You might find that the heart language they speak, also ressonates with the faith that you aim to share with others.

 

Splashtop Remote, Bible Library Servers, and Mobile Accessibility

Friday, January 20th, 2012


Last month, we had a post from LaRosa Johnson talking about his new Asus Transformer Android tablet computer and how he planned to use it work and Biblical studies. Of the latter, he was doing something pretty neat in that he would use the tablet to remotely log into his laptop to be able to use the desktop Bible software packages that he has there. We’ve found another example of this over at Biblical Studies and Technological Tools where instead of a tablet, we’ve got an Android smartphone, and the software being used is SplashTop Remote Desktop. Here’s a snippet of that experience:

In the past I have used Logmein for remote access to the various family computers I maintain. Even the basic free account lets me take over a computer and run programs on it. It works great and is secure. I will continue to use it for such maintenance tasks. Note that this can work the other way around, and what a program like this allows me to do is run programs that are on my home system from any other computer. As long as I have my home system on and Logmein enabled, I can remotely connect to my home system and use my installed programs like BibleWorks or Logos. I’ve also used it to grab files I’ve forgotten on my home computer when I’m at school. (I now use SugarSync to keep my systems all in sync via the cloud. It’s a wonderful thing.) It’s a little slow to use Logmein this way, but it works. What this also means is that I can use the web browser on my smartphone and see BibleWorks on my phone. I say “see,” because without the use of a mouse on my phone, I really can’t do too much. Logmein does have an Android app ($29), but I just don’t use it that much, especially on my phone, to buy it.

Read the rest of BibleWorks and Logos on Android (sort of…) at Biblical Studies and Technological Tools.

Now, this sounds like something that would be only useful in areas where wireless bandwidth is accessible and there’s some technological savy on the part of the person putting this together. But, I can’t help thinking that at some level, it would make a lot of sense to see something like Bibleworks, Logos, etc. offered in a “server package” where you purchase “seats” and those authenticate mobile devices are able to use it. This would be no different than what we see with CRM, task management, Intranet, and office productivity suites (Salesforce, Basecamp, SharePoint, and Google Apps to name a few).

A difference in the application here though would need to be that Bible software suites doing this would want to explore being usable in different streams. For example, something like having the BibleWorks install and UI sitting on a Seagate GoFlex Satellite, with anyone accessing that hard drive/access point being able to “see/read” BibleWorks on their device, but it is being served from that single point. There’d also be something like Logos’ Biblia that could be explored where a license for an organization could make available to authenticated seats some measure of the Logos library. Or, finally we could see the BibleWorks/Olive Tree/Logos/etc. move to a model of use where instead of purchasing and downloading a product, that people and organizations purchase access to a virtual desktop of sorts which would allow them (a) access to the library and (b) multiple devices which can access it per use account. Now that I’m thinking about it, it would be really neat if I could recreate the mobile web server and then host the bible project I’m working on from it… uhmmm

In whatever case, its pretty neat to see these kinds of access choices taken when it comes to Bible software. We shouldn’t limit mobile just to “what’s designed for the small screen” when its clearly possible for that small screen to access a bit more. What is worth being explored though is how we can better enable mobile to be a key to a content library, whether or not those with the devices have the financial means to access the content or not.

 

A MobiMedia for Churches Idea

Friday, January 13th, 2012

During my vacation (last week of 2011), I visited the church my best friend attends in PA and got a chance to meet the elder in charge of operational items for the church. My bro plugged me and what I’ve been doing with MMM and we got into a quick conversation about the church’s move into TV/broadcasting that they expect for this year. In listening, I started to ask why they are looking to go broadcasting, but changed my question to something a bit different. This is a paraphrase of what I proposed to him:

A TV/broadcast ministry for the size of church that you have will need probably about 5-6 dedicated people. You’ll want 2 camera persons, a video tech, a sound tech, and then a production manager to keep all of those together. You’ll probably need to have one of those persons, if not someone (or 2) else to take the content and do any further graphic/sound editing to the final product. And then there’s likely someone on that team, if not another team entirely that is going to be responsible for putting it on a website and making it “press ready” for other local stakeholders who’d want to rebroadcast it. That’s a lot of folks. 

Many of the members have mobile devices (feature phone, smartphones, and tablets were all visible during the service I attended). Why not create mobile media (mobimedia) teams in which people can sign up and do one of three things: recording video, recording audio, and taking still pictures. Ideally, you’d want to make sure that you keep the groups mixed so that the devices are being used within their best capacity, but then you end up with the people who are part of your community, giving a view of a service or event from their perspective, not just the one that’s most camera friendly.

You would then have just two positions to create for the community: a production designer/manager who would be responsible for taking all of the content from the devices, and then creating the “official” video that goes public, and a public relations-like person who would field questions/comments from the public/stakeholders.

When I proposed this to that elder, it was like a light bulb went off. He never considered that (a) the normal design of doing multimedia would need so many layers of people and processes and that (b) it would be possible to include the community in such a way that they’d have a greater sense of ownership of the community and the preached Gospel message.

Now, there are a few things here. You aren’t going to get RED camera quality video or Dolby quality audio from everyone’s mobiles, so you’d want to make sure that you have some kind of grid that would allow you to see the quality of video/audio/stills so that you can organize your teams appropriately. Then again, there was this movie shot entirely on a Nokia N8, so quality isn’t really a question right?

You’d want to make sure that you design a policy that allows people to keep whatever they record, but with the statement that if they make their’s public that it cannot be considered official content from the church. So, you might have a Flickr/YouTube gallery that they would all upload the pics/videos to, but then have something of an official “set” that becomes the public-facing gallery. You’d also have some streams for training that would have to be taken up. For example, you’d definitely want to do a workshop talking about how to best take photos/videos during a service (mindful of flash, camera sounds, zoom, etc.). There might only be a few folks who can do this well in your churches now, but what if that few turned into a few folks from your teen, college, and senior ministries? Considering that many mobiles really are just fine in doing this, these are the kinds of thoughts you’d want to have going into it.

I’m of the opinion that mobiles and people are ready for doing this. But, if I’m to pull this off, I’d have to start a church or something to prove it (uhmmm, the people formerly known as congregation) or just point to those folks already doing it in similar genres (Mobile Media Toolkit, hint, hint).

So, now I throw this one out there to you. Some of you are in churches of similar size (

 

2012 Resolution #1: An App is Not A Strategy

Monday, January 2nd, 2012

Welcome to 2012 and Mobile Ministry Magazine (MMM). Since 2004, we’ve talked a lot about this intersection of faith and mobile technology and how this has often looked like applications. We’ve talked about the good and bad about these applications, what has improved, and what still isn’t being touched. And yet there’s there is a pervasive resolution that I think you should endear to any mobile ministry efforts for 2012: an application is not a strategy.

We’ll summarize how we come to such a conclusion in this article. Some of these concepts have been covered before, other parts not yet in enough depth to give you a means to continue. But don’t worry, as we encourage you to step into 2012 with your mobile ministry efforts, the goal of this article is that you address mobile ministry as a spoke in a larger wheel of your efforts, no matter where you are in the chain.

This article focuses specifically on these points:

  • What is Mobile Ministry?
  • What are the specific areas in which mobile has addressed a ministry context?
  • Is there anything consistently applicable across those areas of mobile ministry?
  • If applications are part of the solution, what else is there?
  • What are some resources for applying these points?

What is Mobile Ministry

Mobile ministry is the application of mobile devices, services, and/or experiences for the purposes of forwarding ideals and characteristics of a faith movement.

Mobile computing has a market-led definition (portable, cellular and/or WiFi-enabled computing devices which have screen sizes between 2.2 and 5in, and have some form of primary input that is not mediated by accessory-attached mice/keyboards). We take the stance that mobile computing devices can include any portable computer that is not designed specifically as a clothing accessory.

Mobile services include, but are not limited singular applications of cellular (voice, data, SMS, multimedia), Internet (browsing, email, IM, VoIP, Wi-Fi, GPS), and applications (including the tools to create and distribute, API structures/protocols, development standards/practices, etc.). 

Ministry is defined as any activity which forwards the ideals and characteristics of a faith movement, that may be personally motivated, community organized, and/or governmentally implemented.

This definiton is intentionally not grounded on any one religion/faith, and has been [slightly] refined from its more academic-correct beginnings. Discussions towards refining this further should be a part of any conversations brokering mobile as useful in ministry contexts.

Specific Areas of Ministry Applied in Mobile
Over the course of seven years, MMM has observed six specific applications of mobile technology within ministry contexts. This doesn’t mean that there are not, or could not be others. Within these six areas, we have identified unique approaches combining devices, services, and/or experiences which create avenues for personal, media, and cultural transformation through faith-binding activities.

These six areas are as follows:

We will further define and illustrate these areas throughout 2012. Please refer to former articles and presentations on this subject in order to see some of the progression of these ideas. We will endeavor to link to articles tagged with these topics in order to best consolidate the discussion on this site towards these points.

Layers of Mobile
We are careful not to simply define mobile in the context of devices or development. There are three components which encompass the mobile environment which all need to be considered and included within the context that is mobile computing:

  • Devices
  • Services
  • Experiences

We will further define these areas beyond our initial exploration of these throughout 2012. Please refer this article/document for a direct linking to that discussion.

Applications and Beyond
It should be clear within what we’ve explained so far that defining mobile ministry strictly or specifically in the context of downloadable applications is incomplete. Applications are only a part of the usable toolkit for mobile within ministry endeavors. Streams in which mobile can be developed/sold/applied within ministry contexts include:

  • Software Applications
  • Hardware Applications
  • Voice Services
  • Video/Audio (Streaming, Downloads, Sharing, etc.)
  • Text (SMS, language transcription, etc.)
  • Downloadable/Streaming Media (APIs, content libraries, etc.)
  • Mixed Media (creation, distribution, specifications, etc.)
  • Security
  • Reporting
  • Personalization

We will further define these areas throughout 2012. 

Resources for Moving Forward

Conclusions: An App is not a Strategy, But…
We will not debate the point that for many endeavors, the first door that mobile will open is that through an application store. However, the first door seen is not the only door available. Depending on what it is you are developing, offering, or enabling, an application might not be the best point of entry. 

For 2012, consider your opportunities and challenges within ministry, and whether mobile is the best route. If it is, then you will want to start looking at where you sit in terms of those areas of mobile, and then whether you are targeting devices, building a service, or managing an experience. After that point, it becomes clear how you should approach mobile. It may very well be that you do need an application – but now it will have a specific target, you can begin planning and setting up your team and content appropriately. If it means you need to outsource the development of your mobile solution, you do so with knowledge of more than simply “make it work on this device.” 

At the intersection of faith and mobile technology, what are you pointing towards? In 2010, don’t let your strategy (or lack of one) turn mobile into a dead-end for your effort.

 

Mobify empowers marketers and developers to create amazing mobile web experiences. Tap to learn more

Mobify