First, you need an expert on-site. Objective C is unlike most other programming languages and working with Apple provisioning, testing and submitting to the App Store is enough to make a grown man cry. Additionally, the lack of standardization amongst platforms like Android, iPhone and Windows Phone 7 increases overhead and is ultimately less economical for one church to produce across all platforms.
Second, companies like Apple are notorious for changing standards and imposing new restrictions on their platforms. Basically, tech support doesn’t exist, good luck talking with a real person, and lastly, they retain the right to reject your app for many reasons. In general, Apple is extremely close-handed about the developing platform.
We love developing for Apple, but they can present many challenges for any developer. Apple makes things appear very easy from a user standpoint, but when you become an iPhone developer, the whole game is changed. Most recently, Apple has changed it’s SDK agreement to eliminate cross platform technologies like Adobe Flash. Thus, using a third party can mitigate some risk associated with developing on these platforms.
If you are a church considering a third party developer, here are some red flags to watch for:
1. If a company offers to build your church an iPhone app for free or “almost free,” be weary. You usually get what you pay for. Support may be spotty or the apps may contain ads—both of which may be out of your control.
2. If a third party doesn’t have any examples of previous work, strongly consider other development shops. If you are using a third party, you want to ensure that they can deliver the quality you want. With over 150,000 apps available, many are third rate, sub-par apps that only contribute to the white noise of the store-both in terms of stability, usability and design.
3. Make sure that your content remains yours. Steer clear of people who want to own or sell your content, but it's common for a third party to maintain ownership of their code. Software as a service is a great option and that would include services like Basecamp from 37 signals, Dropbox, and Beanstalk.
In summary, mobile technology will significantly impact the Church. For churches who are ready to adopt the new technology today, they should carefully consider the the costs and benefits of building a mobile version of their site compared with those of an app. Churches should also be aware of the challenges of developing iPhone apps in house and potential red flags when considering third party developers. For churches who are still on the fence, please consider engaging in the mobile dialogue. Understanding the importance of mobile technology is imperative for remaining culturally and technologically relevant.