Zero Considerations is written and supported by one person. There is no ticket queue, no chatbot, and no call centre — there is an email address, and I read every message that lands in it.
How fast will I hear back? Usually same day or the next. I aim to answer everything within two business days. I am one person with a day job, so a busy week can stretch that — if you have heard nothing after three business days, assume the mail got eaten and send it again. Resending is not rude; it is genuinely useful.
Sending a bug report costs you nothing and it is the only way I find out something is broken. The app collects no analytics and phones nothing home, so if you do not tell me, I do not know.
Most reports that stall do so for one reason: I cannot reproduce them. Five lines of context usually fixes that. Copy this block into your email and fill it in — anything you cannot answer, leave blank.
App version and build: (Settings → About, e.g. "0.14.10 (build 100)") Phone and OS: (e.g. "Pixel 7, Android 15" or "iPhone 13, iOS 18.5") Where it happened: (which screen / which step of the session) What you expected: What actually happened: Detection details text: (paste it — see below)
Open the app → Settings → scroll to About. The line reads Version 0.14.10 (build 100) or similar. The build number matters more than the version — several fixes have shipped inside the same version string, and it tells me immediately whether you already have the fix.
Camera behaviour, image sizes and the on-device detection models differ enough between handsets that "it does not work" is unanswerable without this.
This is the important one, and it is the part people usually skip.
When a photo step fails or gives a result you did not expect, open the Detection details disclosure on that screen. It prints exactly what ran — how many of the four corner markers were seen, which decode sizes were tried, how sharp the frame was, and whether each detection engine loaded. Select that text and paste it into your email verbatim.
It matters because those cases look identical from the outside and are completely different problems. "No corner markers seen" is a framing or lighting problem you can fix in ten seconds. "Marker engine: FAILED TO LOAD" is my bug, on my side, and no amount of retaking the photo will help — that exact failure once masqueraded as a photo problem for weeks. The disclosure is there so you never have to guess which one you are looking at, and so I never have to guess either.
For anything involving the camera, the target, hole detection, scale or markers, the photo is the bug report. Please attach:
On your photos and your privacy. The app never uploads anything — if I have a photo of yours, it is because you attached it to an email yourself. I use it to reproduce your problem and nothing else. If you would rather not send a photo of your actual target, a photo of a printed sheet with a few holes punched in it reproduces most detection bugs just as well. Please do not send anything you would not want in someone else's inbox.
Send them. The single most useful message I have ever received was a tester telling me one sentence of onboarding copy was confusing; that turned into a rewrite of every instruction in the app. Small, specific complaints are worth more than long wish-lists — tell me the moment you got stuck.