Home   Information   Process

Integrated church management features for a complete experience.

Involvement

PLATFORM : iOS & Android
ROLE : Lead Designer

Research & Testing
UX / UI Design
Visual Design
Art Direction
Sketch Component Library

Overview

Church Community Builder started in 1999 and was privately owned and grew to $17 million in revenue before being aquired by Pushpay in December 2019. We're aiming to be a complete tool for churches—a ChurchOS, if you will. I've been responsible for integrating the ChMS features a congregant would use into the existing Pushpay native app.

Integrated ChMS Features

Historically, the web app was designed to be a Facebook like single platform where both administrators and congregants interacted, but eventually showed a very low adoption of congregants due to a high barrier to entry. Building a congregant facing app created a better experience specifically tailored for them. From the first kick-off with my Product Manager, we explored different design directions to help this product succeed, and at the time, possibly influence the rest of the software.

Early Concepts

Before Church Community Builder was aquired, we had designed a concept of what our own stand alone app could be—from app identity to product design.

Early Component Library Documentation

Final Designs

After the aquisition of Church Community Builder, the direction of the ChMS features pivoted from a stand alone app to integrating within the already and well adopted Pushpay app platform. This meant that I had to retro fit funtionality into existing UX patterns using an established UI library. I collaborated with the App designers to ensure the designs matched the current apps design guidelines, while also testing and introducing new components that weren't defined to help the ChMS features success.

Next Project

Contact

Connect

Instagram
LinkedIn