Mobile Ministry Magazine

Do any of you who are teachers, pastors, etc. utilize websites to share information about your taught content? If so, what services do you use and why?

Labels: teaching, web application, website

Saw this some time ago at AnthonyCoppedge.com - a new service called MinistryGive that enables people to give to ministries/orgs via a website or mobile device.

This seems like an ideal solution for a lot of giving campaigns, or even as an additional "offering line" service for those who might not carry checkbooks or have PayPal accounts.

For more information, visit the MinistryGive website.

Labels: donation, giving, MinistryGive, software, web application, website

A new friend from Logos might get on me a bit for this, but I did tell him that I wanted to post about something he showed me when we got together Friday night :)

My friend had a Samsung Q1 UMPC (review of this at Brighthand) with him and explained to me how the paradigm of Logos and the TabletPC led him to really embrace mobile computing. Being that we were both of the background of developers, some of the conversation got technical, but the more interesting part of things is where he spoke about ownership, and how many of the principles of Web 2.0 take that away from the user for the sake of short term profits.

Needless to say, I was very impressed at his disection of the marketplace, and what it means for uses both now and in the future. Of course, he is highly invested into Logos, which wants to keep the paradigm of ownership with the user, rather than with the company or publisher.

Getting some back to the mobile tech, he told me about how he uses Logos as a reader, moreso than a sermon prep application. With the number of books that he has on the Samsung Q1, in addition to the size and mobility of the device, he is able to essentially take his Bibles with him, and read in a manner that gives him the knowledge of a serminary's library at his fingertips, but the usability of a Moleskin with the touchscreen.

That's pretty much one of the best applications of desktop Bible applications in a mobile setting I've seen to date. How do you use your electronic Bible solutions and what do you feel about the concept of ownership as it relates to having all resources in your possession versus a website where you subscribe and rent them?

Labels: Bible, Logos, ownership, tablet PC, tech, web application

Its been a while since we have touched on Bible applications in detail, and mainly that has been (on my end) because it is quite hard to focus in on some kind of solution that appeals best to publishers, developers, and users. Everyone seems to have such a different perspective that it has felt a bit futile in terms of asking all to come together and actually build something of mutual benefit.

But in one of my readings this week, I came across an idea for doing such that fits better with the placement of MMM, as well as the abilities and resources of all those who would otherwise be involved. I'd be remiss if I didn't thank Sender 11 for that excellent post - thanks a bunch. And I will also contribute some recent learning about project management methodologies as being the fuel to this line of thinking.

A Common Problem

The common problem is reading the Bible effectively. Pastors will tell you that simply getting people to read is hard; teachers will say getting people to comprehend is a major challenge; publishers will say that there are only a finite amount of ways a person will pay for a product; and readers just want to read without going though hoops.

A paper Bible seems almost idea. Choose the Bible from the shelf, open to the index, table of contents, or last bookmarked section and boom you are there.

Remembering the Book

Lets keep with that last piece about a simple book. An application should have as few entry points as possible: an index of all the terms, a table of contents for the major sections, and finally personal bookmarks. The first two should be built into the program, they should sit in a database that is optimized for speed then results, rather than results then speed.

Personal bookmarks, or notes, or annotations, or highlights, whatever you want to call them. This should be information that the program accesses, but it does not sit in the domain of the application only to use. It needs to be a common to the device format, yet contain the information needed to keep it linked to the application. This means that the program either needs to provide an API to a default notes application, or provide a notes application that is at least as sufficient as the default application, but does not remain proprietary so that one can only get to it by first going to the Bible app. It should store information in open formats, and be exportable to any format needed.

Then We Read

Now getting past that initial entry point, a person as found the book, has opened the book, and is now reading. Nothing else matters. Seriously. Nothing matters. They are in the Word to connect with God. The interface should allow that. There should be as few disruptions by the operating system, application chrome, and additional resources as possible.

Speaking of additional resources; I know that lots who visit here dig commentaries a lot. I get value out of them too. But they should sit as additions, not necessarily as separate entities. One should be able to click on a verse or verse number to gain access to additional resources that are contextual to what was just clicked. For example, clicking on a verse should show 'Get Map', 'Get Parallel Verses', and/or 'Read Commentary' in addition to a 'tag' and 'add note' function. Note, we are still just reading. The other stuff just comes out when we are in the mist of reading and want more.

