Articles
Practical notes from real projects: what I built, why I made those choices and what I learned along the way.
- Clair Contour: what a gallery system solves, and what I learnedAn online system for galleries, artists and collectors: trying a work on your wall at real size, private catalogues, resale-royalty records. And what eight weeks of building taught me.
- One sentence, one product: how KlipTrack came to beAn engineering inspection firm could not find a time-tracking tool that fit. How that became a live system in three months, and why we did not customise an off-the-shelf app.
- Work-time tracking without surveillanceLocation-based time tracking for field teams can show attendance without exposing someone's route. Five design decisions and a real example.
- Battery optimisation vs. a reliable background appAndroid manufacturers may stop background apps to save power. How KlipTrack keeps tracking reliably with alarms, notifications, device-specific settings and alerts to the office.
- From Excel to Excel: comparing fleet journeys with working hoursA company's weekly fleet report is compared with tracked work hours using fixed rules. Why a language model should not decide when the report is about people's time.
- Features, not tiers: why almost everything can be switched offKlipTrack has 16 modules, and each company sees only the ones it enables. What stays on, what is optional, and why billing can never disable the phones.
- One developer, one product, three months: building with AIKlipTrack is one developer's work, built with AI assistance. What sped up, where the tools failed, and which decisions stayed human.