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

Another use for the Mobile Web Server that occurred to me this morning was to be able to use it to edit and add information on my mobile device without having to fiddle with a number pad or small screen. For the most part, sync conduits and integration into services with applications like GooSync already handle this. But if the mobile device can play the role of being the server already, you can get rid of the middle man and just log into your phone from any larger screened web terminal and then add/edit information much easier.

Thinking about it like this makes the MWS seem a lot more versatile than just a means to have information. There is an empowerment about it that is only limited to the imagination of the user.

For example, a person could be a developer and design an entire website and interface for their projects using the MWS. A teacher could design class modules and then using groups allow for students to log in. Taking that a step further, that teacher could have a test that will only be up while the MWS is online; taking it down means that whomever didn't finish their test on time could be easily noted just from looking at the logs.

I write this to say that I know that its a bit unconventional, and uneconomical in a lot of respects, to think about connectivity in this granular of a fashion. But we have to look at this mobile tech as a means to an end. Taking out some of those in-between points might very well be a means to helping to realize this, and the fruits of the thins past generations constantly dreamed about.

I believe you have to be willing to be misunderstood if you're going to innovate. That's actually a serious point. If you're going to do something that's never been done before - which is basically what innovation is - people are going to misunderstand it just because it's new.

Jeff Bezos, one of the founders of Amazon; quote via Tony Morgan Live

This post was written before the third installment of the MMM Mobile Experiment Report was written. Some of the information in this post is repeated in that report, but not in the detail that it is presented here.

Labels: Mobile Web Server, mobility, software

Welcome to the third and final installment of the MMM Mobile Experiment Report. In Part One, we talked about the general setup and the reasons for doing this experiment. In Part Two, we spoke on the day to day use of it; and then started talking about why its not yet an accessible solution, but it is a versatile one. In Part Three, we talk more about what is possible with the Mobile Web Server and come to some conclusions towards its potential use.

You see, for most end and power-users of mobile devices, the Mobile Web Server is not yet a solution. There are a few too many niggles with it before it can become a solution. What it is however is a canvas, a very empty canvas. When one wants to think of what is possible with mobility, this section of the report hits on that. And specifically for the Christian church, what we do with technology will go a long way towards making divisions along digital lines a thing of the past. Innovation requires that we think outside of the box before we jump into a new one. By the end of this report, I hope that you can not just see why doing the MMM Mobile Experiment was a paradigm shift for me; but also where and why Nokia sees this as a profitable endeavor.

This section of the MMM Mobile Experiment Report contains:

• Lessons Learned
• Current and Future Applications
• Why This Is A Model for the [Digital] Church
• Appendix/Additions

Lessons Learned

At this point, the MMM Mobile Experiment seemed to be a solid idea that is just a bit further than where people want to go with interacting with websites and at the same time, its not far enough in terms of how organizations and ministry can reach out to one another. What I saw in the first few days was that in order to get people to come to MMM Mobile, I had to be proactive about advertising and up front about limitations such as loading speed and the log-in issue. After getting used to it from a lifestyle perspective, I had to come to grips with the ability of attainable technology not being up to snuff with the demands of a web server being backed up by a social network. The frame work is there, but there is a gap before this can be applicable on a broad scale.

I did learn some things that were quite positive, and gives me hope that maybe the Body is better equipped to use near-solutions in effective ways. For example, in talking to my pastors about the MMM Mobile Experiment while it was going on, they had a genuine interest in how it would pan out and how it could be relevant to them. One of the smaller experiments was to live-blog during one of the sermons and then forward them the link to get their thoughts. Live-blogging the sermon on a mobile phone brought stares from people unaware of what I was doing, despite knowing my technical bent. Getting my pastors to be able to log in without issues became a problem because I did not noticed the case-sensitive issue for logging in under the guest account. And even during the sermon, I was not prepared for the out of memory error that running the browser and mobile web server would cause, preventing users from even accessing the site. it was advantageous to try, but in light of things, could have been better planned out.

Other parts that proved positive were in just the evangelism of mobile devices and the Internet as being tools of connectivity. I found that with the MWS active that I had more time to spend on mobile devices, thereby getting me in places where I could engage people and allow various aspects of using mobile technology open the door for conversations. In one instance, interacting with a child in a coffeeshop was made more fun when I took his picture via the Web Camera feature and then showed it to him and his parents from the screen of my N800 Internet Tablet. This showed to them that technology has a way to touching us even more than we think without having to have a Star Trek moment.

