I’m a HUGE fan of using APIs.
Brian’s post caused me to think about all of the APIs that I use to give the “big bad wolf”, aka time, a good fight.
I regularly use Flickr, Facebook, Twitter, Vimeo, Amazon, Church Community Builder, Twilio (Texting), and a host of other APIs for projects. Using APIs allows me to manage and store information on other websites and display that same information on my church’s website without having to do it multiple times. I simply program a few lines of code and BANG! I see my data present on a web page where I can style the data the way I like or need.
Saves Time and Effort
In addition, this makes information particularly easy to access via the web and it saves my co-workers (who are trying to change things on the website and do not know how to code) both time and effort. It also saves me a great deal of time by not having to do it for them!
One step further
I wonder why there are not more church applications offering APIs. It only makes sense to me that web companies marketing to churches make available APIs to create, read, update, and delete. In fact, the more companies doing this, the better.
For example, I have been vocal on Twitter about Youversion releasing an API, as a part of it’s application, to display bible verses and other features that I can incorporate on my church’s website. Right now, this option does not exist. It seems that the more open churches and companies that market to churches become about making things available via APIs, the more we will see potent church web apps being built.
These apps would work wonders for advancing the Kingdom! The secular world does a great job in this area and it is time for the church to catch up, then take the lead.