Mobile & web / Community
OneChurch
A connected home for church communities.
The problem
A church is a community with an operations problem. Leaders need to know who is coming, who needs care, and what is happening this week — without asking an administrator to become a developer.
I built the shared Flutter layer and the admin experience, concentrating on the unglamorous parts: predictable forms, clear empty states, role-aware navigation, and responsive layouts for the web build.
The result is a platform that feels like one product on a phone and a laptop, because it is one product.
What’s inside
Member experience
Announcements, events, giving, and small-group coordination in one place instead of five group chats.
Administration that respects time
Role-based admin screens for attendance, scheduling, and member records built for non-technical staff.
One system, two surfaces
Shared Flutter code deployed to mobile and web, with layouts that adapt instead of stretching.
Safe by default
Firebase hosting and rules keep member data scoped to the role that needs it.
What came out of it
- Cross-platform Flutter with a responsive web build
- Role-aware administration for volunteers, not engineers
- Firebase hosting and rules behind a single deployment