Engineering, made inspectable
Behind the Scan.
Follow one QR code through QRify. Every stage has a narrow job, an explicit boundary, and a reason it exists.
The full path
A code is never treated as an instruction to obey.
Choose a stage. The diagram updates with the real responsibility of that part of QRify’s pipeline.
01 · Camera
Receive an image, not a conclusion.
QRify begins with a live camera frame or an image selected through the system photo picker. A scan has not yet asked the app to open, pay, connect, or share.
// QRify makes the steps visible before action scan() → decode() → classify() → interpret() → explain() → user chooses()Local by default
Meaning is built on the device.
Camera decoding, classification, URL semantics, UPI and Wi‑Fi parsing, gallery recovery, and the result experience are designed to work without sending every scan away.
- Local semantic engine
- Parses URL structure, extracts observable signals, considers identity context, and synthesizes an explanation.
- Gallery recovery
- Attempts the original image, orientation variants, contrast adjustment, thresholding and sharpening, then upscaling when needed.
- Clear handoffs
- Browser, Wi‑Fi, UPI, copy, and share actions remain choices after QRify supplies context.
A separate network boundary
External verification is a choice-not a hidden step.
When a user asks to verify a URL externally, QRify uses Firebase Cloud Functions as a protected gateway to a configured provider. The URL being verified is the relevant data; provider credentials stay on the server.
Read exactly what is processed →