property-detail

Summary

One listing, drawn twice: before the buyer pays and after.

Raw wireframe

• .context/designs/mobile/buyer/property-detail.html
• .context/designs/web/buyer/property-detail.html

Why it is drawn this way

Two screens, not a screen and a state. Locked and unlocked are the same record with different fields masked. They are separate files — property-detail.html and property-detail-unlocked.html — because the journey moves from one to the other through the unlock sheet, and a state collapsed onto its screen would hide that step in the chart.

The mask is the server's, and the reviewer's. Floor, wing, flat number, parking spot, exterior photos, the exact pin and the owner's contact are hidden by default. A reviewer can override any of them per listing. The frontend is sent the masked shape and cannot un-mask it — see design-principles.

Favorites knows which one to open. An unlocked favourite links to the unlocked screen and a locked one to the locked screen.

Related

• catalog — the visibility defaults, field by field
• unlock-confirm — the step between the two
• load-bearing-flows — the unlock transaction

Sources

• .context/designs/mobile/buyer/property-detail.html
• .context/designs/web/buyer/property-detail.html