Mobile Ministry Magazine

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