The brief I gave myself
Households that employ helpers need to track attendance, advances and the month-end settlement. I wanted an app that does that without asking anyone to trust a server with wage data. I own every part of it: product, architecture, UI, Hindi localisation and store submission.
Local-only, by design
There is no signup and no server. Records live on the device in SQLDelight, inside a shared Kotlin Multiplatform module, and users own their data through export and restore.
Keeping wage data off any server keeps the app outside data-fiduciary scope under India’s DPDP Act, and it gives households a reason to enter real numbers.
A shared data layer like this is also where Kotlin Multiplatform adoption usually starts.
Product rules live in the data model
- Unmarked days default to present, so a worker is never underpaid because someone forgot to tap.
- Half-days deduct exactly half. No rounding surprises at month end.
- Settlement statements are bilingual (English and Hindi), so the employer and the helper can both read every line.
Release engineering
A signed AAB with R8 rules for SQLDelight and kotlinx-serialization, Crashlytics with no names or amounts in the logs, Play Data Safety declarations and a staged-rollout plan.
Where it is now
Live on Google Play after a closed beta with 12–20 households. Jetpack Compose, min SDK 24, target API 35.
Taking a first release from idea to the store like this is what my MVP service covers.