Handling Multiple Books

This might come as a bit of dismay to some, but I see additional books as being something that should also be complimentary to the singular reading. Most people just read one Bible and then have maybe one additional source.

And that's speaking of those who'd read often. Keeping the program simple means that if there are additional books, that the option for getting to them should be noted on that inital screen with the Index, Bookmarks, and Table of Contents. Just something like, 'More Books' that opens a library would be sufficient. Give the user the option of seeing this either on that screen, or as an addition option on that tap verse item explained earlier. A simple 'View in Similar Book' note would work.

So What Am I Saying

Ignoring the formatting differences, pricing schemes, online or offline abilities, building the experience of reading the Bible simply transends any particular platform and just goes into a need. If one wants to build a Bible app that successfully takes that analogy of reading a book and then presents it simply, we have to think about how we read, and then from there make sure that the additional features don't get in the way.

If I could code something, I'd build according to what you just saw for the Internet Tablet. That's how confident that I am in this methodology of development being something of value beyond just our circles.

Labels: Bible, developer, software, web application, wireless application

Hopefully, you all aren't too tired about this subject. There is certainely room for improvement with Bible applications, and this makes for a great forum to discuss how they can be enhanced and improved.

With the introduction of the iPhone, Apple also announced a service called MobileMe. Much like Microsoft Exchange is in the workplace, MobileMe allows users to sync and use information such as email, calendar, and contacts, across several devices. My interest in MobileMe though is what it was made from and how that speaks to another way of thinkning about mobile web applications.

MobileMe uses a JavaScript framework (skeleton) called SproutCore. Now while the framework in and of itself is ok, the fact that it is so powerful makes it possible to explore desktop-like functionality on a web application. This would mean that folks like Laridian (iPhoneBible), eBible, and YouVersion can do more than just make a mobile Bible application, they could also make one that leverages the browser's inbuilt ability to be a Bible reader across several types of devices.

Of course, I've been panned a good bit recently with an article that was publised at Brighthand last week stating that Apple made a mistake in backing off of the idea of just doing web-based applications. A framework like SproutCore, in addition to browsers supporting offline functionality, makes the idea of web-applications that can be used online and offline more of a possiblity and less of an exception.

For example, you already have a group like the SWORD Project that already utilizes some open source development. Adding something like SproutCore to it, along with some offline ability (Google Gears or an advanced browser) would really make getting into the Word easy and a piece of cake.

Considering the range of this particular discussion, I'd like to hear some of what you all think. Because not every mobile device has a browser, let alone a good one. And not every user feels comfortable with applications that constantly talk to a server - though that is what every web page does, go figure. What can the Body look at in this area in terms of a solution towards not just making yet another iPhone or mobile site but something that really does blurr the line between web and offline in a way that makes us all better for it?

Labels: Apple, Bible, browser, JavaScript, MobileMe, offline browser, software, web application

I've spent the better part of the last few weeks thinking about the idea of a Bible Notes application and have been drafting some ideas about how such an application can work out. However, I want to throw some questions out there as I am pretty sure that I am not considering everything when it comes to something like this. If you could be so kind as to respond to these quetsions in the comments to this post, it would be greatly appreciated - and possibly help any developers who are looking at doing something like this.

• Do you use a browser that has the ability to view/save/edit content when you are offline?
• Is tagging and searching of notes more important, as important, or less important than the notes content itself?
• How do you feel about being able to link to content from other websites easily (verses, commentaries, Wikipedia terms, etc.)? Would you prefer the application came with preset resources, or was a user-added feature?
• If you are a pastor, could you see an application like this assisting both in sermon preparation and study follow-up?
• How would you feel about using this kind of an application on a laptop, smartphone, tablet, etc. during services, studies? Would you encourage the use of mobile tech if such a program is used?

These are some of my thoughts, do you have any others?

Labels: Bible, browser, commentary, community, developer, notes, resources, software, tech, web application

This is what happens when I sit down and begin to think a bit more about how a Bible Study Notes application can/should work. Feel free to offer your opinions, and if you are a developer, think of this as a project analysis of what I've been thinking about.

