Case study, 2015–26
Keeping an 11-year-old Android scanner app running Konga’s warehouses
Every order the Konga app sells has to physically move. Warehouse staff scan each waybill from origin, through incoming and outgoing, to last mile, on an Android app that dates from the Eclipse era: an 11-year-old Java codebase still running on handheld scanners across Konga’s warehouses. I own it.
- Role
- Senior software engineer, owner
- Where
- Konga Group
- When
- 2015–26
- Stack
- Java, Android support libraries, Handheld barcode scanners
Legacy that still pays
Not every important app is new. This one has been moving parcels since 2015, and the waybills don’t stop while the rest of the stack is modernised. A crash on a scanner doesn’t show up as a bad review; it shows up as parcels waiting at a hub.
What owning it means
I keep it stable on the devices it already runs on, and I recently extended it to new scanner hardware, so Konga can buy current handhelds without waiting on a rewrite. The goal is simple: logistics should never wait on software.
Why it matters next to the Flutter work
I’m also rebuilding Konga’s shopping app in Flutter. The scanner app is the other end of that chain: the app sells the parcel, this one moves it. Keeping both running is what lets the modernisation happen without the business feeling it.