Hey everyone 👋 Daniel here — maker of LapLog. I built LapLog after noticing something surprisingly common: most manufacturing teams still time assembly cycles using a phone stopwatch… and then write the numbers down on paper. It works — but it’s messy, slow, and the data rarely turns into real insight. LapLog digitizes that exact workflow: • Tap to record laps • Add structured issue tags • See instant summaries • Export clean CSV data All data is stored locally on your device.

Hey everyone 👋 Daniel here — maker of LapLog. LapLog started from something surprisingly simple: engineers timing assembly line cycles using a phone stopwatch… and then writing the numbers down on paper. It works — but it’s messy, slow, and the data often gets lost or never analyzed properly. I built LapLog as a lightweight digital replacement for that exact workflow: • Tap to record laps • Add structured issue tags • See instant summaries • Export improvement-ready data No heavy MES system. No complex setup. Just practical lean timing. While building it, I realized the real problem wasn’t timing — it was turning raw seconds into insight. So the product evolved from “a stopwatch app” into a small but focused improvement tool. If you work in manufacturing, lean, CI, or production — I’d love to know: How are you currently recording cycle times? Paper? Excel? MES? Something else? Excited to hear your thoughts 🙌