Church community project · Expo app · Hono API
Church QR Attendance
QR attendance, rewards, polls and announcements for a church community, in Arabic and English.
- SQL migrations
- 15
- SQL migrations
- source: apps/api drizzle 0000–0014

The problem
Attendance was taken on paper, so follow-ups on absences and birthdays depended on memory.
My role
- Engineered the application: full-stack development
Engineered during my role as AI & Software Engineer at Elenor Marketing Agency, Cairo (Jan 2026 – present). Screenshots come from sanitized demo environments: client and business data are replaced with demo data.
What it is
Members carry a personal QR code and servants scan it. Progress is tracked per meeting category, with reward sets. The app adds announcements with read receipts, birthday and absence follow-ups, polls, trivia, a spin wheel, meetings, a KPI dashboard and CSV reports. It is a Bun monorepo with a Hono API, an Expo app and shared Zod types.
Key features
- QR check-in with camera scanner
- Three roles: member, admin, super admin
- Push notifications
- CSV reports and KPIs
- Arabic/English with dark mode
Architecture
App
- Member
- Admin scanner
- Super admin
API
- Hono REST
- JWT
Shared
- Zod types package
Data
- Postgres (Neon)
- Expo Push
Stack
Mobile
API
Delivery
Engineering challenges
01
One source of types
A shared Zod package defines every payload once, so the API validation and the app’s types cannot drift.
Screens
Screenshots from the production app running on an Android phone. Real member names are replaced with placeholders, and the phone status bar is cropped.
Next project
Herts Quest