Mobile, backend & web
Sistem Kebun
Connecting offline field records with plantation administration and payroll through Flutter, Go, and Next.js, with conflict handling and protected payroll finalization.
Read the case study for Sistem Kebun ↗- Keep field records consistent
Each queued operation retains its identity across retries. Local cache, changes, and synchronization cursors are persisted together; database transactions keep business changes, sync records, and audit entries consistent.
- Make concurrent changes visible
Record versions detect conflicting edits instead of silently overwriting them. Managers can review conflicts and trace corrections through an audit history.
Mobile, backend & admin panel
Sales Force
Connecting field sales with a Laravel admin panel, using encrypted attendance and visit queues, scoped access, and idempotent requests to keep records consistent.
Read the case study for Sales Force ↗- Retry without duplicate records
Queued requests retain their identity and payload. Idempotency and ordered dependencies prevent duplicate activities and keep check-out behind a successful check-in.
- Respect organizational boundaries
Permissions combine with team and area scopes. Mobile users access their own activities, while supervisors and administrators receive access appropriate to their responsibilities.
Mobile & backend
KelasKita
Connecting classes, flashcards, and quizzes with a Go backend that checks access, enforces deadlines, processes attempts, and supports automatic and manual grading.
Read the case study for KelasKita ↗- Keep assessment rules on the server
The Go API checks deadlines and uses transactions for answer submission. A separate worker processes overdue attempts, keeping timing rules outside the mobile countdown alone.
- Model access at resource level
Role checks are combined with ownership and class membership. Authentication uses Argon2id password hashing, Ed25519 JWTs, and refresh-token rotation.