Server time, not the phone's clock
Timestamps come from the server, so changing the device clock can't move a check-in.
Presensi PKP Pemerintah Kota Pangkalpinang · Diskominfo
The official attendance app for the Pangkalpinang city government. Civil servants check in with GPS and a selfie, request leave and review their history. Every late minute is on record, and bonus cuts are based on it.

Attendance used to be signed on paper. Someone who arrived late could still write down an on-time arrival, and some staff filled in the whole five-day week in one go.
The record matters more now: the bonus is cut by how late someone is and by every absence. BKPSDMD, the city's civil service agency, needed attendance it could trust.
| Paper sheet | Presensi PKP |
|---|---|
| The time is whatever the person writes down. | The time comes from the server, so changing the phone's clock does nothing. |
| A whole week can be filled in at one sitting. | Each check-in happens on the day, inside the office geofence, with a selfie. Fake GPS is refused. |
| Nobody can tell how late anyone really was. | Lateness is counted to the minute, and bonus cuts follow the record. |
I designed the app and built it in Flutter for Android, iPhone and iPad, from one codebase.
I listened to BKPSDMD, the city's civil service agency, about what the paper sheets got wrong: late arrivals written down as on time, and whole weeks filled in at once.
I designed the check-in, leave and history flows myself, so the screens went straight into the Flutter build with no hand-off.
Flutter with Clean Architecture and BLoC, and Firebase Crashlytics, Performance Monitoring, Analytics and Cloud Messaging, so problems in the field show up on a dashboard. Released on Google Play and the App Store; version 1.0.9 fixed the four crashes Crashlytics ranked highest.
Timestamps come from the server, so changing the device clock can't move a check-in.
Mock-location and spoofing attempts are detected and blocked, so a check-in means the person was really there.
Crashlytics ranks every crash by how many people it hits. The top one, a Retry button on the location dialog that did nothing, reached up to 64 users on version 1.0.8. Version 1.0.9 fixed the top four.
Trade-off: A rare camera crash on Android 13, seen by 2 users, waits for a later release.
Each feature splits data, domain and presentation, and every call returns a result or a typed failure, so the attendance rules are tested without a device: 104 tests, BLoCs included.
On an iPad, content stops at a readable width instead of stretching edge to edge, and system text size is capped at 1.3× so large fonts don't break the layout.
















Attendance is now recorded on the day, where people actually work, with lateness counted to the minute, and bonus cuts follow that record.