1a1A complaint with no visible progress is a complaint nobody files twice
Submitting into a void is exactly the experience residents already had with the phone line. If the app reproduces it, it has added nothing.
0The facts
- Role
- Client project: mobile development
- Year
- 2025
- Status
- Shipped
- Category
- Mobile
- Built with
- React Native · TypeScript · i18n · Firebase · React Query · Reanimated · Zod · Push Notifications
- Where to find it
- Google Play
1 · Overview
What it is, and why it exists.
A service app for residents and visitors of Ajloun: raise a municipal complaint from home and track its resolution, and browse the governorate's archaeological and tourist sites.
Two audiences in one app: residents who need something fixed, and visitors who want to know what is worth seeing. The municipality wanted both, and separating them into two apps would have meant neither got installed.
The complaints side lets a resident raise an issue within the municipality's remit and receive its resolution without leaving home. The tourism side covers the archaeological and heritage sites across the governorate.
1a · Challenges
Each problem got a card. Each fix got filed behind it.
1a1aWhat I did
Every complaint carries a status the resident can see, and status changes push a notification. The value is the visible state transition, not the submit button.
1a2Complaints arrive with photos on rural connections
A photo is what makes a complaint actionable, but uploading one from a village on weak mobile data fails often enough that people give up mid-report.
1a2aWhat I did
Images are compressed on the device before upload and the submission is queued, so a report survives a dropped connection and completes when signal returns rather than being lost.
2 · Results
- Published on Google Play for Ajloun Governorate.
- Municipal complaints with tracked status, plus a heritage site guide.
3 · Screens
Next project
→Sawt
Automating an election, from voting to results.