How Sneh checks its own work
Before calling a build done, Sneh opens the app, walks through it on desktop and mobile, and reports honestly.
What checking means here
Sneh opens the app it just built and actually looks at it — on a desktop viewport and a phone viewport — rather than assuming the code it wrote does what it intended.
It then reports two lists: what works, and what does not yet. The second list is the point. A build that looks finished but is broken on a phone is not finished, and you should hear that from Sneh rather than from a visitor.
Reading the report honestly
If something appears under “not yet”, it is not a failure of the build — it is Sneh being straight with you about the state of the app. Some entries are things it can fix on the next turn; others are platform limits it cannot fix at all, like custom domains.
Checking reduces surprises. It does not make the app perfect, and it is not a substitute for you clicking through the thing yourself before you send it to anyone who matters.
Read next
- When a build goes wrongWhat to do when the preview breaks, a change makes things worse, or Sneh keeps missing the point.
- The Product BriefSneh writes a plan before it writes code, and asks you to approve it. Here is what is in it and why it matters.
Did this miss what you needed? Email hello@sneh.ai — or browse the rest of the help centre.