API Strategy & Roadmap
Looking back, only for moment…
Almost a year ago to the day, Fellowship Technologies deployed the Fellowship One REST API into production. We were excited to achieve this milestone since it represented months of dedicated work by our development team. Since then committed developers, vendors, and our own staff have come together to form a Community dedicated to bring solutions to the church world. I am encouraged and edified by the fantastic work that has been accomplished. Good work!
If you cook it, then you better be prepared to eat it…
We believe that the best way to prove our API can accomplish what others need it to accomplish is to use it ourselves. No… I am not talking about for just some things like a mobile app that does this, or a CMS shared login, or vendor solution integration. I am talking about using our own API for the majority of our mainline product development. We call it eating our own dog food. (The good juicy kind!) If we build an API that is comprehensive, hearty, and reliable enough to support the production code of thousands of users and millions of calls every day; then simple logic leads us to the conclusion that it will serve the greater Community’s API needs.
Strategy is for generals, we’re in the trenches…
Hang on! We really believe we’re on to something. If we are going to consume our own API for most everything we develop moving forward, then we better have an API to consume or we won’t be developing our own end-user solutions. Something about a cart and horse, which must come first? Well, we are going to make the API the horse. Our goal is to make the API production available ready to the Community at the same time or before our own end-user application solutions.
Be honest, can you convert vision into reality?
Most likely in September of this year, we will production deploy a Remote Deposit Capture solution for our Fellowship One Enterprise customers. Remote Deposit Capture will enable churches to process checks from a high speed scanner and post contributions into Fellowship One. Care to take a guess how we built this feature? Bingo! Yes, we built a Giving Realm for the REST API, and developed the entire solution consuming our own API. Does this mean Fellowship One now has a Giving API? Well, yes again.
Dog food is suddenly appealing, can we try some?
We are just asking that you give us a few more weeks to test, and then we will provide the Community access to the new Giving Realm API. In this first iteration we have resourced the data that allows inserting, editing, and retrieving individual contributions. I hope the Community’s creativity is positively challenged to conceive inventive solutions with the Giving resources, especially when used in conjunction with the existing People Realm API. Got some ideas already? Share them with the Community!
Two requests please, foot on the gas and rev up the RPMs…
We believe the patterns are solid now that two API realms have been established. Our next development user story is to develop an API auto-generation framework. Feed the auto-generation framework a data model on one end and API resources come out the other. Hmmm, sounds like RESTful sausage. Based on Community requests (and our own mainline development needs) our goal is to whip up a plate of Groups resources for an API consumer feast before the end of 2010.
What’s for dessert?
What would you like?
Scott Lowrie joined Fellowship Technologies in 2004, and has served as the Director of Product Management for the past three years. He enjoys turning shared ideas into workable solutions.
- Include Requirements & Contribution Sub Types
- User Case Story from Hope Community Church
- Group Search Categories and More
- Account Creation
- Single Sign On Functionality Exposed
- API Communication Value Changes
- API Enhancement: Create and Edit Groups!
- API Enhancement: Requirements Exposed
- Resource Versioning
- Enter Visitor Data via Your Church Website
- Fellowship One & Planning Center Online
- API Libraries and Sample Code
- Building a custom login for your church website using the API
- Roll Foward!
- The Agile Triangle
- Conversation Paralysis
- Picture this, image updates & creates through the REST API
- A REST API double shot : Groups and Events realms
- Increasing Software Delivery by 500%
- Quick people API realm update
- Introducing the new REST API giving realm
- Raising the bar…
- Building a Deployment Pipeline
- The World of Dev Craft
- Running Tests in Parallel with Selenium
- Abstracting Your Code to Remove Duplication
- Documentation in an Agile Environment
- Drowning in Debt
- Intro to Ruby on Rails
- API Strategy & Roadmap
- Staging/Sandbox Environment is Back up!
- Downtime in Sandbox/Staging Environment
- Android & OAuth
- F1 API Static Library with Objective-c
- Programming in F#
- NoSQL: HuMONGOus Benefits (Part 2)
- Our Scrum Team Structure
- SaaS & BI - The History & Future
- Getting Started with Android
- NoSQL: Leaving Schema Behind (Part 1)
- Your Feedback…and a $25 Gift Card!
- A Scrum Ceremony? Is this a wedding or something?
- Variables in PHP
- Data Exchange API Fixes
- F1 Check-in on the iPad
- Be the first to get the news & tips!
- An Introduction to PHP
- Working with Pop Up Windows in Selenium
- List Comprehension
- Source Control: A Time Machine For Your Source Code
- Developer Conference…Lower Price, Same Great Content!
- The Quality Assurance Team
- How does Fellowship Technologies manage complex projects?
- Developer Conference coming in May!
- Sandbox Refresh Complete
- Sandbox Refresh This Week
- Updates coming to the REST API
- Sandbox Environment Down Time
- F1Touch :: Fellowship One On The Go
- Under the Hood
- Sandbox Refresh Complete
- Sandbox Refresh Tomorrow (Oct. 2nd)
- Fellowship One Developer Forums
- Ten Commandments of API Consumption
- REST API Enhancements / Fixes deployed to Sandbox and Production 09.09.09
- Data Exchange URL cut-over complete
- Important Data Exchange URL changes
- Ron Nom Nom
- How to get started using the REST API