Posts Tagged ‘mobile apps’

JIT (Just in Time) as Your Mobile Focus

Wednesday, May 16th, 2012


When preparing for this week’s articles and activities, a term kept coming to mind, then it started popping up in various articles and comments. The term is simple, JIT (just in time), and it refers to a context of information and the media channels supporting it. But when we drive into mobile, JIT takes on another, more personal implication – I’m using this device for this channel because at the moment of need, its just in time to reply.

When was the last time that you went to your mobile for something you needed right now? Was it directions? A movie time? A contact you needed to message? How did it make you feel when you got that desired information? Were you relieved? Or, did you decide that you’d not go that route anymore – hoping that you never were stuck in that same place with that “only known to you” avenue of finding it?

In designing for a mobile context, this concept of JIT has to be taken probably a bit more seriously than everything else. We can see that there’s at least one signifiant set of mobile consumers who can be strictly judged by this JIT approach (see Pew Internet report).

So, when you are designing your application or service – does it matter to a JIT context? Yes, some content doesn’t. Let’s strike that off the board now. Now, to the content that does matter – can it be accessed just as its needed? Does someone have to remember a login code to get there? Do they have to compromise privacy in identity, location, or relationships to get whatever is needed just at that time? Is the value of that extra step worth what’s at the end of the rainbow?

At least from my perspective, many of the apps – and I can argue even down to the mobile platforms themselves – do very little these days to repsect that some information needs to be gleaned as easily as God makes Himself available to us – think it, nav to it, got it. When its not, what breaks in the experience? There are less than 20 app slots on that homescreen – is what you offering as necessary to someone’s life also valuable enough to be put on that screen that’s accessible at the immediate moment of need? If not, did you have the right focus/perspective in building that channel?

Just in time… we get dingged about that towards MMM all the time (hence the design approach taken with the alternate mobile site). If its not available when its needed, then its value diminishes faster than the time it takes to finally get there – if you do get there. Tech is relevant when its personal – but personal matters in the context of being right on time.

 

Trying Out the biNu Mobile App Developer Platform

Friday, May 11th, 2012

Per our usual activities here, we occasionally check out processes and software which would be relevant to the #mobmin (mobile ministry) world. A question for many groups is the process of making a mobile application, and so we definitely like to take a look at the various application creation platforms that are out there to get an idea of what’s needed in terms of graphical, technological, and marketing knowledge to get things up and running. The latest of these development platforms we are looking at is the biNu platform.

biNu is a software delivery platform. Think, something like an app store – but optimized for feature phones (non-smartphones). When there is an opportunity for an engagement to be accented with a mobile app on a (most likely) Java-based mobile, biNu is positioned through its delivery platform to refactor your RSS feeds or any other custom (mobile-lite) page content into a downloadable application for these mobiles.

We took a look at it from the perspective of  a content owner who’s looking to gain a presence on feature phones (its a good idea to read Should Our Church Have an App or Mobile Website prior to this). Therefore, our most important places of entry happen through the biNu Dev portal (still in beta – this comes up again).

Note: the screenshots and activity here were performed on a Windows 7 laptop using the Google Chrome browser. For the benefit of the impression, this is an imposed boundary to using the product.

Step 1: Registering for at the biNU Developer Portal