Current and Future Applications

Having done this experiment, it is easy to say that it can be used. However relevance for the mobile web server has its place in only a few areas, mainly because of the hardware and connection requirements that would necessitate more affluence than the market can share at this time.

In terms of a software platform, having a web server on a mobile phone can present the opportunity to remove a few middle layers of device management and information management software that has been slow to catch on in some areas. Normally, we think of this as syncing, backup, and personal information management (PIM) software; the structure of this mobile web server platform offers a few aspects of use that previously were harder to get newer users to adopt:

• If the smartphone is online (cellular broadband or Wi-Fi) accessing it though an IP address or domain name assigned to the device (or SIM card) give the opportunity to do things such as add and remove applications, connect contacts to social networks, backup contacts to an offline storage area, or even lock down the device in case of theft;
• If the device is not online, these same tasks can be done through a Bluetooth or Wi-Fi ad-hoc network where all that a person needs is a browser with a larger screen in order to extend the functionality of their device;
• Adding an email component would essentially make the MWS platform a replacement (on the consumer level) or products like MS Exchange as the device is the server and there is nothing that needs to be additionally added to the device.

This is thinking about the mobile web server as it can have present relevance in the way that people want to get the most of their devices. For this to work best however, unlimited data plans, and seamless connectivity needs to be the norm and not the exception. Also, quality of service in terms of mobile operating systems, cellular lines, and even user experience will play a larger part in letting this connectivity option be the norm rather than the exception for mobile computing.

Taking things a bit further, the mobile web server has the ability to innovate in small business and organizational communications by:

• Intranet for a low-funded ministry or non-profit organization
• Website for a traveling missionary who travels in well connected areas and has has the funds to connect frequently enough to make this viable
• Future: platform for sharing documents and calendars as a family point of contact system
• Multi-campus connector for small groups spread over a large area

This is not to say that there are not other applications; only that in using the Mobile Web Server, I spoke with and engaged with organizations where the relevance of a mobile device that can handle these connections made for opportunities to remove buildings, excess tools, and in some cases a learning curve, therefore making more time for the connections that a web server and interpersonal communication allows to happen.

Why This Is A Model for the [Digital] Church

I was asked very bluntly at the conclusion of my experiment why I felt that this was a model for computing that the Body should be receptive to. I was given the reasons about economics, device availability, and even preconceptions that a mobile device should only be used for talking. My reason for thinking and believing that the mobile web server in various forms is a suitable means to enable the digital church is simply that it is something that has not been done before. Its new ground, and puts the Body at the place of pioneering and setting the bar in terms of what is possible with communication technologies.

I do not say this to mean that there are not other organizations that would not benefit from what has been written here, but to say that because the church has a mission to connect and empower people, it should take what is available and not duplicate solutions, but create them.

The book of Acts is an account of a sledging church finding its legs after Jesus left the scene. He deposited within them the Holy Spirit to empower and equip them with the innate ability to go to the ends of the earth and be a representative of Him and carry the Gospel's message of a redeeming and justified love. Since taking the plunge with Nokia's Mobile Web Server, I can see how that would not just be a radical idea, but an attainable one. The question is, are we innovative enough to capitalize on what has already been deposited in us to do since Acts.

Appendix/Additions

Labels: community, education, email, gospel, mobile accessories, Mobile Web Server, mobility, Nokia, phone, software, tech, usability

Web Worker Daily recently posted an article titled 5 Essentials for the Mobile Web Worker where they looked at 5 pieces of hardware and software that would be essential for the mobile web worker. Here are some of mine:

• Removable memory card with backup of data
• Solio solar portable battery charger
• Bluetooth external keyboard

Given that my setup is based on a smartphone and Internet Tablet it might be different than yours. Seeing that many pastors are moving towards a similar type of setup - laptop computer, Wi-Fi- hotspot, and online applications - what are your essential tools?

Bonus: And what things do you have in place when those tools aren't working due to environment/finances/etc.?

Labels: Hardware, mobile, mobile accessories, mobility, N75, N800, software, tech

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

One of the things that I most enjoyed about using the Mobile Web Server was the ability to live-blog sermons and Bible studies. For the most part, this was conducted on my N75 using T9 for inputting text. Because of some hardware and performance aspects, I did have to keep mindful though of how fast I would swap between saving the blog posting and updating it. This meant for shorter notes, but gave me a chance to listen and make sure that I got in the most important points.

