Compound Maintenance System
For Residential compound — Egypt
A purpose-built mobile application replacing WhatsApp-based ad-hoc coordination with structured incident reporting, community confirm/dispute voting, and an admin operations dashboard.
Compound residents and admins relied on WhatsApp groups to report utility outages, coordinate maintenance, and share announcements. Messages were lost, resolution times went unaccounted for, and there was no structured way to confirm or dispute an incident. The work delivered here replaces that chaos with a purpose-built tool.
What we delivered
A bilingual mobile application with two role-shaped flows. Residents see an all-clear hero state when nothing is wrong — and a structured report flow when something is. They can confirm, dispute, or withdraw votes on incidents others have raised. Admins see an inbox-style operations queue: open incidents, ETR management, maintenance request triage, and announcement broadcasting. Devices activate through invite codes issued by the compound — no email, no password — and sessions persist quietly in the background.
How we worked
A compound resident — the real end-user, and the person on the receiving end of the WhatsApp chaos where genuine updates got buried in endless group-chat discussion — joined the build as the embedded domain expert. They mapped the incident lifecycle from the receiver’s perspective, which is why the resident dashboard leads with the all-clear hero state and community-confirm voting, rather than being modelled around admin workflow.
A note on resident testimony, in their own words:
“كنت بتوه عالواتس عن الرسايل اللي بتوضح معاد الصيانة في وسط طلبات و شكاوي تانية كتير. دلوقت أي معاد صيانة واضح و كمان بيجيلي به نوتفيكيشن.”
“I used to lose track of the WhatsApp messages telling us when maintenance was happening — they’d get buried under all the other requests and complaints. Now any maintenance schedule is clear, and I even get a notification for it.”
— Farah, compound resident