As with similar services, you have to go through a short process to register for the biNU developer portal (http://developer.binu.com/). After filling out the form, you get a confirmation screen noting that you need to complete a step in your email in order to complete the process. Nice and simple in this respect.

Step 2: Navigating

biNU Developer Dashboard

Once you login, you are presented a straight-forward list of what you’d want to do: List Apps (see all the apps you’ve built), or create a new Basic or regular app. First up on my listing was to do the Basic App (this would most likely be the used option for 1st time users of this service).

Step 3: The Basic App Wizard

biNU App Wizard

Once you get into the Basic App creation wizard, you simply just add the title and description to your app. You do need three graphic files here. Though the sizes were specified, I noticed in the test view that all of them seemed to be resized fine. I’d recommend here not using anything smaller than the recommendation, and you will need to ensure that its a PNG graphic w/o transparency for best effect.

You will also need the URL for the RSS feeds that you would use to populate the app. I took our raw feed, in addition to our Twitter feed and the Twitter feed for the #mobmin hashtag (we’ve done this previously with other apps) and there seemed to be no issue with either of those kinds of sources.

Step 4: Testing/Further Edits

biNu testing emulator

biNu offers a Java-based emulator that gives you an impression of how your content will flow to the smaller screen and different input controls of a feature phone. On the PC that I used, I didn’t update the Java client in order for this to work properly (but you would probably want to do this).

Step 5: Publishing

biNU Publishing Your App

Once you have created and tested your app in the emulator, next is to publish it. There are two avenues for publishing – the first puts the app on the biNu platform “store” where those who’ve downloaded biNu would be able to search and download it among other similar apps/services. The second avenue is for you to generate the app yourself using biNU, and then use publish that app on your website or wider-serving app stores such as GetJar.

biNU Generate Java/Android app

When you choose the option to generate an app, you are taken to a screen that’s similar to the app wizard where you refine the details about your app. What’s most interesting here is that you see the option to generate either a “regular” Java app (ideally, compatible with most Java mobiles) or an Android java app (an apk, compatible with Android devices). Apps can be unsigned or signed using Verisign or Thawte. Again, good options for an app which could be distributed in an open market environment.

Generating the app was the only point in the process where I entered an issue that I had to escalate to biNu directly. As of this writing, this is something being looked at.

Step 6: All Done, Go Build Some More
biNU listed apps dashboard

Once you’ve finished making your app (testing, publishing, and generating Java versions), you are pretty much done. As seen in the publishing step, you’ve been given a URL with which to publicize the app (I’d recommend using a URL shortening service like TinyURL or Bit.ly to make it smaller, more share-friendly, and easier to add to marketing materials). View/Download the 1st MMM biNu app.

Conclusions:

Overall, using the biNu app wizard enabled me to build an app in less than 30min. When I went back through the process to build an app from scratch (see Step 2: Navigating), the process took even less time because the source for the app was an existing mobile website (in this case, our alternate mobile site which is written using HTML5 and jQuery). Given the speed and costs (free) to just get on their platform, this isn’t a bad idea for many sites. I’d like to know how some of the more interactive content offerings would fare here – for example, those doing church online might want this for a presence, but the experience of viewing media on a 2.2in screen that’s not optimized for such “snack time” viewing might be a turn off in some respects. Still, there’s some sense that could be made from doing this and perhaps pointing to your YouTube feed of content.

For more information about biNU, do check out their website. Again, the developer section of the site is in beta right now, so if you enter into any issues with it, do chalk it up to that aspect of things. Still, there aren’t too many mobile services specifically targeting feature phones (more people use these than smartphones by a very wide margin). If your content is ready to go, then biNu should be ready for you.

 

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.

 

How to Select Mobile App/Web Content Options from a Buffet of Offerings

Monday, November 14th, 2011

One of the challenges that larger ministries tend to run into when looking at developing a mobile ministry strategy, or even developing a mobile ministry website, application, or service, is that of taking their entire plate of content and making it mobile-friendly. Chances are, if you are at this place in your mobile strategy, you’ve probably hit a nice speed bump. Here are some tips to help you over that bump and move towards something a bit more digestible to your audience.

First: Understand What It Is People Do On Mobile Devices

This part doesn’t take any complicated statistics, viewpoints, or trends studies. It actually is just one of those common sense moments. You have a product or brand experience that you’d like to offer on mobile. How much of that experience translates well into a 10-30 second glance on a 3.5in screen?

Take email, people get notifications of messages. They check it. They might throw out a short reply. Then the device goes back into their pocket. You might get them to scroll a bit. But, you know how it is – get too much scrolling or the subject matter is too thick and that’s something relegated to viewing on a larger screen like a tablet or laptop.

Think about contexts like this. What about your brand experience translates to how people already use mobile devices? Will what you offer on mobile expand on that existing behavior, or invent something new?

Second: Figure Out All of the Features/Services That You Offer

This might come as a shock, but in many organizations, there are a number of people who don’t visit that organization’s website. Even more shocking, you might find that the people who do visit it don’t go to the places that people who don’t work for the company venture to. This mis-association with websites leads people to not know the entire swath of services/products that the organization offers.

Once you’ve figured out what all it is that you offer. Make a two-column list. Title one column “things I’d like to see us do on mobile” and the other “things I couldn’t see on a mobile.” Then, take that first column and, using your mobile device, do those items. Log that experience. You might need to adjust the number of items in one column versus the other.

Third: Determine What is Uniquely Yours to Offer in/on Mobile

Of that listing of items that “you’d like to see us do on mobile,” there are hopefully some items which are unique to your ministry or organization. These might be siloed items (meaning that they have very loose connections to the overall brand/marketing strategy of your ministry/organization) or that they might be so very custom that it might take some signifiant work with either communications behaviors, technologies, or even convincing executive company members. Still, these are unique to your mission, and have some value if you can determine what in these can go mobile. This is where the bulk of your decision process for specific mobile features needs to lie.

Fourth: Reach for the Low-Hanging Fruit First

The last thing, and the most focused thing is taking that list of what you’d like to do, that’s been filtered to what you uniquely do, and then saying no to everything except one. Go for the low-hanging fruit. This will be your initial mobile app/web/service offering. It will allow you to make mistakes, generate successes, and see a faster return-on-investment for your efforts.

The Example (Fictional, Based on a few Real Ministries)

A ministry has been working in the southern region for sometime, and they’ve created a wealth of communications materials (daily devotionals, newsletters, reading plans, and the occasional multimedia piece that coat-tails on a popular local event). They want to “go mobile” but find that they have entirely too much content, and an unwilling content management system (incl the organizational processes) behind it.

They decide to take a look at their goals for going mobile. Thankfully, this is encapsulated in their mission statement (entreat, reach, and teach). These goals – when viewed through some of the unique characteristics of mobile – flow nicely with that initiative. They look at what they offer right now in terms of features (daily devotionals, newsletters, reading plans, and the multimedia items). All of these can go mobile, but only the daily devotionals are unique to them. They decide that their first engagement in the mobile space will have these daily devotionals as their backbone.

Due to the current reach of those devotionals (email and web analytics give this information), they know that developing a mobile website is a better proposition. They don’t have the in-house resource to create a mobile website from scratch (see other Mobile Web App services), so they invest in the Mobify service in order to make it happen. Those devotionals are already on their website, so they just need to use Mobify’s content editor to add their own branding and styles. At the end of the process, they choose a paid option for Mobify since their was little upfont costs in terms of reflowing content or learning HTML/CSS.

They release the next newsletter, daily devotional, and multimedia event with a link to the mobile-enabled daily devotional. The new m.fictionalministry.com website URL points only to the daily devotional which has links at the bottom of it to be shared with social networks. They also realized during the process that SMS (text messaging) also needs to play a part in sharing, and so they investigated Greater Calling and other SMS service providers whom are able to take the mobile-enabled devotionals and send those as a link via SMS.

We now have a ministry that’s utilized their brand position to take a deliberate and specific step into mobile. With minimal effort, they’ve been able to take existing content and make it available within mobile channels using both web and (version 2) SMS. Using the analytic tools within those services, they can see what works and what doesn’t and refine their plans for other areas of their site assets which need to go mobile. And to those portions of their ministry assets that cannot, they don’t lose the positive feelings generated by what does work well. Its not their entire offering, but just enough to feed the mobile appetite.

Resources to Help

 

How to Determine Your Audience for a Mobile App, Website, or Service

Thursday, November 10th, 2011

Ok, so you have decided that you will take the jump and build a mobile application or website. And in your analysis, you’ve pretty much established that you already know what kind of content it is that you will serve. So what’s left? Well, deciding who exactly to target your mobile efforts towards is one item. Take a look at this graphic recently produced by Asymco which speaks to the published information about global shipments of mobiles

From this graphic (not to mention the data that went into it) we can get an idea of some potential targets for an application or a website on a global scale. For example, we can see from the blue in the graphic that there’s a considerably larger percentage of persons who don’t use smartphones, though this number seems to be getting smaller on a consistent basis (you won’t hear doomsday analysis of the feature phone market here, the numbers bear this as standing strong for the foreseeable mobile futur – i.e., 3yrs easily).

Coming Down from a Global View to A Regional One

Now, this graphic only helps if you are thinking of rolling out something on a mobile global-reaching basis. For many of you, the reach is considerably more regional, and so information like that which Asymco has provided looks best when put against other data, for example, this information from the IDC:

…In Asia/Pacific (excluding Japan) (APeJ), feature phones recovered in the third quarter on the back of Nokia’s resolved inventory channel issues in China combined with the strong showing of its dual-SIM handsets across emerging markets like India and Southeast Asia. With Nokia fighting back at the Chinese low-end competitors, the proliferation of these smaller brands has slowed as margins hit razor-thin levels. APeJ smartphone growth last quarter was driven primarily by Samsung and HTC, as well as ZTE in China. In Japan,the market rebounded sharply after two quarters of either low single-digit growth or outright market decline following the natural disasters of this spring.

The Western European phone market declined as a result of lower demand for both feature phones and smartphones. The smartphone device type growth was mainly driven by mid-tier Android devices. High-end smartphone growth was negatively impacted by Apple’s fourth-quarter iPhone 4S launch, which caused consumers to delay purchases. Meanwhile, Nokia’s transition from the Symbian to the Windows Phone operating system as its primary smartphone platform led to a transition. Feature phones declined as consumers that replaced their devices upgraded to smartphones while others held on to their devices for longer periods of time. Overall the Central Europe, Middle East and Africa (CEMA) markets showed strong growth due in large part to Nokia’s rebound in the regions. Bucking its global troubles, Nokia had a very strong 3Q11 due to feature phone growth. Its smartphone decline continued, however, but it remained the market leader in the region. Among the niche smartphone brands, HTC did particularly well in some markets, including Russia. RIM continues to make progress in the Middle East and Africa, but fared less well in Central and Eastern Europe…

Read the entire Q3 2011 IDC Press release

Now, this information from the IDC is a snapshot of what’s happening with the entire mobile industry (like Asymco’s data), however gives a more detailed snapshot of what’s happening in Q3 of this year compared to next year, and also considering regional and manufacturer differences. This is solid information, and allows an effort to craft a mobile website or application to center onto cultural and distribution details that are a bit easier to manage (languages, platform focusing, etc).

Identifying Opportunities, Tools, and Your Users

What’s left after this is to look a bit more into what it will take to actually build the mobile application or website. For that information, we have to take a look at a few facts: (a) where are the opportunities, (b) where are the tools, and (c) where are the users.

What are some of the opportunities for faith-based mobile apps, websites, and services?

  • Games
  • Funding (not just fundraising)
  • Group Communication
  • Education
  • Health and Wellness
  • News and Information

Or, what are the categories that see the most application downloads (this information is hard to come by, for example just Apple App Store data here; pulling this together requires some effort)?

Where then can we find some of the tools to take advantage of those opportunities?

Specifically Design for Your Specific User

And finally, we’ve got to define where the users are for our application. Not the mythical user. Not the “if we put an app out there, it will be used because they have a mobile” user. The hard numbers. Who in your communities, areas of influence, have expressed such interest in a mobile solution from you that it has effected the ability of your current media offerings to grow? Or, how has the success of mobile for your competitors/partners driven your customers and stakeholders to question your mobile strategy?

It is here that you will want to start researching your user base (or prospective user base) towards whatever mobile experience it is that you intend to craft. That doesn’t mean that you are designing something to please them (part of the effect of mobile is that you surprise and delight because you offer something people didn’t know they wanted), but it does mean that you have a pulse on what they use, what works, what doesn’t work, and where potential consumers of your mobile lie.

Analyzing your user base might mean digging into information that you already have (website visitor data, attendance data, response data from polls/surveys, etc.). And it also might mean that you need to generate means to learn more about your community (surveys, focus groups, feedback forms for events, etc.). But, you have to identify exactly who it is that will be using your applicaiton. Try creating personas for these specific users and then (before developing anything) testing the ideas that you have against them. Then, when you get to the point of testing and looking for feedback to your application, you have some benchmark against which to determine where you proceed with your mobile activity.

Of course, you don’t have to do this work of figuring out your audience. You could very well be the next Steve Jobs and literally have a intuition towards what will work. You also have to have the discipline to make sure that it does work.

Resources, Encouragement
We have some resources that should help you through this process here. But, as we noted above with looking at your users, much of what you need to know about making a successful mobile applicaiton, website, or service is already within the people you serve. Know them, and you know what works.

 

Rash of Upcoming Events

Thursday, October 20th, 2011

google calendar iconGot a rash of items on the plate in the coming months which might pique your interest. These have been (and will be continue to be) talked about on Twitter (@mobileminmag), but here they are for a quick and overall look for you.

Upcoming Presentations

Hackerspace Charlotte Presenation: ‘Minutes to Money – How Africa hacked the cellphone and evaded the CC Cartel’
Oct 25 8-9PM, Hackerspace Charlotte 430 E 36th St Charlotte, NC
Abstract: Discussing the effect of mobile money transfers in Kenya/Tanzania future trends in mobile money transfer

The Geek Fest Presentation: ‘From the Toilet to the Pulpit: The Embrace of Mobile Technology in Faith Circles’
Nov 10 3:45-4:45PM, CPCC Levine Campus, Matthews, NC
Abstract: It is well understood that nearly everyone has a mobile device. It’s also becoming commonplace to see mobile devices used everywhere – to the point that its no longer taboo for people to be found in restrooms using mobile devices. Another area of life that mobile has been quickly finding itself is in religious circles. Starting with Bible applications, mobile in faith circles has moved to educational and media industries to co-bolster those efforts. This talk will describe some of those efforts and how religion becomes the next private place where technology shifts major behaviors.

Call2All Conference ($$)
Nov 29 – Dec 4, Long Beach (LA), California
For more information and to register, visit http://call2all.org
Still hoping to be able to attend this; might not be able to nail doing a presentation though.

Mobile Ministry Forum Consultation 2011 ($$)
December 11-13, 2011, JAARS Offices, Waxhaw, NC
For more information and to register, visit http://mobileministryforum.org

ICCM-Europe ($$)
Feb 8-12, 2010, ‘de Betteld’, Netherlands
For more information and to register, visit http://www.iccm-europe.org/
Hoping to be able to get here as well; sponsorship opportunities available below paragraph at end of this article)

