Mobile Ministry Magazine

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

I write this a good bit before writing Part Three of the MMM Mobile Experiment Report but this is a great article posted at the Biblical Studies and Technological Tools blog about thinking about what technology and faith will look like given what we have seen happen in other media and lifestyles in the Western church.

Without going too far into things on my end, here is a snippet of this great thought-piece:

I am also wondering, then, if we might actually become more dependent on private resources/devices rather than network resources. I.e., it will be lots easier to secure a personal device not connected to any network, and I will be more confident in working with guaranteed secure resources not based on the network. This does mean that I believe that someone will still be developing and providing technological resources for biblical studies, but I also suspect that the choices will be greatly reduced. We are already seeing the convergence of best features of the various Bible programs, and as this trend continues, the only differentiating factor will be cost. I just hope we aren't all buying Wal-Mart or Google Bible software after they buy up every other current company in this field

Read the rest of the post The Future of Bible Studies and Technological Tools.

Related Articles:

• New King James with Microsoft OneNote (Palmsolo)

Labels: Bible, church, community, education, gospel, mission, mobile, mobility, networking, phone, purchasing, software, stewardship, study, tech, urban, worship

Image via Wikipedia

In reading Matt Miller's latest post about a sub-$1000 ultraportables, I was wondering, how many of you use a laptop/ultraportable (not smartphone and keyboard) in Bible studies, meetings, etc.?

Considering devices like the HP Mini Note and Asus Eee PC that are well under $1000 (under $500 in some configurations), it would seem that its very possible to have a capable note-taking solution?

Of those of you that use ultraportables (that is, laptops with less than a 12in screen), do any of you orchestrate special programs or usability features for those in your communities that also use them? If so, what do you share/do?

Labels: Asus Eee, community, Hardware, Laptop, mobiles, software, study, tech

I unintentionally tend to sit on some news stories. Hoping to speak about some things when there is an open slot or the chatter on the interwebs isn't so loud about it that it would get lost in the shuffle; some things just get pushed to the back a bit. Here's some of those items that aren't too flaccid in terms of timing, but definitely useful for various applications.

• Logos post address Spanish-oriented resources.
• The latest GMPSoft newsletter has several deals on various electronic resources for your PDA or smartphone including a Bible Bundle which includes the Greek UBS4 module.
• Something to make you think on how to approach little ones with the subject of hearing God and prayer even when its something that the Bible may/may not talk about ;)
• Palm Addict has a random giveaway of a 15 inch Mac PowerBook going on right now. The rules are to send in a post relevant to how you are using mobile tech. If not something that you need, definitely enter for someone in your circle who could use a computer but may not have the means to attain one.
• Swerve, a ministry of Lifechurch.tv, has two post titled 10 Things.... The first deals with Introspection and the second Ministry. Hands down, a very solid read and meditation piece for the weekend.
• And finally, the Carnival of the Mobilists at Mobilestance has plenty of readings from the past week in mobile tech.
• Forgot this one: YouVersion has done some updates that have improved performance and added a few new versions to the fray. Unless you are on an Internet Tablet like me, it really should work very well in connected settings as both a journaling and group Bible study tool.

Don't forget that we published MMM Issue 5 earlier this week. Several articles and insights there as well for your own mental scratchpad.

Labels: accessiblity, Apple, Bible, Carnival of the Mobilists, community, devotion, family, issue 5, mobile accessories, mobility, Spanish, stewardship, study, tech, worship

Image from Wikipedia

For many of you, its not an issue of "if" to extend your offices, by using web and mobile technology, its a matter of "how."

To answer the "how" we are going to look at a few areas: engaging people to use the tools and selecting what works best with your budget.

Engaging the Team

A major hurdle to using anything new is getting people sold on the idea that it would work best for them. Unfortunately, we are creatures of habit. Doing something different, especially when it comes to utilizing mobile devices, services, or applications can be a bear.

One thing you want to have in place before you roll out a solution is some type of easy to access help system. This should be in two layers (simple): knowledge base and people (in that order). The first questions people ask are the "how do I do this" ones, so making sure that this is populated, and constantly maintained, is of great importance. This resources should be emphasized during any training, and a part of a weekly routine of checking on the progress of implementing a solution.

What this looks like to the minister's on-the-go-office could be a wiki that is saved on the mobile device with common topics. It could be a contact entry that is constantly synced with a note detailing how to do immediate problem solving.

The people resource should be the second and final one. This is where one asks for assistance in doing a feature, or needs a refresher in what was taught originally. Everyone needs a point of contact, and assuring them that there is a person that can be contacted makes it easier for people to accept that there's a change in the workflow in the mist.

