Skip to content
All work
AI ProductsFull case study

Keto Scanner

Point, scan, decide — in three seconds

A barcode and label scanner that tells people whether a product fits their diet. I designed the scan-to-answer loop, the confidence and correction states, and the onboarding that teaches the app's limits honestly.

Role
Product designer — AI UX, mobile UI, prototype
Category
AI Products
Industry
Health & Nutrition
Platforms
iOS, Android
Year
2025

The problem

What was actually wrong

The recognition model is good, not perfect — and a nutrition app that confidently gives a wrong answer costs a user's trust permanently. The design had to be fast when certain and visibly careful when not.

The work

What I did, in order

  1. 01

    Designed the result screen around a single verdict people can read at arm's length in a supermarket aisle, with the reasoning one tap below it.

  2. 02

    Created three distinct confidence states — confident, uncertain, unrecognised — each with its own visual language and its own next action.

  3. 03

    Built a correction flow that takes seconds, so a wrong result becomes training data instead of an uninstall.

  4. 04

    Wrote onboarding that states plainly what the scanner can and cannot read, setting expectations before the first failure rather than after it.

  5. 05

    Optimised the camera screen for one-handed use with a trolley in the other hand — the actual context of use.

Key decisions

The three choices that mattered most

Every project has a handful of decisions that shaped everything after them. These were this project's.

The verdict comes first

A large, unambiguous yes/caution/no, then the numbers. Nobody reads a macro table while standing in an aisle.

Uncertainty has a design

When the model is unsure the UI says so and asks a single clarifying question, rather than guessing and being confidently wrong.

Wrong answers are cheap to fix

A two-tap correction path turns the app's worst moment into its best feedback loop.

What was delivered

  • AI interaction model
  • Scan & result flows
  • Confidence & error states
  • Onboarding sequence
  • High-fidelity UI
  • Prototype & usability testing

Tools used

FigmaProtoPieMaze

Files were handed over annotated and component-based, with a live walkthrough for the engineering team.

Have a product like Keto Scanner?

Tell me what is not working. I will tell you honestly whether design is the right lever and what I would do in the first two weeks.

madnansakhi@gmail.com