Bible Notes App/Web App

Short Description Note taking application for mobile devices, internet tablets, etc. that uses a plug-in based architecture to connect to local and online resources.

Why and Who: The reason for this program is so that casual Bible readers, students, and sermon attendees can take notes in a format that follows alongside their natural ability to take notes in a notebook whether they use a digital or print bible.

Goals

• Create notes that extend beyond the context of one particular reading to the various points of information that exist online and/or on the user's device
• Create a point of intersecting the APIs of several Bible programs, formats, and sources so that the user has choice in how to use the resources available
• To encourage the development of plugins for commercial and non-commercial resources so as to not to slight the publishing industry's licensing rights for resource materials
• To address the semantics behind studying, by putting to work the semantics of the web

What Does This Program Look Like:

• Start with the Notes Application on Nokia Internet Tablets
  • Addition of a button that adds functionality
  • Finger typing friendly
  • PDF, HTML, and XML export
  • Upload to Google Docs (download then reupload possible?)
• Title/Initial Actions Screen
  • Create, (3-5) Recent Notes, Delete, Manage Plugins, About
• Notes
  • single screen
  • bottom bar with Bold, Italic, Underline, Color Selector, Bullets, Link (Plugin), Save, Save/Upload

Limitations

• Simple formatting options
• Initially no ability to draw on screen or insert images
• If a web application, needs a server; would be better as a web application that can be launched from a bookmark in an offline mode then save when connected

Workflow

• Two screens: title/actions and notes
• Dialog boxes to confirm actions such as 'link to resource' and 'saved to local/web'

Document Structure

• XHTML
• In page CSS (initially no custom styles for users)
• BibleRef Tagger
• Semantic Bible

Program Structure

• Language: unknown, depends on native or web app
• MySQL on local machine for indexing tags and references
• UI based on writing first, tagging second
• Will NOT tie into any Bible reader program directly, plugins only

Plugins

• Must use API defined by source resource to access content
• search plugins will only pass information via a search string and open in local client's browser
• Plugins that point to local apps should be done with the GPL for user/developer customization
• Plugins that point to licensed material need to be checked for possible licensing issues
• Can plugin point to native app
• Plugin to add ability to highlight, draw on page instead of build into app (possibility)

Plugin Limitations

• Cannot create content
• Cannot pull in content from websites applications to paste into document (later functionality possibility)

This is somewhat detailed, but gives a clear idea of what I was speaking about in Sunday's post. What are your thoughts? Place them here, and let's get a push to make an application that will have some far reaching effects.

Labels: annotating, Bible, mobility, notes, software, study, tech, web application

I am sitting here thinking about my upcoming schedule of things to do and realize that it would be very nice to have a better Bible application (or web application that works offline) that would just facilitate leading and attending Bible studies or listening to sermons.

If you will, I don't need something that would be a Bible reader that then does notes. I am thinking more along the lines of a notepad application that automatically links to a Bible (on the device or not), in addition to other resources.

Something where I could create a document, and it would just be an HTML document. I could add tags to it (so that its easily searchable); and it would upload to places like Google Docs so that it can be shared with others. But then again, it wouldn't have to do that so much.

The idea of automatically linking to resources though is the fun part. For example, if I write a note, I want to be able to highlight either the verse notation written, or a keyword, and then be able to select what resource that it should be pointing to. That resource would basically be the search page for that Bible/commentary/lexicon/Wikipedia/etc. website and instantly give some depth to my notes. Imagine even linking to a city and having Google Maps, or whomever is doing a Google Maps-like ancient Bible maps mash up, link to it automatically.

I think something like this would be ideal as a web application because it is something that I would want for a mobile device (most likely my N800 Internet Tablet, but also my mobile phone). The ideal thing would be for this to work offline without having to be connected first (an issue with many web applications). But I could see something like this coming in just as much, if not more in handy than having a Bible reader, and then asking for the other features to be plugged into it.

Side note: If someone is willing to build this kind of an application, either a web app or something for a dedicated mobile device; I would be glad to help test (sorry, not a app developer) and when it is done promote the application here at MMM.

Related Articles:

• Semantic Bible
• Crosswire Bible Society's SWORD Project

Labels: Bible, mobiles, sermon, software, study, tech, web application