Other Attending Events
BarCamp Charlotte Oct 22nd http://barcampclt.org
Mobile Apps A-Z Oct 27th http://meetu.ps/4CF9l
Responsive Web Design Oct 26th http://meetu.ps/4lC8b

Again, announcements about these hit Twitter first, so stay tuned to use there (@mobileminmag) either via their website or using either of our mobile apps (Nokia/Symbian and Android). Many of the Charlotte (local) events can also be seen via Meetup; as life extends some grace we’ll make local fit into a few more areas.

And to be straightforward, if its possible for to get somewhere to present, and the costs work out (prep and followup are big time sinks), we’ll get there. If you would like for us to share our experience and knowledge and budget is an issue, contact us anyways – faith gets stretched a lot (sometimes more than other times). That’s just the reality of things at this point.

Sponsoring MMM for Conferences/Speaking
If you/your company would like to sponsor MMM for conferences/speaking engagements (this is different than contracting for training or consulting services), get in contact with us so that we can hash out those details and get coverage and insight towards that event that might not be heard/read elsewhere.

 

Mobile App Opportunities

Friday, September 23rd, 2011

Might make this Friday's post; making the NET Bible very... on TwitpicFor as much as I would like to get away from the app-centric culture of mobile, there’s something to be gained for that focused window into a task that opens up an opportunity.

