Skip to content
Ritesh FirodiyaGet in touch

Work / AskCal / Wiki / Surfaces

analyzing

Surfacecanonicalverified 2026-09-24

SURFACE.MOBILE.SCAN.ANALYZING

Summary

The two-second wait, shown as the shape of the answer.

Raw wireframe

  • .context/designs/mobile/scan/analyzing.html

Why it is drawn this way

A skeleton of the result, not a spinner. The wait explains what is about to arrive rather than just saying that something is happening.

The steps tick through in order and the last one names the thing the product is actually for.

The first step is not the estimator's work at all. It is the shutter writing the photo to the camera roll, and it is listed because the photo was being lost: the camera hands back a URI in a cache directory the OS reclaims when it wants the space, so a user who took the picture, got a bad estimate and wanted to look at the plate again had nothing to look at. This is the moment it happens, so it is the only honest place to say it. A photo chosen from the gallery is not saved again — it is already there.

Known drift: scan/analyzing.tsx also replaces to Out of scans and to Plan unverified, and neither is a link in this wireframe. Both are listed in routes.js under missing.

Related

Sources

  • .context/designs/mobile/scan/analyzing.html

Every project of mine is written down like this.

Read the résumé