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 (<250 people) and have similar contexts (cable channel access, many mobile devices, need to provoke greater involvement from community, etc.). Couldn’t this work for you? And if it couldn’t (because there’s some unspoken rule about using the latest greatest cameras/tools/tech, this is just not normal, we don’t have money/resources, etc.), then why?
While it is good to get the perspectives of going mobile or web with Bible reading, sometimes it’s better to get a view of the implications of the introduction of those technologies from the more tradition end – starting first with the print (paper) Bible, ad then seeing what kinds of technologies can be grafted onto there. If done well, it can be an enhancement. If not, it could end up as just one of those features that’s great for conversation and little else.
Over at the NY Times, I took in a reading about the 
There’s some sense of disbelief across mobilists, developers, theologists, and just about anyone else when I describe to them 
This past week, I was asked to be a guest on the 
When I speak with people about MMM, some people ask about Bible and religious-based applications. What’s always neat is when after offering their opinion about what it is they are/aren’t using, I ask them what would be their ideal application. Interestingly enough, the answer to this always sounds like some aspect of faith digitally applied rather than faith-knkowledge retreived from somewhere (the paradigm of Bible apps).
Continuing on Resolution #4: Raising the Bar on Mobile UX Standards
Sunday, January 22nd, 2012With that starting point, we want to highlight a bit more about Mobile (UX) Standards and in referencing that All Books Project, and some of the items to keep in mind whiile moving forward in your mobile initiatives this year and beyond.
Mobile UX Standards
It is assumed that the idea of what makes for a great mobile user experience is pretty easy – just grab yourself an Apple iPhone and use it for a week or two, then switch to another platform for the same amount of time and note how often you frown, toss the device, or find yourself limited in some fashion. And while we can agree that Apple’s iOS platform does make for some suitable claims towards what makes a good mobile experience (consistency, quality, variety of applications, etc.), its not the only mobile experience, nor does it answer every question anyone developing, selling, or using mobility will ask towards.
Over at UX Mag, an excellent article talking about mobile standards beyond the styleguides, frameworks, and guidelines that would usually reference as we develop apps makes an excellent point:
*List formattting added
Beyond simply saying “we want to go mobile” or “let’s use this or that to go mobile,” you really have to ask core questions about the interaction and steer adamantly towards those goals. What happens when you don’t steer specifically towards the goal, understanding these kinds of questions throughout, is that you end up with a glut of features, conflicting brand messages, dis-engaged users, and missed opportunities to deliever the depth of the Gospel that you/your group intends that application or service to portray.
Start With A Picture, Ask Until the Ink Dries
With the All Books Project, I started with an idea in my head (more efficient Bible reading on my personal mobile device that wasn’t limited to closed-licensed texts), and started scraping together what was needed and what wasn’t in order to make that happen. I boiled things down to two features: reading and searching. And then I took to one of my favorite apps on my iPad (Tactilis) to sketch some reasonable ideas towards how I would get there.
This UX flow document is my gage of whether I’m meeting my goals. If I am, then the lines here continue to make sense. If not, then I go back to this document towards what I (originally or later modified) thought and ask whether my thinking should continue down the path I’m or, or get back on course to what was drawn.
One of the pieces of interaction that I’m aiming for with All Books is a sliding popup for when I click on those verses with footnotes. The feature is harder to implement than its drawn. But, because I’m clear towards what I want to do when the popup is envoked, how its interacted with, and how it is dismissed, I can keep my programming focused and timelines (generally) well kept.
A Good Mobile UX Is Also Your Feedback Loop’s Process
In designing an effective mobile user experience (UX), you also need to take into account the development/design of your support infrastructure. As we talked about once before when developing mobile web apps, you need to have in place the resources not just to build the app, but to support, maintain, and maybe even update it.
Build, Get It Out There
After I was able to figure out my issue relating to displaying content within All Books, I needed to start using it. It didn’t matter that there was (noted) performance issues or the inability to see the footnotes as I’d like. Getting it into my normal use allows me to catch things that I’d not considered in my initial development and design, and then adjust on the fly without effecting other pieces of the project. For example, I realized that for all the work I did with makng this a spatially-orienting design, I still felt lost when navigating. The insertion of colored indicators on the section that I was within helped this considerably, and it was a few lines of code to add to do this (1 CSS class and 1 JS statement).
With that: do you have your mobile UX resolution refined now. Its the middle of January, don’t let too much longer go by.
Tags: Android, APIs, Apple, applications, best practices, bible applications, BlackBerry, CSS, HTML5, iOS, Mobile in Analytics/Development/Marketing, mobile in development, mobile in moment, mobility, native apps, services, standards, Symbian, tech, Windows Mobiile, Windows Phone
Posted in Commentary | No Comments »