I'd like to share the last set of live blogged sermon notes with the MMM community. As we often talk about using technology in innovative ways, I want to make sure that I open to you some means of looking inside of how I am working around the mobile tech of today to address what will be questions for later (the next post will talk about this a bit more).

Here's the important information.

• Link to the May 4th Sermon on Acts 13:42-52 at MMM Mobile
• Login with the username Guest and the password mmmguest (both username and password are case sensitive)
• And just in case my device is down for some reason, a link to the discussion thread at the MMM Jaiku Channel.

Labels: Bible, community, N75, Nokia, sermon, software

This is the meat of the MMM Mobile Experiment Report, and also where it makes the transition from being just a review of software and online services to one of looking beyond the offering to the ability that it lends. Here's an outline of what is covered in this, Part Two, of the MMM Mobile Experiment Report:

• Additional Setup Items
• Day to Day Use
• Immediate Challenges
• Accessibility versus Versatility

Given the length of this, section of the report, it will be an extra day before publishing the third and final section. This report will also be made available as a singular download (debating on the format of that now). Enjoy Part Two, and please do not hesitate to give any comments to this or Part One.

Part Two:

Having set up the Mobile Web Server application on my device, and creating the Mobile Web Server website, I had to set up some initial pages so that in coming to the site, Mobile Ministry Magazine readers would be greeting with more than just a blank page. There are two parts to setting things up for day to day use; one part is on the mobile device and the other is through a browser (that can be on the mobile device or not; but most might choose not to go that route and just use a separate computer).

Setup on the Mobile Device

On the mobile device, one navigates to the Web Server application and is presented with a series of screens. First, you are asked to insert your user name and password that was set up on the MWS website. There are a few easy to figure out section of the application that is always shown when it is opened from here: Users, Status Message, Statistics, Access Log, Folders, and Settings.

The Users section was probably the one that I spent the most time with initially. There is a default Guest account where one can set Guest access to the MWS; and then from contacts in one's address book, you can set specific users to have ability with a user name based on their name in your address book and a password that you have set for them. I quickly abandoned doing this for a lot of people and just settled on making sure that I had a user group for my family to special sections of the MWS site, and everyone else just got the Guest account.

Truth be told, I spent a lot of time looking at the Access Log. I wanted to see how many people were hitting the site, and it was kind of neat the first few days of the experiment. We averaged about 10 unique users per day and for the most part people did not have issues with logging in (user names are case-sensitive; found that out halfway through the project).

Setup through the Web Browser

There is a setup wizard that one has to access from a device that has a suitable web browser while the mobile web server (MWS) is running. On my end, I used my Nokia N800 Internet Tablet connected to a Wi-Fi hotspot at a local coffeehouse while the MWS was running on my N75.

Two parts of this allow you to set up things like the welcome screen, offline page and message, and get a badge that can be displayed on several websites. After this wizard, there is a control panel that keeps the latter items, and allows for presence updates on the status page. One can change the theme to several types; however they are nothing more than color and banner changes. Unless you want to dig in the mobile device and play, there is no way to create custom layouts or fiddle with the CSS for more customization.

From the web browser one is able to set all types of options and create content and points of contact.

• Home
• Blog
• Camera
• Gallery
• Guestbook
• Contact Me
• Presence
• Web Chat
• Calendar
• Messaging
• Phone Log
• Contacts

By default, guests only see the Home, Blog, Presence, and Contact Me sections. The Gallery has to be setup to either show (share) pictures that are shared from the phone's internal memory, memory card, or both. I found that the Guestbook was a bit of a redundant feature, but it could prove beneficial in some applications. The Web Chat section is interesting as when someone starts a web chat, there is notification on the mobile device of the chat and then an IM-like interface is given. From there chat happens just as it would in any other chat room. The Calendar, Phone Log, and Contacts are pulled right from the mobile device and gives a browser-accessible means to see and edit content. I liked this feature, but wished that there was more granularities so that some users could see "Busy" instead of the specific event. Presence tells the state of the mobile phone such as how long it has been idle, battery life, and a status message. And finally Messaging allows one to send an email or SMS message directly to you as well as see all the SMS and MMS messages that are stored on your mobile device (Inbox and those sent).

One neat feature that is present throughout is the fact that all contacts that appear in various applications such as Calendar and Messaging are linked to their contact card. This contact card shows the last call as well as links to the address book entry. Simple, but really neat.

From registration to setting up the welcome page and basic access rights it took about 30 minutes to get rolling. After that it was just a matter of running the MWS on my device and engaging with people as they visited MMM Mobile.

