Get the next teardown in your inbox.

One email when a new teardown is out. Free, one click to leave.

We'll email you a link to confirm. No account, no password.

Teardown 11 · CraveLens, food from your screenTrust 50%

Teardown 11

CraveLens

A trust product that hides what it is doing

What Ayush said · teardown

“A Chrome extension that watches what you're doing on your laptop, suggests food that fits the moment, and orders it from Swiggy for you, with payment by scanning a QR code.”

10 screens · about 3 min

start ▶

Something on screen makes me hungry. I want it now.

Teardown 11 · CraveLens, food from your screenTrust 50%55%
{TAP}

Fig. 1: The real home page: a Chrome plugin that orders what you crave.

A plugin that orders food

A plugin that orders what I crave. Okay.

What Ayush said · walkthrough

“you can add it as a Chrome plugin to your Chrome”

Teardown 11 · CraveLens, food from your screenTrust 55%65%
{WAIT}

Fig. 2: The site's own mockup: the dish on screen, matched.

It saw the pizza

It saw the pizza on my screen. Wow.

What Ayush said · walkthrough

“whatever you do on your laptop, you will be able to look for that particular kind of food”

Teardown 11 · CraveLens, food from your screenTrust 65%70%
{TAP}

Fig. 3: Setup: pick the model that checks what you watch.

My own model

My own model, on my laptop. Good.

What Ayush said · walkthrough

“you can use a local AI model, or you can add your own model if required”

Teardown 11 · CraveLens, food from your screenTrust 70%45%
{TAP}

Fig. 4: Five closed sections, and nothing shown until you open one.

Options, all folded up

What are my options? All folded up.

What Ayush said · walkthrough

“there were multiple accordions where I was not able to view what options are present”

Teardown 11 · CraveLens, food from your screenTrust 45%35%
{WAIT}

Fig. 5: Inside Swiggy now, and only a spinner says so.

Doing what, exactly?

It's inside Swiggy now. Doing what?

What Ayush said · walkthrough

“What is actually happening in the backend itself?”

Teardown 11 · CraveLens, food from your screenTrust 35%25%
{TAP}

Fig. 6: A cart and a Pay button, before any sign of how it chose.

Pay, before I trust it

I'm not letting this spend my money.

What Ayush said · walkthrough

“This creates a non-trust factor for the user to use the application itself.”

Teardown 11 · CraveLens, food from your screenTrust 25%35%
{TAP}

Fig. 7: Scan with your phone, pay from the laptop.

Pay by scanning

Paying by QR from the laptop. Neat.

What Ayush said · walkthrough

“I do like the idea of you being able to pay for the meal from the laptop itself by just scanning the QR code”

Teardown 11 · CraveLens, food from your screenTrust 35%30%

Fig. 8: Where most people actually watch: no CraveLens here.

Not where I watch

I watch on my phone. It isn't there.

What Ayush said · walkthrough

“Most of the time, there are a lot of people who are using a mobile phone to do this.”

Teardown 11 · CraveLens, food from your screenTrust 30%55%

Fig. 9: The same card, showing its work before it spends.

Show each step

Show me each step before it spends.

What Ayush said · teardown

“Show what the Swiggy MCP is doing in the backend, step by step, to build trust.”

Teardown 11 · CraveLens, food from your screenTrust 55%

What mattered

The journey

Trust, slide by slide

Three moments

  1. 04Options, all folded up
  2. 05Doing what, exactly?
  3. 08Not where I watch
Teardown 11 · CraveLens, food from your screenTrust 55%

C

Our grade

Trust product, hidden work

A trust product has to show its work.

What Ayush said · teardown

“Interesting idea, and context-triggered ordering is a real wedge. But it's a trust product shipped with an opaque UI, and a mobile-first behaviour served on desktop only.”

next teardown ▶