Mobile Ministry Magazine (MMM)

Posts Tagged ‘mobile application’

How to Build an App for Your Ministry

Monday, September 19th, 2011

@Ew4n @jebbrilliant just sketched this in Tactilis; thoughts? on TwitpicWhile we’ve talked in the past about the considerations you should taken when looking to build a mobile application or mobile website, we’ve not had for sometime a post that leads you down a few simple steps to having an app (ignoring website for the moment) for your ministry. The below items are strictly high level and may not apply to all ministries in the same manner – however, this should at least give you a starting point from which to build and market a mobile application experience for your ministry.

Step 1: Collect and Organize Your Content

Figure out what it is that should be in your mobile app. Whether its sermons, announcements, videos, music, or all of the able, you need to know what’s going in the app (and why it deserves to be there).

Create a small organizational chart that lists where these will be in relationship to how someone will use it. For example:

  • Home
  • Latest Sermons
  • Latest Videos
  • Calendar and Networking
  • Pastor’s Blog
  • Help/Support

Your outline might be a touch more in-depth than this, which is fine. The key is making sure that you at least know what’s going into your application and at a high level what you will be building.

One of the things that I like to do at this step is to use either a physical whiteboard or my iPad to create a general wireframe of what it is that the app should look and function like – sometimes including points to other systems that feed into the application.

You may decide that you want something other than a Bible/sermon/brochure app – that’s a good thing. Outline your expectations and what should be in there as well.

Step 2: Figure Out Your Mobile Platforms

There are several mobile platforms out there, and its very hard for any ministry to support them all. I recommend that you do some kind of survey (informal is just fine) toward figuring out the kinds of mobile devices that people have to which you will be creating this application for.

This doesn’t mean that you will only target one platform (such as Apple, Google, BlackBerry, etc.), but it does mean that you have an idea of what your potential use base will be.

You may also need to do additional research on mobile applications and many other parts of the mobile industry. We’ve got a list of resources that can help you get started (warning, its a lot of reading).

Now, here’s the important point, if you/your ministry is making the statement they want to support every platform *no questions asked,* then you need to stop thinking about an application at this point and point your energies towards making your website work best for mobile devices.

Step 3: Build or Buy

For the next step, you need to figure out if you are going to build the application from scratch, or purchase a application service-platform with which you’ll use to build your application.

Our list of mobile website and mobile application services

If you have decided that you will build your application from scratch, and your outline for what you want to offer looks like our example above, this is the type of team that you want to have in place for the least amount of fuss:

  • 1-3 mobile application developers who know the ministry’s current content management system
  • 1 software tester
  • 1 person who understands all of the current produced content within your ministry
  • 1 person who understands all of the current and near-future marketing messages within your ministry
  • 3+ people who will simply support the effort by prayer alone
  • 5-10 people who have the target devices and are ok with being a closed beta testing group
  • 1 person to document the application, frame/organize training if needed

This is optimal. This isn’t always what happens, and in many cases one person carries many of the hats mentioned here. The bigger the expanse of the application however, the more these specific points need to be taken into account.

If you’ve decided that you will build your application from a template (application-creation service), these are some of the items and people that you’d need:

  • 1 person who is responsible for creating and/or collecting all of the graphic assets that will be used in the application (ideally, this is the same person already responsible for this for web and other marketing materials)
  • 1-5 people who would be available to create or edit text content that will be used within the application
  • 1 person who understands the technical requirements and capabilities of various mobile application development platforms
  • 1-3 people to build the application on the mobile application development platform
  • 1 person who understands all of the current produced content within your ministry
  • 1 person who understands all of the current and near-future marketing messages within your ministry
  • 3+ people who will simply support the effort by prayer alone
  • 5-10 people who have the target devices and are ok with being a closed beta testing group
  • 1 person do document the project, application, frame/training, and manages the relationship with the application-creation service provider

Step 4: Build the Application
At this point, its just a matter of getting the code, graphics, and media together into something that nearly-works.

Its in this step that you are testing the application. The developer(s) should be testing as they go along, your test grip should have some kind of structured testing script that they are using. Don’t over-do the testing, but also don’t be afraid to take the medicine either. If something isn’t working, this is the time to figure that out.

If you are working with an application-creation service, they might also offer consulting services to help you through this part of creating your application.

Step 5: Promote Your Application

No matter if you have built the application from scratch, or used an application-creation service, you need to now let people know that there’s an application available from your ministry.