Day to Day Use

The Mobile Web Server is pretty much a set it and forget it type of application. I let it run most of the day, taking it down in the AM in order to use my mobile device as a modem for my Internet Tablet and desktop. During this time, I updated the status message to point visitors to the MMM Jaiku channel. In pointing people to the MMM Jaiku channel, it was my hope to engage the usual readers of MMM, and the new visitors of the breadth of content related to Mobile Ministry Magazine, as well as engage in some discussions across a social network in a slightly different function than what is normally done in blog-driven websites.

On the downside of the day to day use, the MWS was an inconvenience in terms of the other connectivity that I aspire to have on my mobile device. Usually, I run the Emoze email client and the Jaiku Mobile client. Because of the MWS, I was not able to run these and have a long functioning device. Either the MWS would take over the connections, or the applications would consume too much memory and cause one or all of them to shut down. During the experiment, I only suffered one total device crash, but this was an instance where the hardware specifications of my N75 (which has about 15MB of memory free for running programs at boot) was at the very bottom of what is needed to run the MWS.

Because of this limitation, I was not able to use programs such as widgets to keep me abreast of what was going on at the MWS without opening the application. That being said, it was quite nice to have the server running and not have to think about it unless I needed some kind of functionality that was a bit more than normal.

A small note: the Nokia N75 is a 3G phone, meaning that it has the ability to use a high speed data network called HSDPA. Because of the specifications of this network, the device is able to use applications that connect to the Internet at the same time as using voice functions. While running the MWS, there was no drop off in voice quality or phone functions except for occasional slowness for MMS message processing.

Immediate Challenges

While there were those hardware challenges, the large and more pertinent challenges to using the MWS was trying to keep the same kind of communicative presence that had been done at Mobile Ministry Magazine. Essentially, opportunities to post to the blog, upload pictures, and engage the reading community were all things that seemed a lot easier when connectivity was spread across devices instead of being centered on one device.

For example, whenever I needed to use the web browser on the N75, I had to shut down the MWS because the two applications were too large to run at the same time. This meant that I would have to create a status message saying that the server was down and point people to the MMM Jaiku channel; then initiate a discussion at the MMM Jaiku channel; and then I would be able to continue with using the web browser. Certainly, having a device with later hardware (more memory and processor speed) would have been great here.

Another issue that I found was that in order to publish to the blog, I needed some type of dual connection. Using the MWS made situations of traveling to WI-Fi hotspots a bit of an adventure as now instead of using them just as a rest place, I wanted to be strategic in making sure that I could create a conversation piece around the use of the technology. It was not until later in the experiment that I realized that there would be times that I would be able to use the web browser on the N75 in order to populate the blog. This stretched the mobile device, but creating a blog post where I was able to live blog a sermon and have my notes created on the N75 instantly appear online was quite exciting (mental note: taking a T9 typing class before doing this should be a prerequisite).

Accessibility versus Versatility

This challenge of balancing multiple devices, multiple input methods, and then just the plan fact that a web server can really go with you anytime makes one feel more accessible than ever. The granular level of being able to assign contacts or groups of contacts to various parts of one's mobile device presents a solution that is present already in some enterprise applications such as SharePoint and even commercial ones like Movable Type. But those are PC-focused solutions. Nothing wrong with that, but as mobile devices become more versatile, one should not just assume, but see that a lot more of what we do can be driven from a mobile platform.

The Mobile Web Server is an answer to a question that is not yet asked so loudly yet though. Its not so much an issue of how does one stay accessible, as many connected devices open to you; but it allows you to determine how you want people to connect to you based on the social network that you have built - your phone book. This is more powerful and empowering when combined with a communications strategy and a personality that invites people to want to connect to you. That being said, its not accessibility that is the focus of using the MWS, its versatility. Versatility meaning that you are empowered to take your social network with you, and how they connect to you is determined by you, not by the service that you subscribe to.

This is if you where using the software and service makes a change from being just a piece of software or just another online service. It would be easy to just put the MWS into one of those categories and then judge it based on its benchmarks; but there is nothing to just it against. Nokia's Mobile Web Server is a canvas that if given the network and the hardware (and economies) becomes a canvas that enable the kind of personal computing that was dreamed about in the 1950s when the foundations of the Internet began, and now realized with the fast and (nearly) open wireless networks that most of the world has access to.

Flash Sideshow of MWS Screens, via Share on Ovi

