Explicit feedback dies after week two. People are there to move freight, not to be your annotators. If confirmation requires an extra tap that does not help them, they will stop tapping.
Dwell is the signal they cannot help giving. They open a record to read the bin, the pack qty, the photo. If they bounce in 400ms, the match was probably wrong even if they did not say so.
Thresholds that respect the floor
I do not treat a one-second view as a label. I look for a pause long enough to read a location — a couple of seconds — plus a navigation pattern that looks like work: copy, scan next, or walking to a bin.
False positives happen when someone opens the wrong card and stares in confusion. That is why dwell is weak confirmation, not ground truth. It is still better than nothing, and it scales.
Combine it with the rare explicit no
The reject button stays. Dwell fills the positive class. Rejects fill the negative class. Together they give you a loop you can run without a data team and without begging for ratings.
