An intermittent issue tracker that does one thing, and does it well
I am an electronics engineer. The most expensive bugs I have chased were never the hardest ones. They were the ones that refused to show up on demand. So I built the tool I kept wishing I had.
Why this exists
Intermittent problems are the expensive kind. A board that resets once a week. A radio link that drops "sometimes". A motor that stutters, but only when it is cold. They have one real talent: they disappear the moment someone qualified is watching. The visit ends with "could not reproduce", and the guessing starts again.
What cracks them is rarely a smarter technician. It is data: every occurrence, with the time and what was going on, and the moments when everything works fine. After a dozen entries the pattern usually jumps out, and the fix turns out to be almost disappointing.
The tools for that were either too generic (notes, habit trackers) or too heavy (industrial software that needs a training course). Nothing in between. This app fills that gap with one job: catch the problems that only happen when nobody is looking.
It comes out of more than fifteen years of hardware engineering, on metro passenger displays, robotic arms, medical devices and client prototypes, and it was built the way we build products at Atallis: start from the real problem, keep what works, remove the rest.
What it gives you
One tap to log an event, wherever you are. Within days, those taps become something rare in troubleshooting: evidence. When it happens, under which conditions, after which events, how often, and whether it is getting worse.
The app separates real links from coincidences with honest statistics (no pattern claimed from three data points), then turns the history into a report a technician, a supplier or an engineering team can act on. Fewer "could not reproduce" visits, shorter diagnostic sessions, and decisions based on facts rather than on whoever saw it last.
Wherever "sometimes" costs money
Prototypes on a test bench, units in the field, a production line that stops for no visible reason, a vehicle fleet, a building. The method does not care what is failing, only that it fails some of the time. I also use it at home, for a fridge that hums at 3 a.m. for reasons it keeps to itself.
That is how I work at Atallis. A product rarely fails inside one discipline. It fails where electronics, firmware, mechanics, users and the business around them meet. I am hands on, scope probe and soldering iron included, but the first question is always about the whole system.
Free, private, no catch
The app is free. No ads, no account, no subscription, no tracking. Everything stays on your phone. We all have enough monthly subscriptions; I was not going to add one to yours.
If it saves you a few evenings of head-scratching, it did its job. And if the problem turns out to live in a product you are developing, you know where to find me.
You have the idea.
Let's make it real.
One conversation is enough to know if we're a fit. No jargon, no commitment, just an honest look at what it takes to build your prototype.