Labels: accessiblity, browser, community, device, internet tablet, Jaiku, mobile, Mobile Web Server, mobiles, mobility, N75, Nokia, review, SMS, software, tech, usablity

The MMM Mobile Experiment was one part a technological look at what is possible with mobile devices today, and a look at what is possible/can be done now with mobiles as part of a social strategy for inreach and outreach initiatives.

Just a review of what Part One of this report will contain:

• Reasons and Goals of Experiment
• Explanation of Nokia's Mobile Web Server and my Device
• Social Networking Component

As stated in our previous post, the experiment is looking at the technology as something doable now. But also why software and usage has relevance in this highly connected world. Part One of the MMM Mobile Experiment Report gives an overview of the technology used in this experiment and how it was set up for use.

Part One:

For eight days in April 2008, Mobile Ministry Magazine's Antoine RJ Wright conducted an experiment where the Mobile Ministry Magazine website was hosted completely on a mobile device using Nokia's Mobile Web Server. The goal of this experiment was to test the viability of such a mobile platform as a solution for running a community website, to investigate the capabilities of mid-range mobile phones and smartphones as a communications hub, and to investigate possible uses for such technology in various social and economic environments.

Backing up this software, Mobile Ministry Magazine used the Jaiku social networking service as an offline community component. The reason for this is that limitations in the phone hardware would mean that the mobile web server (MWS) would be offline, yet there needed to be some means for consistent with the MMM reading community. This channel of the Jaiku network contains aggregated RSS feeds of several websites that speak towards life and technology in Christian circles.

With these two aspects set, the MWS server was activated, and MMM Mobile began to live. In this section of the report, we will talk in detail about the technical and physical look of this MWS, and then how these worked in real-life.

Nokia's Mobile Web Server

Nokia released software based on the Python programming language called the Mobile Web Server (MWS). Expanding the methodology of their N-Series mobile devices being the "next stage of computers," the MWS is a project to demonstrate the ability of mobile phones today, and to explore the use of a server, or data and application hosting platform, on a connected and mobile device.

Setting up the MWS requires the registration of a user name at the MWS website (http://mymoobilesite.net). This user name will become the address of the website (username.mmymobilesite.net). After setting up the user name, you then set up information such as a profile, offline page, and then download the software.

The MWS software is compatible only with Symbian S60 mobile devices. While there are a few devices by Samsung and Motorola, only Nokia devices with Symbian S60 have been tested to work with MWS. Unfortunately, not all Nokia S60 devices will work, and many will have limitations based on their hardware. This limitation will show up later as a reason where a solution for its use is limited technologically and economically.

My device is the Nokia N75. This S60 smartphone is one of three 3G devices that Nokia currently has made available in the US. This device was featured on the Cingular/AT&T wireless carrier a little over a year ago and for most purposes is about at the end of its marketing life. This doesn't mean that it is incapable, only that better is here and coming. I purchased this device in December of 2007 in order to better learn about the S60 operating system and have something that would have ample value to my usage as a person who enjoys and lives on the web and mobile devices/applications.

The Social Networking Component

As a nearly-30 adult, much of my online time is spent on email and within social networks. While I do not have a presence on MySpace or Facebook, I do have one with Jaiku. A recent Google acquisition, Jaiku found favor with me because of its mobile client application, the ability to consolidate RSS feeds into one singular area, and a community of people from multiple background, faiths, and locations. In terms of social network services, Jaiku belongs to a subsection called lifestreaming applications. Lifestreaming meaning one can have several streams of their life appear in this service. From microblogging to sharing photos on services such as Flickr, to community channels, Jaiku is one part a community and another part a gate where you can allow people to come in and out of your life.

For Mobile Ministry Magazine, Jaiku is used as an RSS feed aggregator and community window. Through discussion and the RSS feeds, our community focus is seen and shared. Because of this ability to be a window made it a suitable back-chatter component for this experiment.

In Part Two, we cover the day to day use of the Mobile Web Server, some initial and lasting challenges, and the difference between accessibility and versatility as I began to dig into using MMM Mobile.

Labels: community, device, mission, mobile, Mobile Web Server, mobility, N75, Nokia, review, software

Mobile Ministry Magazine has gone mobile. For the next week, MMM will be hosted completely via Nokia's Mobile Web Server on my Nokia N75. This is one part a test of the technology, and another part a means to keep me on top of those things that might lend towards some effectiveness towards those of you who need small intranets within your workplace, but the cost of developing and maintaining on might be out of reach.

View MMM Mobile at: http://mobileministrymag.mymobilesite.net.

Username: Guest
Password: mmmguest

If it says that the server is offline, its probably because my battery is dead or I needed to close the app for a bit, just visit the MMM Jaiku channel as news, notes, and discussion can always be found there.

Now this is really taking things mobile :)

