Production case study

Parker Diaries — Milk Delivery System

Android app for delivery staff to track delivered products, record customer payments, and keep daily logs for a milk distribution company.

AndroidJavaRetrofitSQLiteMVVMFirebase

View delivery system overview

Client: Parker Dairies
Engagement: Delivery operations product
My role: Android engineer

Offline-friendly

field use beyond reliable connectivity

One workflow

deliveries, payments, stock, and logs

Field to cloud

local work with Firebase synchronization

01 · The brief

The assignment and its real constraints

Replace fragmented daily delivery and payment records with a focused workflow that delivery staff could use in the field.

Keep core delivery work usable when connectivity is weak or unavailable.

Make frequent field interactions fast enough for staff working through a delivery round.

Preserve operational records across local use and later synchronization.

02 · My mandate

What I owned

✓Turned delivery-round activities into a focused Android workflow.
✓Implemented local persistence, API integration, and Firebase-backed synchronization.
✓Connected delivery, payment, stock, instruction, and daily-log records in one product.

03 · Technical judgment

Decisions that shaped the system

Design for the field first

The core workflow remained useful away from reliable connectivity instead of assuming every doorstep interaction could reach the backend.

Keep related operations together

Deliveries, customer payments, stock, instructions, and daily logs shared one operational flow to reduce fragmented record keeping.

Synchronize around local work

Local storage supported immediate field activity, while Firebase-backed synchronization connected those records to the wider operation.

04 · Execution

From discovery through production

Step 1
Mapped the recurring actions delivery staff needed to complete during a round.
Step 2
Reduced delivery, payment, stock, instruction, and logging tasks into a focused Android flow.
Step 3
Used local persistence for field continuity and Firebase-backed synchronization for wider operational visibility.
Step 4
Structured the application with maintainable networking and presentation boundaries for ongoing product changes.

System delivered

The production surface

Delivery rounds and field activity tracking

Customer payments, stock, and delivery instructions

Offline-friendly field workflows for delivery staff

Daily records that keep operations synchronized with the wider system

05 · Result

Production outcomes

Replaced fragmented field records with one workflow for deliveries, payments, stock, and daily logs

Added offline-friendly flows for delivery staff working away from reliable connectivity

Connected field activity to the wider delivery operation through Firebase-backed synchronization

Evidence & disclosure

Parker Dairies publicly describes a large doorstep-delivery operation, while the public MDS delivery-system overview highlights rounds, payments, stock, delivery instructions, and offline support.

Public scale and product claims are attributed to the linked source. Delivery details reflect my direct role; confidential client data and implementation details are intentionally omitted.

Review public source

Need someone who can clarify the real constraint, make the technical trade-offs explicit, and stay accountable through production delivery?

Discuss a project