Mobile Ministry Magazine

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 got an email the other day about an update to the PhatNotes Windows Mobile application and it got me thinking about a friend of mine who was using his Windows Mobile smartphone at Bible study, but didn't write one note because the process was just too cludgy between his Bible reader and paying attention to the lesson.

This is not an uncommon problem to many. Annotating is something that we do internally pretty well (usually), but when it comes to transcribing, there just doesn't seem to be enough programs that do it "right." That's not to say that PhatNotes does it bad, but its a solid solution for any of you looking for a notes solution for things such as sermon notes or Bible studies.

A suitable notes solution seems to be something in a few of our wish-lits. That being said, there are solutions, what do you use?

Labels: annotating, Bible, notes, PhatNotes, software, tech