Mobile Ministry Magazine

In a conversation via Twitter (yes, I know that's a bit of an oxymoron) after yesterday's post, the idea that content needs to be independent was in some respects validated, but there's that aspect of publishers and developer rights that's rarely heard in this discussion. So I asked, what would this question of content independence look like if we didn't just say "we want it" but actually proposed a "how to do it?"

So let's try and answer that. And your feedback is key (especially those of you with some vested careers in this).

Here are some thoughts I have:

• Start with the content that is already within the domain of users (notes, bookmarks, etc.). This content should already be using an XML-based format that is readable in any Bible application regardless of platform (PC, mobile, Windows, Mac, Linux, etc.). This much should be done now. I'd say a commonly supported plugin that any Bible application can use that would unify formatting and content types would be enough for this.
• Concerning those newer translations which are already available in the public domain through publisher agreements (thinking ESV, NET, and a few others); where can open source developers and advocates join together in coding and marketing this raw content to whatsoever persons/orgs need it? In this way, we leverage open source not so much for the cost savings, but for the people-energy that it generates. Allow the push to use the software come from the grassroots angle (small groups, the pastorate, etc.) and then also the bigger angles (software and educational organizations banding together to promote code and/or study camps for example). Use that energy to create points of engagement and interest from those outside of those groups.
• Publishers have a vested interest in keeping their formats licensed, so how about instead of attaching the license to the Bibles, the license is attached to the user(s). Much like what some software companies do, publishers would allow a user or group of users to purchase a license which allows limited usage of that content; and a digital token is given that is simply asked to be reregistered a few times a year at no cost. Publishers get sales and metrics; people get content in as many ways as they can view it.

Those are some of my ideas. What about yours?

Labels: accessiblity, accountability, Bible, content, open source, software, tech

With the new version of the Firefox web browser (v3.5) released today, I thought that it would be great to bring back up that topic of content independence. Specifically, when it comes to reading materials (Bibles, commentaries, etc.), are these items independent of a particular browser or reading application?

I don't know that it is. Sure; there are more powerful and capable devices than ever before. And we can say that there's more digital content out there than ever before as well. But when it comes to moving that content from one device to another (for example from PC to mobile), a lot of times, we are locked into one method and don't realize it until we want to move.

I liken it to many of the desktop-grade Bible applications that are out there. All of them have some excellent content available; however, if you want to take that content with you, for many of these you would have to either purchase an entirely different library (software client and content), or manage some complex tasks before it can even be in a complimentary format.

And I don't want to say it to fault the publishers and developers; truly, they do a great work in building and supporting the breadth of languages, regions, devices, and content available to date. However, I do want to call them to attention - especially in light of the move to users becoming more and more independent of a PC-based computing paradigm.

Content should be just that; content. It shouldn't be attached to the presentation layer, nor should politics allow one silo to have prominence over another. If we are truly looking to good on teaching people to the ends of the earth, at the very least, content needs to be independent of the former ideas of reader/application.

This might look like Firefox, where mobile browsers take on an ability to utilize extensions which enable more functionality (this done at the developer or publisher level). Or this could simply look like more partnerships between publishers, developers, and users towards making content available, and sharing the load for marketing, management, and support.

Whatever is the solution though, I'm not sure that many Bible publishers and software companies will be able to stand pat as they are now: using dedicated readers, coding for specific browsers only, or limiting themselves to policial divisions in the hope of keeping marketshare. If the goal is to educate to the point of making disciples, then the content needs to be independent so that the accountability (individually and corporately) can take the primary focus of ministry activity.

Labels: accessiblity, accountability, Bible, community, content, software, tech

Back in the early times with MMM, we had this feature where you (the reader) was able to submit articles, and then we'd post them. Its been a long time since we've had any submissions, but this is something that I'd like to open back up. Part of the reason is that there are aspects of mobile tech and ministry that we haven't or don't cover enough in depth that you might like to; the other part is that it enables this site to be less-driven by a single voice heard here.

Thanks to the MMM partners who do write in here from time to time. Its a huge help when you come in with posts and have things to say that might be similar to things I've thought, but have a distinctly different perspective. Keep it up (please :D ).

Now, if you want to submit something, then just send it to us. I should mention, not everything sent will be published, and everything that is sent will see a round of editing. Thanks for reading and visiting, and lets open the doors here to those things you'd like to see.

Labels: commentary, content

A previous post about Bible readers got me thinking again about the idea of Bible formats and the fact that content is very much unmovable from one appliation to another. In some respects, I really have won out because with my current phone, even though its not Palm OS, it can use the Bible+ Bibles formatted for that application.

Because of this, there's extra value to not only having a Bible on my device, but the content that I've collected over the years. Needless to say, I've got a ton of Bibles (and other content), and much of that I didn't want to have to reacquire for another application and publishing scheme.

And in previous posts, we've talked about this conflict with publishers needing to (rightly) control the content they make available, and the Bible software developers who make all of our Bible readers possible. I don't want to rerun too much on previous discusisons, but I do want to ask the community here a question:

How important is it to you that the electronic Bibles that you have for whatever application you are using now are compatible with another Bible application you may choose to use in the future?

This is a pretty valuable question. Some don't consider the free or low cost Bibles, but those as well as the very expensive bundles can be very tedious to move from one applicaiton to another. What are your thoughts? And is this something that we should change?

Labels: Bible, Bible+, content, reading, S60 Bible Reader, software

Over at the Digital Sanctuary, a post and conversation has been going on entitled 10 Challenges facing the Church in Cyberspace. Now, I'll not take her points and just reiterate them here. Its better (for our needs) to look at these challenges within the lens of mobile technology and see where challenges and solutions might be a bit more of a behavior change than a technological one.

(1) Accept the Virtual World's significance:
Its not just virtual, its mobile and virtual. Content is not respective of the tool anymore, and therefore the church's response needs to accont for this. Not just a mobile version of a website either, integrating SMS/MMS, and teaching about security and safety online needs to be areas where the church steps into and innovates.

(2) View online expressions of Christianity as valuable extensions of real world faith:
Take this how you want to, but frankly speaking the current and next generations of Internet users are not living two lives (online and offline). The two intermingle and therefore what they do online with faith has just as much importance as what they do offline. In other words, get on their phone and see what they are living out from what you are/aren't teaching.

(3) Embrace the opportunity for Church without borders:
This should go without saying on a mobile site, but think about it. If you are mobile, time and geography are only contexts, they are not content. Learn to get out of the idea of content and context (in terms of location) being the same and see how the Church can and should engage people outside of traditional locations.

(4) Welcome the presentation of God's Word in the vernacular of current culture :
Ok, so we aren't going to be using IM chat in the mist of a service (all the time), but understanding how language is changing within the context of mobile and Internet will help you decode how best to engage people with Christ.

(5) Respond to the globalization of the planet with hope:
Nuff said; its all possible. Let's just show folks how God's folks can bring the hope of the Gospel with it.

(6) Develop and maintain an online presence purposefully populating cyberspace :
How do you do this with mobile? Easy, get out of the house and create a mash up map where you let people know that they can engage you and Christ and utilize healthy boundaries (presence notifications in phones and common sense with people) to emphasize that you are reachable as well as available. Mobile allows this more than any other medium, and its getting better.

(7) Establish virtual outposts for evangelizing, preaching, equipping & training :
Ok, the cynic in me says get a Mobile Web Server and do something fun :) But this is as simple as just making sure that your mobile tools are not just tools for being productive but also an outlet to teach. Our best reference is Inner-Linked; taking what we've learned from using the tech and making a place to teach usability and accountability in the forfront of that use.

