Mobile Ministry Magazine

One of my bros asked me why I'm not running MMM on the Mobile Web Server, and I told him it was because its still beta, and that's something of a large decision (I currently run the an MWS site as my personal website, and dig keeping content separate). Nevertheless, it did remind me that I did not post about the recent update of the MWS to version 1.5. Here are some of the new features to be found in this version:

• A new Access Rights web page highlights some of the site administration updates. This new page makes it easier to see and control access to MWS pages.
• RSS has been addressed with a new configurable RSS feed. Instead of just taking all the content, RSS feeds can now be separated into several feeds for the different aspects of the MWS.
• Finally, developers now have the ability to add their own Python web applications. By using the MWS SDK and framework, developers can create external applications which, when added to the MWS, will show up in navigation similar to the built-in applications.

This new version of the Mobile Web Server has also been tweaked to take advantage of the Destinations feature in Symbian devices using the latest 3.2 (Feature Pack 2) operating system.

Nokia's Mobile Web Server is compatible with Symbian S60 devices and can be downloaded for free from the Mobile Web Server website. As a note of advice, it would be smart to have an unlimited data plan with this. Its not bandwidth heavy, but you would want to keep the site up :)

For those who are still wondering about MMM and the Mobile Web Server, you can read the MMM Mobile Web Server Experiment Report (PDF, April 2008) to see some of our findings. Maybe we'll revisit it with a newer device and near-final software to demonstrate and push the envelope a good bit more ;)

Labels: mobile, Mobile Web Server, mobility, software

Just putting something out there for thought and possible discussion, so please excuse yet another rough thought spill...

Since receiving the N95 NAM as my prize for the Mobile Web Server Competition, I have been exploring aspects of mobility that I had only dreamt about. For example, one of my usual tasks these days is foregoing the desktop and Internet Tablet and connecting the N95 to my TV and Bluetooth keyboard and just working and browsing from there. Outside of a few niggles, it really does work very well.

Today (Sunday) though was interesting, I had to put my car into Pep Boys as it was smoky and as I waited for the oil change, I pulled out the N95, and it proved to work as something to browse, read, and just connect with the local environment.

I pulled it out when I got to church to turn the profile to the Meeting profile, and then used it to read along with the sermon. I made a note to blog about the sermon later and set up an appointment to meet with pastor.

Getting home, I then connected it to the TV to browse, writ that blog post, and catch up to some weekend reading. I realized that mobile wasn't the push so much as the context that it was used. And if the mobile's software and hardware works in concert with my environment, then I am better able to live and connect with the world around me.

That got me thinking about how using mobile devices allows us to better respect and use the context for the benefit of Christ and community. Where much of the other technology that we use is pervasive and stays that way, mobile devices have the ability to be pervasive first, but then meld into the background as they are more personal than other technology and media. If you will, its designed to be used in context with our environment, and from there we connect.

So I sit, composing this on my tablet as my phone is streaming music from last.fm, imagining what it willb e when my mobile responds to the environment much like a person does after being taught the ways of culture. For my mobile to automatically go into silent when I get to church, and then pull up the Bible reader with a prompt to download the pastor's outline and any church announcements to my calendar. I look forward to all that's really left for us to do is have the tech move out of the way, so that in the context of connecting and sharing the Gospel with people, we just are able to live without layers.

That is what I saw today in using my mobile. Context is where mobile makes its impact. Should be fun to see how this works out.

Another post created with the alpha version of WordPy for Internet Tablets; please excuse any issues as I am doing some application testing.

Labels: community, Context, mobile, Mobile Web Server, mobility, N95

Having received the Nokia N95 (North American edition) as the prize for my second place finish in Nokia's Mobile Web Server Challenge, I am now about the business of using it and its associated applicaitons and services to turn what we know about church and Bible studies on its head.

First thought, and something that I will certainely try and pull off (in some form), is using my mobile device as a learning center for a Bible study. For this we have a few items:

• My N95
• Nokia's Mobile Web Server
• JoikuSpot
• Friends with various wireless devices
• eBible or YouVersion