Labels: community, Jaiku, mobile, mobility, N75, software, tech

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 was sitting here thinking about the Nokia N-Gage platform and their new Get Out and Play campaign and how it takes the online aspect (think X-Box Live and World of Warcraft) and brings that community to mobile devices. I wonder, much like some ministries have gone into virtual worlds to start ministering to people there, could the same thing be possible within N-Gage?

Labels: community, mobiles, mobility, N-Gage, Nokia, software, Video game

Greetings all. I'm back from celebrating my birthday (Sat) and just having an enjoyable and very busy weekend connecting with friends and family. To get started with the week, I'd like to share some of the links that had been sitting in my RSS feed list this weekend that I am just getting to.

• Laridian has a PocketBible 4 for Pocket PC Preview posted on their blog. It looks like this will be a very good update to those of you already using Pocket Bible. And those of you on the fence about it might really want to take a look as well; looks spiffy at this point. Beta testers are being asked for as well. See the post and a video of PB4 at the Laridian Blog.
• TonyDye has posted about the start of a CITRT group on LinkedIn. CITRT stands for the Church IT RoundTable and plenty of believers from around the US are a part of this group encouraging and sharing knowledge of what works in tech in their respective areas. Do connect on LinkedIn and the CITRT website.
• Frank J. at Strategic Digital Outreach shot MMM a note about a post on his blog talking about how ministries are using SMS as an enabler to connect people with ministry outreach events. Very cool stuff.
• Don't forget to vote in last week's poll about MMM taking itself literally to being run off a mobile device for a week. This poll will close later this week.
• There's a relatively big announcement coming in the next day or so about an extension to the MMM family. Stay tuned for that as many of you might want to link in with this fairly quickly ;)

Labels: Bible, Laridian, software

I am one part a member of Nokia's Blogger Relations team, and have recently been invited to be an S60 Ambassador. Essentially, I speak about Nokia's products to people when I see that there's a need for them. In some cases, I'll get devices or services to try out and then report those findings back to Nokia. For them, it's an effort to see how people are using their devices and services. For me, it's a chance to see how mobile technology can enrich and empower lives.

The better part is that there are relationships that happen. Being able to live in Christ around them makes having opportunities like these presented by Nokia and other companies kinda neat. Here are a few of the recent reports that I filed to Nokia's S60 Ambassador's program. For those of you looking at ways to see how mobile tech fits, this is how I go about learning and applying.

Episode 1: The Young Mother

I went to visit a friend of mine on the other side of Charlotte as she has a 1yr old kid who has provided for several great photo opportunities. She and I talked about her e-learning class that she is taking and some directions that she could go with content for her blog. I recommended the idea of the phone as the literal center of the Internet for the school by using the Mobile Web Server.

First, I had to explain to her what the Mobile Web Server is and what kind of functionality that it opens up. Then, I told her that I could show her what it would look like. So I pulled out my N75 and turned on the Mobile Web Server. We navigated through each of the pages on her laptop that was in front of us, and I showed her how such a setup would make for a different take on distance learning ventures.

She was amazed that my phone could do that and asked why it was that her 3555 was not able to do the same things even though it was a Nokia phone as well. I explained to her that while they were from the same company, that they used different operating systems. One of the applications that she'd become a bit intrigued about is Jaiku; especially its ability to link with the address book for presence notification. That was something that she wanted for her phone. I led her to Yahoo, and there she learned about Yahoo's oneConnect service. Unfortunately, she does not have a mobile [data] plan, and does not see getting one; so downloading that was out of the question.

he problem that she posed to me was how to get more out of a phone like mine without being online. Considering that I do so much online via my N75, that really left me without many words. Other than the Bible, voice, and SMS, the rest really is the Internet. Making my phone compelling towards those who don't need that functionality will have to become another search of mine.

Episode 2: The Church Admin

Monday night is usually bible study at It's a Grind Coffeehouse and that is where I was again this Monday. Having had a successful demonstration of the Mobile Web Server running on my N75 earlier Monday, I decided to pique the interest of one of the administrative workers of my church and get her idea on such a solution.

