The case study
Context
Danquah Worship Centre runs its congregation on a web-based church-management system. Its staff and members needed the same records in their pockets.
The challenge
Bring a large web system to a phone without duplicating it: the app has to respect every permission the Centre already defines and speak the system’s own API.
What we built
- Secure sign-in with the session token held in secure storage, and routes guarded by that person’s permissions.
- A member directory, member records and a self-service profile.
- Events, an attendance console, public check-in and attendance analytics.
- Visitors and visitation tasks.
- Care requests — prayer, welfare and new converts.
- Announcements with authoring, a resource library with upload, SMS campaigns and reports.
Engineering scope
A Flutter app with 46 screens and 74 permission-aware routes, built on twelve repositories that talk to the Centre’s system API.
Design decisions
- One source of truth: the app reads and writes through the Centre’s system rather than keeping its own copy.
- Permissions travel with the person: every route checks what the signed-in person may do.
The delivered system
A Flutter app for staff and members, built against the Centre’s system API. We publish no member or visitor information from the project.