(8) Create interactive portals for experiencing Church (streaming media):
This is the same as #6 in terms of mobile. Everything about being mobile is interactive, take advantage of it (as the kids with the PSPs and DS Lites how to do it if you aren't sure).

(9) Practice spiritual disciplines in the global online conversation :
You are not immune from laws, nor can you claim that ignorance is a calling card. From end-user-license agreements, to service agreements, to warranties, to local and international laws, we are responsible for upholding those things that God has allowed rulers to establish. And from there, we find innovative ways to address Christ-less-ness in areas where those laws curtail the freedom to believe on Him. This also includes personal boundaries towards use and being connected; learn how to disconnect and make engaging people the point of mobile tech, not just falling in love with the shiny-shiny.

(10) Encourage strategic investment in the iGeneration:
Donate, set up scholarships for execllence, teach, develop programs, work alongside those that already have programs, or simply just connect with people and families in need to knowing that digital is life-next.

Now, its your turn. Go and teach all, baptizing them in the name of the Father, Son and Holy Spirit. You've got mail to deliever.

Labels: children, church, community, computer, content, culture, Internet, mobile, mobility, stewardship, sustainability, website

For a long time now, MMM has been a site that hasn't exactly taken advantage of services like Delicious and Digg to share content. But, I'm hoping to change that a bit and in effect help make it easier for you to share MMM content.

At the bottom of each post, right under the by-line, is now a button by a service called AddThis. There's nothing spectacular about it, except that it allows you to add MMM articles to your bookmarking service of choice, or even some RSS services, and then you can pass that content around.

Now, why do this you might ask? Every so often, there might be a post that might be worth keeping in your back pocket for reference, or to pass along to someone else. This will make it considerably easier to do so, and helps us figure out what stories you like here at MMM. Given that we post about once a day, things can get lost off the front page pretty quickly, and this will help those posts that are relevant to you to stay up and going.

So do us a favor and share a link or many with a friend. We'd appreciate it, and you'll benefit from the connection made at the intersection of faith and technology.

Labels: community, content, sharing