First, use the communication channels that you always use for announcements (during service, in the bulletin, on social networking services, etc.). That’s the easiest and least expensive way to get some attention for your application. If you do this quietly (“going viral”), then you might also catch som issues that might have been missed in the formal testing rounds.

Second, connect with media outlets that cover ministry and technology applications and ask if they would be open to reviewing or republishing the press release about your new application. In many cases, this opens new audiences for your ministry, while also allowing you a glimpse into what other people might think of your ministry offering (feedback is always good).

Third, use your application in public. Outside of contemplative or video applications, there are very few reasons not to fire up your ministry app when waiting in the line at the bank or at the doctor. Bonus points if your ministry’s senior leadership doesn’t just use the application to posture the project, but genuinely enjoys engaging your ministry resources in this manner.

Step 6: Update and Enhance

Things don’t end when you have released the application. Back in your testing queue, you most likely found things that were “better left to version 2.” Taken advantage of that information and get to work on version 2 of your application. You don’t need as large a team as you had the first time around to add those iterations, but it does help if you can keep your testing team(s) engaged.

Help! This is too much!

It is totally understandable that these steps are a bit more involved than simply opening the app store and saying “create me an app.” If you want it done right, you’ll do these, and similar steps in order to make sure that not only you create a great application, but that the experience of using it follows the expectations that you have.

If you find that you are having trouble in getting through these steps, MMM offers consulting services to help you and your ministry get through these moments. Contact us to set up a free, initial consultation (our rates afterward are reasonable for both the knowledge and niche that is mobile ministry software). If you are a developer or development company looking to get connected to ministries who need an app or mobile service, we can get you connected, drop us a line.

And now you can move forward making your ministry and your mobile application to being the best experience that it should be, and a solid representation of Christ to your community and the world.

 

Of Applications and Motivations

Friday, September 3rd, 2010

Been thinking a bit about some of the statements made in that Future of Bible Software piece. Sometimes, a bro can be a bit far-reaching, and other times, I simply expect more out of us all than what’s probably realistic.

I mention this because I’m thinking about my primary mobile device (a Nokia N97 running the Symbian^1 operating system) and why I no longer have a Bible reader application on it. Part of the reason is becasue I’ve found it better in many of the gatherings that I attend to simply listen to what’s being said, using my mobile to note important points. Other times, I’m in a setting where the larger screen and UX of the iPad plays a better role for things.

I wonder though about going back to having something more than a link to preferred Biblical resources on my device. Something that isn’t a Bible reader, but does give me some of the benefits of a quick and targeted search. I don’t (necessarly) need to even bookmark the passage, but I do need to possibly copy it (or tweet it) so that I can recall it later.

And so, I thought some about the Biblia API project started by Logos, and how simply their releasing of this API releases them from an expectation of having to create an application [for me] – but it puts the onus on me to learn how to use that pipe for the kind of content experince that I desire. I’m in favor of such a move, because it is indirectly causing some aspects of the user-base of Bible applications to become fishers of content themselves, and creators of more personal solutions.

However, I’ve not started to crack open the book(s) on learning this API, nor how best it could be used in my kind of a scenario. In some passing conversations with Brett (MMM’s latest team member), his expressed desire to learn to develop for various platforms has rubbed off on me. I want to learn how to use that API, and do it in such a way that adds value to my Biblical needs, not just scratches an itch for information at my fingertips.

What I have been doing is planning my approach. For example, I know that I want something that’s not a native application – it needs to be a web runtime (WRT) widget. The widget would need to have two panels: the static one on my homescreen would just display an icon to the left and the Scripture references to the last two or three items I searched for (there’s no room for more than that). Clicking on the widget would take me to an expanded view where I see a listing of my latest searches (5-7 perhaps) and a search box at the bottom where I could put into it any measure of references, boolean operators, and phrases, which would then spit back to me on a similar screen the results of the search. Clicking on a search result would automatically add it to my “history,” open the browser to the biblia.com website to that reference, and on the widget there’d be a button at the bottom to go back to my search results screen. Because this is a widget, it wouldn’t need to save anything, so when I close it, the only things really saved are my history of the references I went to, not the search queries.

In my mind, on my mobile device, this is something that’s very possible. I don’t necessarly need an app anymore than I can develop one myself. The pipes are there, and I can do with the content what I can based on legal and ethical agreements.

It has me thinking hard about the future of applications as a whole, but also how we are motivated towards creating our own experiences or doors into searching and valuing the availability of Scriptural content. I can’t say that at this moment that I’ve moved forward past what I’ve said here, but I am thinking that something like this should happen nearer than in the future.

 

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

Mobify