For example, the thumbnail on this post. I’d been using the NET Bible on my Nokia N8 since it’s basically a simple “web” app – it’s simply a collection of static webpages arranged as a site and isn’t in need of me loading any thing more than my browser. However, this “package” was really meant for PCs, larger screens, and mouse-driven input. I wanted to change that and so I started exploring what that could look like (first) in wireframe sketches and later a prototype. Nothing has come of it so far, but it has let me stretch my UX muscles a bit.

Then there are those opportunities that come from others such as the one posted this summer by Dave Bourgeios for aN application that would help people create, gather, and manage small group connections – if you will, something like taking cell groups and adding a communications manager component to it that’s usable from a mobile. Now, (at the time of this writing) I’m not sure of the status of this project, but it again points to some of those opportunities that are out there which might not be big hits, but are nonetheless usable and useful.

As you walk into the weekend, probably with a mobile device or several near you, pay attention to the opportunities that lie right next to you. You never know, someone might also be thinking about it as well and will connect with you to push it through.

Update: Speaking of opportunities: just took a quick look at AppGeyser (AppGeyser.com, @AppGeyser) and built a quick MMM Android app. Download it and give us your feedback.

 

Mobile Ministry Should Not Neglect Accessabiliy Practices

Tuesday, September 13th, 2011

