Showing confidence scores: designing UI that admits uncertainty
Our scanner is right 80 to 90 percent of the time. The interface is designed around the other 10 to 20.
Surendra — Tejvon
Senior Android & BLE Engineer
Our offline scanner is right 80 to 90 percent of the time. That is a good number, and it also means some fields on some cards will be wrong. The interface has to be honest about that.
After a scan, the user sees a review screen with every extracted field. Each one shows how confident the app is in it, as a percentage. High-confidence fields can be skimmed. Low-confidence fields are the ones to look at.
The alternative is to present everything as if it were correct. That feels cleaner, and it fails badly. The user finds one wrong phone number, stops trusting every other field, and starts checking each card by hand. At that point the app has saved them nothing.
Showing confidence does the opposite. It tells the user where to spend their attention, so a review takes seconds. They can correct a field or add something the card did not have, and move on.
We also apply the same thinking to the photo itself. The crop is automatic, but the user can adjust the edges if the app got it wrong. The app does the work by default, and it is always clear how to correct it.
Topics
Working on a similar challenge?
Let's discuss the architecture before you build.
BLE system design, OTA reliability, and connected product engineering — this is what TEJVON does every day.
Book a Technical Consultation