First, I gave her a small demonstration of the software on my device, and then used my N800 Internet Tablet to show what the site actually works like in a web browser. At that she was impressed, but I could see not convinced at its usefulness. I then changed modes to talking about how there is always some information that one wants to keep personal, but other things, like pictures and availability that would come in handy for some people to know.

I then set my Gallery to show the pictures from my memory card and showed her how that page could be set with permissions. I then showed the Contact, Presence, and Calendar screens and showed that these can be controlled with a simple group that is created on the phone.

She looked at the phone and said "that's interesting. Your phone is a powerful little thing." Powerful indeed, but as a device that connects, its hard to beat.

Related Items:

• Nokia's S60 Ambassador Program
• Nokia's Mobile Web Server
• N75 Live-in Review Update
• MMM's N95 (via Nokia Blogger Relations) Review
• Yahoo's oneConnect service

Labels: Bible, church, community, device, family, Jaiku, mission, mobile, mobile accessories, Mobile Web Server, mobility, N75, Nokia, phone, software, tech, urban, usablity, Yahoo

Last night, I downloaded Nokia's Mobile Web Server onto my N75 and have to say that its am impressive piece of work. Besides being a web server, aka I can run a website off my phone, I can also use it to extend things like my calendar and contacts to friends and family and essentially have a website for direct communication.

That, of course, got me thinking about Mobile Ministry Magazine (MMM) and a route that could be taken with it. Essentially, I was thinking of taking a week to host the site on my phone, and then use the MMM Jaiku channel to supplement things when I need to take it offline (ya know , to turn off the phone or use it for something else).

But before I go off the deep end and really make MMM mobile, I wanted to ask you all of your thoughts. Here is the poll, please place your responses in the comments.

• MMM should stay as it is and the mobile MMM just be an aside
• MMM should go mobile as described above
• Something else entirely (please describe)

Labels: browser, community, device, Jaiku, mobility, N75, Nokia, phone, software, 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 website Help My Unbelief has done an excellent review on the Amazon Kindle eBook device. While we've touched on it in bits and pieces here, this is the first review that I recall taking the device totally from the viewpoint of an aide to Bible study. Here's a snippet of that review:

...I have two versions of the Bible on my Kindle, the NASB and the ESV. Both of them have very awkward navigation methods. When you open the Bible, you start on whatever page you last left off on. This is difficult because if you are in the middle of a chapter, you will have no idea what chapter you are in or what book you are in. The book/chapter reference is not displayed anywhere on the screen except at the beginning of a chapter. The way around this is to change your habits a little and make full use of the search feature. When you want to read Ephesians 3, simply hit search then type in eph 3 and hit enter. You probably won’t be as fast jumping around the Bible on the Kindle as you would with a paper Bible but once you get the hang of it you won’t have any problem keeping up with sermons or Bible studies where the leaders jump from passage to passage. If you know you are going to be in three or four passages and want to flip back and forth between them, you can bookmark each one and jump between bookmarks easily...

Read the entire post at Help My Unbelief.

Labels: Bible, Kindle, review, software, tech

Monday, I had a meeting with one of the pastors of my church and we talked a bit about getting more out of our church website. Essentially, he wants to use the website bettter to cut some of the administration costs and time to do things. I just wanted to be notified of things in a more upfront, and user-engageable manner. But because both of us are techies, we tended to take things a bit further than some people are willing to go right now with their use of web and technology. So what we did was scale back our thoughts a bit, and then hit on some areas where we could be a good stweard of the web resources we have, but also make those invitiing options for our community.

Here are some of the things we talked about that might prove helpsful to some of you who wish to add some web or mobile-friendly aspects to your ministry efforts:

• Instead of printing announcements and having left overs that just get thrown away, print 1/2 to 2/3 of what you would normally print and then have cards that just list your website address on them to give out when you run out. This drives traffic to your website, and allows your ministry's brand to stand out some more.


• If you have a blog, post a small blurb every week that is just a bulleted listing of the announcements. If there is something that is special or requires more details (such as a teen outing, or study outline), break that out in an occasional single post. Then, when doing announcements, use a screenshot of that posting so that people associate announcements with your website. Here, you can mention using RSS in order to keep up with these items.


• Be innovative in what you post online. I recommended that we post a small outline of our Monday night Bible study on our blog a day or two after the study. This way people who are searching (Google, Yahoo, etc.) will be able to see that we have a study going on, and those who were there would have an additional resource when they want to refer to something said later in the week. Again, emphasize the use of RSS here so that you can empahsize purposeful Internet time.


