Bible Study Notes Application (In Detail)
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
posted by Antoine @ 5/13/2008 10:00:00 AM
4 comments
4 Comments:
Some might have just read this and other posts thinking that I think too much like a developer and not enough like a user. Apologies, but I have been on the bent of an analyst lately.
The thing about a program like this is that you want to make it easy for people to create notes. They are more likely to keep notes when the tool is easy to use. A simple note program is one thing though. A program that plugs into reference materials is another. Just like those that make notes in margins for later reference, hyperlinks can serve this purpose in a document that is more electronic.
The kicker is how to develop such things across so many users and mobile devices. A web app would be a great solution, as would a Java one. But there are limitations all around. Wondering what kind of net can be cast if such things are chanced though.
If the folks at Laridian could give this a read. I would love to have something like this incorporated into their Pocket Bible program that way it could sync between their desktop app which would easily run on most Tablets or Ulta Mobile PCs. You would have them on your Windows Mobile device and your PC. This makes me wish I was a developer.
You see Kevin, I'd like this particular piece of software NOT to be in the hands of any of the Bible software companies. I'd rather it be an open source effort that is mutually supported by those companies. In this way, development doesn't fall to politics (hence the Plugins section where Bible software companies can have their piece of this) and users get a product that is free to develop on for further applications - from a seminary class notes adaptation to whatever.
The other part is that I don't think this kind of program should be a part of a Bible program. The temptation would then be to bundle it, when seriously, most people just need to take good notes electronically. They just aren't yet seeing the need for electronic Bibles en mass. An app like this leads people to understanding where mobile/electronics fit, while giving an option that lends towards education of how software works.
I don't say all of that to deny your points, only that it was not in the original scope of the post.
I need to find a willing group of developers; this really can work.
I was thinking about this a bit more the past few days and didn't even realize it until I did a read of May's postings.
You see, there is a blogging application as a part of the Mobile Web Server that I now use for my personal site. This could be repurposed for use here, and if I can present the ending markup right, it would essentially be an application that would be just this.
I think I might have to try this.
Post a Comment
<< Home