Mablagh: a cash and earnings ledger for delivery drivers
Project status: delivered for a client and complete. A mobile app for Android and iOS, prepared for release and submitted to Google Play for review. Paymentery delivered the whole project, from requirements and design to development and store release.
The problem the app solves
Delivery drivers collect cash from customers all shift, often working with several agencies that settle differently: one expects the cash handed over, another deducts its share from electronic payments. By the end of the day it is hard to know how much cash is really in hand, how much of it is theirs, how much belongs to the agency, and what they earned after tips and expenses.
The client asked for an app that answers these questions instantly, records an order in seconds while working, with no account and no server, and never lets the driver's figures leave the phone.
What was built
One-screen order entry
Amount due, what the customer paid, tip, keypad and summary on a single screen. The change due and the split between agency and driver are shown before saving, with quick-pay amounts the driver configures. The reference order takes five taps.
Clear figures at every moment
The home screen answers directly: cash on me, my share, the agency's share, what they owe me or I owe them, and what I earned this shift.
Shifts, agencies and settlements
Opening and closing shifts with a cash count and any difference recorded, multiple agencies on hand-over or deduction, partial and final settlements, and fixed daily or per-shift fees.
Reports, export and any currency
Weekly, monthly and custom-range reports, with PDF export in Arabic type and CSV. Built-in currencies including the Albanian lek, or any currency with its own symbol and decimals.
Privacy and security
No account, location, ads, analytics or server; the Android build does not even request internet access. Data is stored in an encrypted on-device database (AES-256, SQLCipher-compatible), with its key held in the Keychain or Keystore.
Backups are manual and encrypted with a password the user chooses, with an optional PIN or biometric lock and a full erase option. Google Play declaration: no data collected or shared.
Engineering
An auditable accounting engine
Every action is stored as an immutable event; edits and voids are new events, and balances are replayed from the full log. Amounts are integers in the currency's minor unit, so there are no rounding errors.
Tests before every release
More than 140 automated tests cover accounting rules, storage, encryption, backup and user journeys, including a 130% large-text test.
Flutter, Arabic-first design
One codebase for Android and iOS; every screen was designed and approved in Figma before development, right-to-left with an English version.
Delivery stages
- Requirements analysis and documented accounting rules and edge cases.
- Screens, design system and interactive prototype in Figma, approved by the client.
- The accounting engine and its tests, before any interface.
- Encrypted storage, backup and app lock.
- App development and testing on a real device, fixing what real use revealed.
- Release preparation: icon, signing, privacy policy, support page and store forms.
Outcome
A complete, store-ready app was delivered: the Android build has been submitted to Google Play for review, and the iOS build is ready for App Store release. Drivers record an order and see their figures instantly, and their data never leaves the phone.
Have an app idea?
Describe the users and the problem you want to solve. Scope and the right technology are reviewed before work starts.