Repair management portal

Phone repair is, in practice, a sector full of paper, key tags with labels, post-its on the counter, and missed calls. For a client I contributed to a platform that helps repair businesses manage their work simply and securely — without forcing them to throw their existing way of working overboard.

The portal streamlines the full repair process: registering a device, intake and diagnosis, handing over to the workshop, status updates, completion, settlement, and pickup. Every step has an owner, a timestamp, and a traceable status, so 'lost in transit' — literally and figuratively — happens far less often.

At the same time, the platform gives customers insight into their repair progress and any costs. For repair businesses this means fewer 'is my phone ready?' calls; for customers a much more comfortable sense of control in a process where they are temporarily without their device — often an important personal one.

On the front-end we used Angular 4 with Angular Material. Material gave us a quick path to an interface that looked polished out of the gate, plus a component set that's pleasant to operate in real-world conditions (rapid clicking at a busy counter). On the back-end was Vert.x on Java 8, allowing us to process many real-time updates without making the platform heavy.

We invested time in a smooth build pipeline (Webpack) and in tests with Karma. Nothing spectacular, but exactly the kind of foundation that lets a team safely ship small changes often — which in an operational platform like this is far more valuable than large, rare releases.

The project showed me again that 'simple' workflow software is often an underestimated kind of work. Where the end result feels light and obvious, underneath sits a lot of thinking about edge cases, roles, statuses, and user habits. That's exactly where the value to the client lives.