As you can see, we have a common contact point in the N95. The N95 will serve as the WiFi router for the other mobile devices with JokiuSpot (did you think we'd be meeting in a coffeehouse). And then we will balance having Bibles and resources with eBible and/or YouVersion, while the lesson and its comments will be placed on the Mobile Web Server.

Location: the middle of a park. There are a few reasons for this location. One, we are outside of a building and able to enjoy the beauty of God's creation while engaging His Word. Also, we put people in a place where they are less tight from sitting in a traditional church environment. Lastly, this is open enough that it would invite others to sit with us, but not feel like they cannot just pull out a pen and paper, or a laptop of their own, and jump right into the discussion.

Of course, making sure that this is something that can be found on a map would make it easier, so we use the MapSpot add-on with JokiuSpot to put the hotspot on a literal map so that people could see and engage with us, and have a means to get directions to our location.

This assumes a few things, such as connectivity issues as not being a problem, and that those involved would have the technology to engage this environment. Of both of these, I see them as being much less of an issue for the current and next generation of mobile users than what has been had previously. Devices and networks are ready for this if you will.

After all of that its just about digging into His Word. Using what we have been given in terms of His Word and Spirit to hear what God would have us learn at that moment. And then with the technology we can engage virtual audiences with audio, text, and video. We have a means for people to follow up on things as they are saved on the mobile web server and easily accessible. And then we have engagement. Its all about people and giving them avenues to engage the Word and their communities.

Thoughts (because I've not done it just yet, but I will)?

Labels: community, eBible, internet tablet, iPod Touch, Laptop, Mobile Web Server, mobility, N95, smartphone, study, YouVersion

This year, one of my biggest struggles with just about everything has been to remember that there's a good bit of relevance that must be undertaken with everything. And especially in the field of mobile technology where things just move faster than people want to even write about, its important to remember something I've been told often, technology is only relevant when it is personal. Some recent thinkings have put me in a position though where I realize that I have to do a lot more evangelism than just using this stuff in order to make this point clear.

I can start with the example of my use of Nokia's Mobile Web Server. Frankly speaking, this is probably one of the most far out things that I use and one of those things that people go "ooh" about, but just don't understand. Without repeating the entire post that I wrote up on my personal website, I will say it like this: using a web server on your mobile phone, or even just the idea of having a web server in your home gives YOU control of the information that you put on the net. Not Google, not Nokia, not anyone. You administer it, and you say how it gets anywhere, if it goes out at all.

The mobile device that's that and adds the ability to associate that personal information with the context of your environment. Its not just an IP address, its an IP address that's attached to a photo of a place or a contact person or a a mesh of all of those and more. That's not the web virtual, that's a literal web. And its already something in your hands. Imagine knitting the Body together with that kinda stuff.

Or about about mobile devices in general? Most would say that while they are enabling, that they offer no real benefit over other computing situations. That might be right, until you consider the cost of powering devices. The wastefulness that we display as a computing culture is crazy. Slimming down to the bare essentials should allow us the time to develop more accessible and renewable solutions, while making all of those previously stated connections all the more fruitful.

Connecting: I want to be the kind of parent who has the "key" for allowing his household to be online. If you will, I'd like my mobile device to be the gateway for my family. This way I can see and interact with what my kids are doing, and my wife has an accessible and open means to keep me accountable. Far reaching? Nope. Using something like this soon to come software and a solid smartphone this is not just possible, but probably advisable.

Look. I am not saying that we have to do this. I am saying that the technology is relevant if we look at it as being so. I still think that a partnership between churches and developing nations could do more for increasing technical competencies for both sides than just doing nothing. I still feel that solutions like Earthcomber should be used by more urban missionaries to share and live the Gospel. I still see the need for people to put these devices down and interact with one another being an important part of using these devices. I just have a problem with just letting it sit here. I'm made in God's image. I'd like to believe that somewhere in me beats the ability to be relevant with whatever is in my hands and life.

For me, it just happens to be mobile tech and its various applications, intersecting with my faith, in a way that just happens to push the green light out a bit longer.

Labels: accessiblity, Bible, children, church, community, computer, environment, innovation, Internet, Mobile Web Server, mobility, networking, OLPC, smartphone, software

Winners have been announced for Nokia's Mobile Web Server Challenge. Instead of spoil the surprise, do check out the news posting at the Mobile Web Server website.

Labels: Mobile Web Server

I just wanted to remind those that might have seen the posting last week and figured to wait a bit. The Nokia Mobile Web Server (MWS) Challenge Finalist Voting ends today (probably in a few hours Finland time). Do check out the five finalists, including MMM with the MMM Mobile Experiment Report.

To vote, you only have to make your entry on the feedback form. Its easy and you don't get spammed for anything.

Prizes include a new Nokia mobile and gift certificates.

Thanks to all who've voted already. And even if MMM doesn't win on this note, I really appreicate the support from Nokia's MWS team for our contribution in this contest.

Labels: community, contests, Mobile Web Server

Some good news to break into things today.

The MMM Mobile Experiment has made it into the final round for the Nokia Mobile Web Server Challenge. You can vote for the MMM Mobile Experiment as well as the other four finalists by visiting the new article announcing the finalists.

The really interesting thing is the variety of applications for the mobile web srever that is presented in the finalists. Whether you are an end-user, programmer, or just intrigued, there's something solid to be voted for.

For me, I'll finish campaigning for the moment, but please do vote for someone :)

Don't forget that the MMM Mobile Experiment is available as a PDF for your reading as well.

Update:: thanks to everyone who has voted so far (special shouts out to Jaiku, Brighthand, and Palm Addict folks a big thanks there)

Labels: community, Mobile Web Server, mobility

After some edits by Kevin A, I went back to the MMM Mobile Experiment Report and cleaned up a number of outstanding issues with it. Besides a new summary at the beginning of the report, there is also the addition of a cover page, and links throughout to correspond to the links that appeared in the blog postings of the MMM Mobile Experiment Report. Of course, grammar and spelling fixes abound. And more are probably to come.

I will say that this is by no means a finished product. It is considerably better than what it was though. Hopefully, this is something that will be of an enlightening read for you; and give you some understanding of where Mobile Ministry Magazine's goals lie in terms of the type of content to expect from this site.

Please do not hesitate to point out any issues relating to this PDF. And if you know of anyone who'd be able to devote some time to editing this and similar MMM-produced pieces, please let us know by dropping us a line via our contact form. Such services are greatly needed.

Read and download the MMM Mobile Experiment (PDF).

Labels: Mobile Web Server, tech

Here is some good news for MMM readers and those who just like technology that reaches a bit more than just out there.

I was approached by Jukka from Nokia's Mobile Web Server team (and I'm sure he's on several others), to write a guest post for Nokia's Mobile Web Server blog. The following is a snippet of the published post:

...In finishing with the MWS Experiement at Mobile Ministry Magazine, I knew for sure that moving my personal website to the MWS was something that I wanted to do. Besides the ability for complete content control, I began growing used to replacing going to MS Exchange when on a full computer to going to my moible via my MWS website. It was not just an issue of replacing a website that excited me, but replacing that entire middle man of syncing that made the MWS an attractive pursuit. However, I was not confident in my mobile device. Battery and memory concerns meant that I would have to modify usage patterns to carry a charger of some sort around often...

Read the rest of the post Replacing a Community-Reaching Website with the Mobile Web Server at the Nokia's Mobile Web Server Blog.

In addition to the post at Nokia's Mobile Web Server Blog, there is now a compiled version of the MMM Mobile Experiment Report in PDF format for your reading pleasure. This is the inital non-styled version, there will be an updated version of this PDF in the coming weeks.

Labels: Mobile Web Server, Nokia, review, software, tech

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

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, usability

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

Greetings all; thanks to all of you who have visited and commented on MMM Mobile in the past week. It was certainly a new experience for me to use a mobile device as the web server and I have a greater appreciation for a lot of aspects of server administration that I had not had before.

Seeing what my mobile device could do under the pressure of being a communications platform in every sense of the word was tough as well. From blogging, to the web chat on day one, to just making sure that I would keep the MMM Jaiku channel going with back-chat; it was both a pleasure and a challenge to do something that (to my knowledge) has not been tried before.

What's next is a report of things that I found, as well as why such an experiment has relevance in this highly connected world. With talk of net neutrality, the new digital divide, and Christian digital responsibility, there's a good deal that this experiment opened that I will be bringing to you in a three part report.

To give you a heads up, here is an outline of what you can expect in my next three posts:

Part One:

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

Part Two:

• Day to Day Use
• Immediate Challenges
• Accessibility versus Versatility

Part Three:

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

I am trying to take my time with this, and I do encourage you to ask questions along the way towards parts that need to be better explained or clarified. Like I stated earlier, making sure that you (this audience) understands why such an mobile experiment has relevance for you today is a big goal of this report. Keeping in mind of the Word to always encourage one another, its my hope that this would encourage you to not just think about how to use technology, but how your innovative use of it will give people a chance to view Christ in ways that they never imagined.

Again, stay tuned, Part One is just about finished being written and edited. Looking forward to your comments.

Labels: Bible, browser, community, mission, Mobile Web Server, mobiles, mobility, tech

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, usability, Yahoo