It isn’t often that we can cite the many miracles Jesus and the Apostles did in respect to their efforts to those whom their communities considered disabled or access-restricted. We find it as some of the more sincere and humbling acts of Scrpture when those persons are met and not simply healed, but addressed and considered as part of the greater community, not a layer to be ignored until public relations or peer pressure dictates they need attention (Matthew 5:1-15).

So, how do your mobile ministry practices address those who might be disabled or have restricted access due to physical, psychological, or political disabilities? For example, you built that mobile app for your church’s content, but are you relying on Apple/Google/RIM/Nokia/MS to have accessibility controls so they can navigate to your content, or have you designed high contrast, voice-powered interfaces that are independent of whatever the platform may or may not do?

Regard these words from technokitten in a recent post:

It’s not that big a deal, right? I can still do everything I used to be able to do. I only need glasses for a smidgeon of my time. And it can’t be that big a deal when we’re talking technology? Or so you’d think. My experience with mobile devices and my not-quite-as-good-as-it-used-to-be eyesight is pretty appalling:

  • Going to a website on my phone and being forced to view the mobile version where the font is fixed and is too small (only by 1 or 2pts) to read without my glasses. Why can’t I zoom in or increase the font size?
  • Going to a mobile site where having squinted at the article I’m reading, only to find that I can adjust the font size right at the bottom. That should be at the top, no? There’s little point in struggling to read the page only to find at the bottom, I could have made it a whole lot easier for myself.
  • But neither of those are as bad as the app situation. Oh my word. That is simply horrid and a frustration. And I’m speaking having used apps regularly on Android, Windows Phone 7, Nokia N95 and N8, Android and Palm Pre II. Why can’t I increase a font size in an app? Why does the font have to be so small in the first place?

And this is from a person who is simply speaking of her accessibility needs which tend to happen to us all as we simply age. I know from close relationships just how much even mild disabilities are ignored in computing – and more so when it comes to religious applications and connected services.

Now, you can take the approach that this isn’t your fight. But, you’d have a hard time finding your efforts ministering to much of anyone if you do. Sure, you meet the goals of building something via mobile, but you miss the point of “a love that serves” over simply having a talent (1 Corinithians 12-14).

Or, you can take the approach of getting up to speed on what you can do, even going as far as entering contests such as the Vodafone Foundation Smart Accessabiliy Awards. Its really up to you. The testimony of what you address though will be clear in time (Matthew 25:31-45).