Originally, the ChurchApp was created to answer a specific question: How do churches provide their congregants with tools and resources that will help them continually engage with the church as a whole? However, the ChurchApp can only function when paired with Seraphim in a tight integration. To discuss the ChurchApp, we also have to look at Seraphim.
Through the Blackbaud acquisition, we realized that the core of Seraphim, the features that set it apart from other products on the market, were great ideas. However, the User Interface (along with browser restrictions and hardware requirements) needed improvement. It was then decided that we could actually rebuild Seraphim from the ground up using the lessons we've learned about the church market. The first thing you'll see is that the new Church Management Solution will be accessible through any browser, on any device, on any platform. This means you will be able to log into Seraphim from PC's or Macs, iPadsand tablets, and even on your smartphone. This new Church Management Solution will receive a major upgrade in usability and interface design as well.
In order to reach the new product state, we need to focus development resources so that we can achieve a new level of Church Management Software. Since, we will be creating a new "Seraphim", we will also be creating a new "ChurchApp" to integrate with it. This new app will ultimately replace the current app. To accomplish this, we need to pour our development resources into the new solutions. As such, there won't be any major releases put toward the current ChurchApp. Does this mean the ChurchApp is completely defunct? No, it does not.
But it does mean that we recommend that any church that hasn't already implemented the ChurchApp should avoid doing so.
Because of our limited development resources on the current ChurchApp product, we believe that only churches that are already using the ChurchApp should continue to use it. The ChurchApp can only be considered in a "Beta state" at this point in time, and may be difficult to implement. However, you can feel free to run some test use cases with the ChurchApp, to see if the ChurchApp in it's current state would be a sufficient tool for you and your team. With this in mind, we cannot guarantee a perfect app experience, and therefore we want to make sure you're not dealing with avoidable product frustrations while we're working on a new solution.
All in all, we believe the future is a bright one! With this in mind, we think it would be best to hold off on implementing the ChurchApp for you and your team. If you have any questions or concerns, we'd be happy to discuss this further.