Case Study
VBCI Church Directory: Member & Ministry Manager
The original process relied on fragmented spreadsheets, so updates and lookups were slow. I rebuilt it as a full stack directory with a Spring Boot API and typed React frontend, owning endpoint design, data modelling, CRUD/search delivery, and frontend integration.
Why I built this
The original idea started as a small Streamlit project during lockdown: I wanted to replace scattered spreadsheets with something that made it easier to see who was in which ministry and how to contact them.
After Makers, I revisited the idea and rebuilt it properly as a full stack app: a Spring Boot API with a typed React UI. Rather than a quick prototype, the goal was something the church could actually rely on.
The app allows admins to add members, assign them to ministries, search by name/email/ministry, and edit or remove entries as the church grows.
Challenge and solution
One challenge was replacing spreadsheet habits with a workflow people could adopt quickly. I solved it by building straightforward CRUD + live search interactions with a familiar layout, which made updates faster and reduced lookup friction for real users.
Key Features
- Add new members with name, email, phone, ministry.
- Live search by name, email, or ministry with a matching count.
- Edit & delete existing entries in place.
- Clean, branded UI with VBCI styling and responsive layout.
What this project shows
- Comfort working with Java + Spring Boot APIs.
- Ability to build a typed React frontend with Tailwind.
- Experience turning a quick prototype into a structured product.
- Focus on solving a real world, community based problem.