Mobile Ministry Magazine (MMM)

Posts Tagged ‘mobile websites’

Lesson’s Mobify’s CEO Learned from Google

Friday, February 10th, 2012

If it seems as if we’ve been pulling from the list of contributors noted on the recent Carnival of the Mobilists, that’s only because these have been items also sitting in our periphery as notes to pay attention to as we derive some knowledge and wisdom about mobile which is applicable to mobile ministry. Sometimes, this just happens to intersect well with other’s views of what is important in mobile.

Another set of insights pulled comes from a report by Mobify’s CEO (Igor Faletski) relayed via GigaOm. These insights are important to us because MMM uses Mobify to transcode and deliver our mobile website (http://m.mobileministrymagazine.com). Where he is taking is platform, we eventually follow in some respect. So, in hearing some of the lessons he learned in a recent excursion with Google’s Mobilizing Mobile event, there just might be something we could gain as a movement going forward.

Here are the individual points (described as numbered lessons:

  1. Set the agenda
  2. Make your innovation tangible
  3. Focus, focus and focus
  4. Track the micro, decide on the macro
  5. Bringing it together

Read the details and examples of these ‘lesson points’ at the GigaOm article.

Our Reflections, Actions Forward
Its really easy to read something like this and just take it as another set of perspectives from a leader who’s gotten there and is basically setting the pace. But, we needed to go a bit futher here. How these lessons applied to MMM pushed forward some thoughts and initiatives that were already underway.

For example, one of the motions that we wanted to emphasize this year is that while we are in favor of the app movement many are prescribing towards in reference to going mobile, an app isn’t a strategy, and focusing on an app, or series of apps, would be a losing proposition with the kind of support we could push there (see how we explained about resource constraints with mobile apps/websites in a previous article. We decided therefore to decommission all of our mobile apps to an experimental status, and focus on cleaning up our use of WordPress so that we could be more readily accessible in a mobile format (see the Mobile/Web App Beta). There’s still a significant level of work needing to be done behind the scenes in terms of article categorization and dynamic page templates, but, not to the minute level of needing dedicated attention to each mobile platform out there. Will it take us longer to have a “solution?” You bet. Will we be better as a lighthouse for the extent of audiences we have here? Most definitely. That’s our focus, and the clarity we aim towards here.

Your steps might not be as drastic (then again…). What you need to decide as you are going down this path of being mobile, is that your success will hinge on the amount of planning, focus and execution that you can do or manage. If you are trying to control too much, however, you’ll find that the tentacles of mobile ministry will choke the purposes you initially had for your project, leaving you quite still in a mobile world.

 

Implications of Amazon Kindle Cloud Reader

Tuesday, August 16th, 2011

Many of you might have seen the news last week, and for those of you who didn’t, please consider this a really small summary – Amazon released a web-based version of its Kindle application last week. Unlike the previously existing effort where you would be able to read your Kindle books in a PC/Mac web browser (Chrome, IE, Opera, or Firefox), Kindle Cloud (accessed by going to the URL https://read.amazon.com/) is designed so that mobile devices with HTML5-compatible web browsers – currently the iPhone and iPad Safari Mobile browsers – are able to essentially work similar to the Kindle application.

In a very simple sense, you don’t need an application to read your Kindle books. And outside of the initial connection, you don’t even need to be online as you can utilize the feature of HTML5 local storage to read selected books when offline.

Sound great right? Well, its a jump ahead for sure, and with many analysts predicting that there could be over 2 billion mobile devices with HTML5 browsers by 2016, it would seem to speak more relevance to the days being numbered for native applications.

Now, I’ve moved to using Kindle Cloud Reader and have to say that with the exception of page animations and copy/paste, I really don’t miss the native app much at all. Its good enough for my needs, and considering that I normally am using my iPad in a connected setting (I have a WiFi-only iPad), its not a bad idea to use for this kind of application.

So here’s the question, and the implication that people are going to ask if more applications go this route – what Bible readers are conductive to this approach? Are Bible readers conductive to this approached?

Many Bible applications have taken the approach to having a native application that has some Internet connected pieces (Facebook/Twitter sharing, downloading on-demand, backup, etc.). Would it make sense at some point in the near future for them to go the route of HTML5-like web apps like Amazon’s Kindle, Financial Times, etc. are not simply niche publications that are trying this, they have considerable followings and in many cases people willing to pay for increased access to greater depth of content and coverage – its literally a similar palette.

If this begins to happen in critical mass – given Apple’s rules for subscriptions with iTunes, Android’s fragmentation concerns across device types, and increasingly cheaper connectivity options for some mobile users – will your mobile Bible/religious publication approach stay with a native approach, or go this route? Will your users care and stay with you or move to someone else, even if it means they lose your support or content offerings?

 

Mobify empowers marketers and developers to create amazing mobile web experiences. Tap to learn more

Mobify