Actually getting the team to use those new tools might be less difficult if it could be implemented into the normal routine. For example, in one SharePoint installation I was a part of, instead of making the entire enterprise use it all at once, we made the departments use it only for announcements. We left it open for individuals to play with, but made them know that the only way to know about what was going on was to visit the SharePoint website. Over time, we rolled out more and more SharePoint-only features, backed up with training key users on more features so they would talk about it, getting others involved into using it on a more consistent basis. Basically speaking, giving it to them in small bits is better than force-feeding.

Budget Concerns

One of the questions that is always asked when talking about extending one's office using mobile tech is the cost. Cost doesn't just include the money, its also inclusive of the time, the administration, and any thing else that is not actively using the tech. Balancing cost versus use is hard, but here are some things to think about when evaluating cost:

• Are those providing support or those building the system a volunteer who may leave at any given time?
• Does using a mobile device require additional learning outside of just using office tools, such as user interface and system maintenance issues?
• What is the backup plan? Will implementing a backup plan cost as much as implementing the primary plan? Can using the backup be easier for users than using the primary?
• What are the cost savings/expenses of an entire ministry team being online? Are subsidies or grants available to offset the costs of running/not running a physical office?
• In extending the office, what are the costs to family, friends, and ministry endeavors? Can appropriate boundaries be kept?

Addressing Smaller Offices

Some of you reading this might see these as all well and good, but you are part of a 5-man or smaller team. Things just aren't that deep (in scope or budget). So what can you do?

Take advantage of web suites like Google Apps or Zoho Office. While providing a centralized interface for work, it will also keep things manageable in one area. Using smartphones, Internet Tablets, and UMPC devices are a good means to take light work on the go. Remember though that more devices are more things to manage. Choose the device carefully, basing the costs and engagement on what you already do and what you need to do better.

Labels: browser, community, device, email, family, Google, mission, mobile accessories, mobility, networking, SharePoint, stewardship, study, tech

Since moving to using the N800 and N75 as my computing devices, I've had a bit of a quandary when its come to using the devices for Bible study and church. One main issue has been search. Its not so much of an issue on the N75 with the S60 Bible reader - this Bible reader is a lot like the Bible+ reader that has IMO the best user interface for searching for verses when you know the verse you are looking for in either term or address.

The problem comes when I am using the N800. There, I am usually writing notes and want to go back and forth with Rapier and Bible Gateway (yes, I use both at the same time). While I can get to many verses or notes, its cumbersome, and I have gone to the point of putting the devices down and just listening out of frustration.

I read a post about how one can look up Bible references from the web with Logos and it really hit that what I needed (in some cases) was just a better way to get the verses down do that the N800 can give me what I am looking for.

The way that Logos works, according to the post, its pretty much as simple as pointing Logos to the web page where you want to pull the verse from, and then the library shows the verses in another screen. This method really works best when you have a web page that has all the verses listed, and then the browser is open to that page, and the person is in Logos - kinda like one of those options we talked about before.

Here is a bit more detail about the process:

Libronix will quickly find all the Bible references mentioned and add them to your verse list in the order in which they appear on the web page. You can then decide how you'd like to view them. The default is to show only the references without the text. Double clicking those references will open them in your preferred Bible allowing you to read them in their contexts, compare them with other versions, or dig into your study Bibles and commentaries. If you'd like to see the text of the verses along with the references, you can select "References and Text in One Column" or "References and Text in Two Columns."

In looking at this just in the context of Bible software. It would seem that the best way to take advantage of this is have some sort of outline in some kind of container (RSS) that a program could use and then using the ability of that program to take notes, one would have all the verses they need and could just concentrate on listening to the lesson and engaging in the discussion.

Labels: Bible, Bible+, internet tablet, Logos, N800, Rapier, S60 Bible Reader, software, study

The Laridian Blog has broken into a rather neat discussion about the using the Bible Maps feature of their Pocket Bible 3 software for Windows and Windows Mobile/Pocket PC as part of an effective reading of the Word. Here's a sniippet of the discussion:

Each map is filled with names of places for which you can read more information. Just tap the name of any location on the map and an article will appear. If you do not currently have the Bible Maps – Articles book open and your preferred dictionary is something other than Bible Maps – Articles then the system will first look in your preferred dictionary for the information and open the appropriate article. If you want it to only look in the Bible Maps – Articles book then you need to either:

- Change your preferred dictionary to Bible Maps – Articles OR:

- Close your preferred dictionary and open the Bible Maps – Articles so that both the maps and the articles are on the same screen. By doing one or the other then it will default to opening the article within Bible Maps – Articles.

Read the rest of this insightful entry, and join the discussion at the Laridian Blog. For more information visit the Bible Maps page at the Laridian website.

Personally, I'd love to be using features such as commentaries, references, and maps more, but I have found that the interface on my IT hasn't yet been optimized for these resources.

Labels: Bible, Laridian, study, tech