01 · Mobile Engineering · Kotlin Multiplatform · API Architecture
Mobile Token Retrieval Experience
Lead Software Engineer (Mobile & Backend Architecture)
- Kotlin Multiplatform
- Compose Multiplatform
- Ktor Client
- PHP
- Laravel
- REST API
- KMP / Compose Multiplatform client
- Laravel modular monolith REST API
- Request validation + rate limiting
- Server-side upstream token-record adapter
Problem
Customers needed a reliable self-service channel to retrieve previously purchased prepaid electricity tokens when standard SMS delivery failed or when recent token details needed to be looked up directly on their mobile device.
What was built
A hosted customer-facing Kotlin Multiplatform and Compose Multiplatform mobile application backed by a modular Laravel REST API that mediates retrieval workflows against an existing upstream token-record system.
Decision that mattered
Separated token retrieval from the system of record via a dedicated Laravel API boundary that keeps upstream credentials server-side, validates meter inputs, enforces per-instance rate limiting, and dispatches analytics recording after the HTTP response.
Tradeoff
Accepted maintaining an intermediate backend API service rather than direct mobile-to-upstream calls to guarantee credential isolation, uniform response contracts, and independent rate-limit controls.
Outcome
Hosted production application rolled out to all users on 1 November 2026 and actively used by customers to retrieve primary-meter and submeter token records.
Hosted production system rolled out to all users on 1 November 2026; architecture documented in case study.