• Encourage leadership to use web applications for generic things such as teh church calendar (Google Calendar, Upcoming, etc.) and then web-based services such as Evite for special services and events. For example, we talked about using a custom Evite invitation for Easter Sunday services.


• Remind people that their cell phone number is also an email address. For some carriers, you can check these emails online instead of on the device. But, you will receive a text message about them all the time. Using this address for time-sensitive information will help people to keep in the front of their head what the ministry wants to do with them.

These are just a few things, but ways in which technology can be used in a manner that addresses a need to inform, and also a need to trim the fat in terms of administration time. I encourage you to ask those techies in your communities who are project managers and team leads on how to implement these types of things into your ministry efforts. Stwearding this resource well is just as important as any other.

Labels: community, education, email, family, mobile, software, tech, usablity

This was quite interesting to see in my inbox yesterday considering the recent post on being a good steward. Splash Money for Windows Mobile has been released. It was previously available for Palm OS handhelds, but now can be used for those with Windows Mobile devices.

Here are some of the features:

• use stand-alone or sync with desktop edition
• ability to categorize individual or batch items
• 256bit Blowfish encryption
• support for several account types (checking, savings, money market, etc.)
• And more.

I really like Spash Money (and am waiting for the Symbian S60 version). Using this along with doing the Dave Ramsey's Financial Peace University course with my church really helped me to better mind my manners when it came to spending. The integration with the desktop, along with the wireless syncing on one (unfortunately not all) of my back accounts made keeping track of things pretty much a breeze. Also, being able to create and print out a report of what I've been doing has been helpful as well.

Splash Money for Windows Mobile is available now as a trial version or can be purchased for $29.95. For more information and to download, visit the Splash Money website.

Labels: devotion, software, stewardship, tech, Windows Moible

I suffer from this mindset of a user experience and user interface designer. I think about how and why we use technology more often than anyone else. I am always looking at where to trim the fat, even to the point of taking two steps back to take 20 forward (eventually).

I've felt a lot like this when its come to Bible readers. While I'm in the group of those wanting to have a much improved reading experience with these electronic goodies, I realize that for many people, the need or want to read electronically is not at all attractive.

This perspective hit home (again) when I was reading an article at Ars Technica speaking about the emotional bond that people have with paper. Not that I disagree, paper is great. And I can be accused of looking past that emotional attachment more often than not. But one cannot discount it. Its there, and as a person with just a little bit of voice in this area, I cannot discount it in going towards the bits and bytes.

That being said, I wonder if developers can start thinking about reading with paper. Thinking about a bible reader as if it were paper. Starting from the perspective that content is seperate from presentation (just like in the print world). That formatting and ease of use isn't about sliders and buttons; but about how to enrich the reading experience. About not just giving a great search index, but making search work like our brains do.

I think LJ was really onto something in his part 2 of his The Ultimate Bible Software Application post. But not in the respect of publishing, in the respect of changning the method completly. The web IS NOT print. Its NOT radio. Its NOT TV. Its different - entirely. And has to be done differently. Those that have tried to pigeon-hole it into those same paradigms have fallen aside.

Like reading with paper changed the way that people assumed information was valid and usable, we have to expect that Bible software has to have familiarity, but be different than just pointing and clicking. Its a lot more than that, and our response as technology evangelists means that we have to find that place, and like a nice piece of paper, elegantly show that there's room on the page for this type of reading.

Labels: Bible, software, tech

LJ posted on his blog another perspective of what we posted on earlier in the week about a Hybrid Bible Reader and what that would look like. Given his perspective of working with Logos and WordSearch a good deal, he brings some needed understanding to the table as to how this can work. Here's a snippet of this post:

...As an avid user of Bible software (circa 1999 or so & using WORDsearch 5 and e-Sword), I've come to find that there are a lot of things that I like in one application, but is not found in another application. Then, there are also those things that I don't like in one software that isn't an issue in the other. Throw into the mix the world of Web 2.0 and you have an entirely different ballgame. Now with the likes of eBible.com and others, one is easily able to share their thoughts on the Word with the world at large, layman and scholar alike. So, just imagine if all of the good was combined into a single application, or at least brought as much of the best of all the worlds together, that's what I mean when I say the "Ultimate Bible Software Application...

Read the rest of the post at the Trailblazin Ministries blog.

Labels: Logos, mobile, software, tech, WordSearch