CranleyGitHub

Tracks

Peri: Forward Deployed Challenge

A small business is in no dataset. The iPhone app scans the shop, and the owner keeps a PDF with numbered fixes and a list of what was not checked.

Judged real-world need, usability (could the business adopt it immediately), execution.

State: no business consulted yet. The entry is only eligible with a business name, the person’s name and role, and one piece of evidence.

Angle if a business is consulted. A small business in Princeton is not in CoStar’s data. The iPhone app scans the shop, and the same tools answer the questions a fire inspector or a wheelchair-using customer would ask: step-free route from the door to the counter, door widths, occupant load from the measured floor area, exits, smoke alarms seen in photos. The output is a PDF the owner keeps, with numbered fixes and what was not checked. They could use it the same day.

Scripted flow: web/src/skins/app/demo/flows/peri.json, “A business checks an office and keeps the report”.

Demo path. The owner’s quote and photo first, then their problem in their words, then the scan-to-report flow on their space (or the demo cafe if they declined a scan), then the report.

The demo

The Cranley iPhone app running a fire safety site visit on the made-up test cafe (1 of 2)The Cranley iPhone app running a fire safety site visit on the made-up test cafe (2 of 2)
A site visit in the simulator on the made-up test cafe: pick the report, and the checks run on the scan.

In the docs