A QR-based product authentication experience designed to help consumers identify suspicious products, verify authorized product identifiers, and make more confident purchasing decisions.
View Full Project
Read case study
Two new projects are being written up right now. Want an early look at the work in progress?
Ask for a PreviewI’m Sanand — a UI/UX designer from Kerala who turns complex problems into products that feel effortless. I care about clarity over decoration, honesty over hype, and design decisions you can measure.
The interface should never compete with the information it is trying to communicate.
Transparent states and clear limitations build more trust than any visual flourish.
Every decision comes with a reason, a user benefit and a way to measure whether it worked.
Senior UX Designer
Senior Art Associate
Layout, typography, branding and visual storytelling
UX Anudeep · Learning programme
Full history, dates and recommendations on LinkedIn.
Understanding the people, the problem and the gaps — so the product solves something real.
Framing goals, principles and priorities so every screen serves a clear purpose.
End-to-end flows and interfaces for mobile and web — minimal, intuitive and accessible.
Interactive prototypes and reusable design systems that keep products consistent as they grow.
Start with a question, not a solution. Map the problem, the people and the moments that matter.
Turn insights into user goals, design goals and a principle the whole product can be judged against.
Shape flows, states and visual language — with every decision tied to a reason and a metric.
Prototype, test with real users and be honest about what is designed versus what is built.
What if you could know a product is genuine before you trust it?
A smarter way to verify. A simpler way to trust. A QR-based product authentication experience designed to help consumers identify suspicious products, verify authorized product identifiers, and make more confident purchasing decisions.
Counterfeit products are becoming increasingly difficult to distinguish from genuine ones. Packaging can look convincing, product information can be misleading, and consumers often have no simple way to establish whether a product can be trusted.
VERIQ brings product verification into one straightforward experience. Scan a code, understand the result, explore product details, and report suspicious activity.
Consumers are expected to identify counterfeit products without access to reliable verification tools. So I started with one question:
Imagine buying an expensive pair of headphones. The packaging looks authentic. The branding is familiar. Everything appears legitimate.
But something feels off.
You search online, compare product images, inspect the packaging, and look for reviews. Yet none of these things can confidently tell you whether the product is genuine.
And that is the problem. Consumers are expected to identify counterfeit products without having access to reliable verification tools. The more convincing counterfeit products become, the harder it is for ordinary consumers to distinguish them from genuine ones.
I started exploring a simple question:
Why should verifying a product be harder than buying one?
That question became the starting point for VERIQ.
Having a code isn’t the same as verifying a product. A meaningful check needs a trusted source, a reliable process and an understandable result. Three gaps stood out:
QR codes, barcodes, and serial numbers already exist on countless products. But simply having a code doesn’t mean consumers know how to verify it.
There is a difference between scanning a code and actually verifying a product. A QR code can direct someone to a website. A serial number can identify a product. But a meaningful authentication experience needs a trusted source, a reliable verification process, and an understandable result.
I identified three important experience gaps to investigate:
Consumers need a verification process that doesn’t require technical knowledge or complicated steps.
A successful scan should communicate what was verified, what evidence supports the result, and what it means.
Users need guidance when something looks suspicious or when the system cannot establish authenticity.
A successful authentication experience isn’t about showing a green tick. It’s about helping people make a confident decision.
I wanted VERIQ to feel like a trustworthy product rather than another complicated security application.
Every design decision was made around one question: How can I make product verification feel effortless while maintaining the credibility of the result?
1
2
3
The home screen gives scanning the strongest visual priority — people open VERIQ to verify a product, so that is where they start.
Most applications introduce users to multiple features, menus, and options. VERIQ starts with the one thing users came to do: verify a product.
1
2
3
A clearly defined scanning frame and simple positioning instructions guide even first-time users through the scan.
Scanning is the central interaction, so it needs to be intuitive even for someone using the app for the first time.
Instead of presenting a complicated camera interface, the scanner focuses on a clearly defined scanning frame and simple positioning instructions. The experience should guide users through the process rather than expecting them to figure it out.
Genuine, Suspicious and QR Not Recognized — because an unknown identifier is not necessarily a counterfeit.
This was one of the most important decisions in the project. A verification system cannot treat every result as either genuine or fake.
An unknown identifier is not necessarily counterfeit. A network error does not indicate fraud. A duplicated identifier requires context. I designed three distinct outcome states.
The identifier matches an authorized issuer record and has passed the checks shown in the result. The user can review the product information and verification evidence.
The system identifies a specific security concern, such as a revoked identifier or suspicious reuse. The user receives an explanation and guidance on what to do next.
The system cannot establish a result because the identifier is unsupported, information is unavailable, or a technical issue prevents verification. The user can retry or contact the brand.
1
2
3
4
Results explain what was checked — the product, its issuer, identifier status and timestamps — instead of asking users to trust an icon.
A green check mark can communicate success, but it cannot explain why something should be trusted. I wanted the verification result to provide more context.
1
2
3
4
A suspicious result leads straight into a short, structured report — pre-filled where possible — instead of ending at a warning.
What happens when someone discovers a suspicious product? The experience shouldn’t end with a warning message.
I introduced a reporting flow that allows users to submit a concern with relevant information. Where information is already available from the scan, it should be automatically populated.
Seven live scanning conditions tell users exactly what is happening — and what to adjust — before frustration sets in.
Most failed scans aren’t caused by the code — they’re caused by the conditions around it. A silent camera leaves people guessing why nothing is happening.
So the QR scan screen reacts in real time, with seven conditions shown right below the scanning frame. Tap any of them to see the actual screen.
The screens bring the design decisions together into one continuous experience — shown here as the four journeys a user moves through.
A calm introduction, a home screen that puts scanning first, and a camera that guides instead of waiting.
Three results that are impossible to misread — each with a clear next step.
Evidence behind a genuine result, and a short report when something looks wrong.
Every check is saved and searchable, and can be filtered by genuine or fake results.
I wanted the interface to feel modern, minimal, and approachable. Rather than relying on conventional security aesthetics, the visual direction focuses on clarity, typography, spacing, and meaningful status indicators.
Modern, minimal and approachable — clarity, typography, spacing and meaningful status colours instead of conventional security aesthetics.
#0B0B0B#04FF54#EA4D4D#2B61B4#FFA000Obsidian Black establishes the primary identity. Green communicates a genuine result, red a suspicious one and blue a QR code that isn’t recognized, while amber guides the scan.
Space Grotesk creates a readable hierarchy and keeps information easy to scan.
Consistent buttons, cards, status indicators, and input fields create a predictable experience across the application.
Subtle feedback, clear loading states, and purposeful transitions help users understand what is happening.
The interface should never compete with the information it is trying to communicate.
VERIQ is presented as a design concept. Its proposed experience and its technical implementation should be distinguished clearly.
VERIQ is a design concept: the full consumer journey is designed and prototyped, while the verification infrastructure behind it still needs to be built.
Designing a verification experience and building a reliable authentication system are two different challenges. The interface can communicate a result, but the credibility of that result depends on the infrastructure behind it.
The initial experience focuses on consumers, but the platform has opportunities beyond individual product verification.
A dedicated platform where brands can register products, manage identifiers, and review suspicious activity.
Allow consumers to understand relevant product information and available supply-chain history.
Help retailers verify products and report suspicious inventory before it reaches consumers.
Identify suspicious patterns through contextual scan history and other reliable signals.
Extend the verification experience to electronics, cosmetics, fashion, packaged goods, and other participating product categories.
VERIQ could become more than an application for checking products. It could become a connected layer of trust between brands, retailers, and consumers.
Working on VERIQ highlights an important distinction between designing an attractive interface and solving a meaningful user problem.
The initial challenge appears simple: scan a QR code and tell someone whether a product is genuine. But the deeper challenge is much more complex.
The lesson: good UX is not just about making interactions faster. It is about making information understandable, decisions easier, and limitations transparent.
These questions shaped the direction of the experience.
The biggest lesson from this project is that good UX is not just about making interactions faster. It is about making information understandable, decisions easier, and limitations transparent.
If I were to take VERIQ further, I would prioritize validating the result experience with real users and working with an authorized brand to test the verification infrastructure.
VERIQ. Scan less uncertainty. Trust with confidence.