№ 313 / The agent’s edition
Make a property comparison sheet
Both views share scale and labels so illustrative changes are obvious.

IN EVERYDAY WORDS
Both views share scale and labels so illustrative changes are obvious. Align the views while inspecting the original office.
The look
Source view → Paired comparison. Both views share scale and labels so illustrative changes are obvious. Keep the agent’s property presentation as the visual subject.
Say this to a designer
On my agent’s property presentation, align the views while inspecting the original office. Show “Source view” and “Paired comparison”. Both views share scale and labels so illustrative changes are obvious.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- The visitor controls “Align the views” with touch, pointer or arrow keys.
- entrance
- Begin with the recognizable state “Source view” in view.
- path
- Source view → Paired comparison. Both views share scale and labels so illustrative changes are obvious.
- timing
- Follow the visitor’s input directly. For a replay, traverse the full study in about two seconds.
- easing
- Use linear tracking for scrubbing and a gentle ease at both ends of a timed replay.
- hold
- Hold “Paired comparison” while the viewer inspects the result or opens the brief.
- exit
- Retain the source, the visitor’s input and the identity of the property throughout the interaction.
The vocabulary
- Align the views
- Both views share scale and labels so illustrative changes are obvious.
- Reference endpoints
- “Source view” and “Paired comparison” define the two checkable states of this effect.
Make it fit your project
Good places to use it: agent’s property presentation, the agent’s edition example.
Apply this to the agent’s property presentation when the visitor needs to see the change from “Source view” to “Paired comparison”.
Watch for: Retain the source, the visitor’s input and the identity of the property throughout the interaction.
When motion is off: Show the two named states “Source view” and “Paired comparison” on demand. Keep automatic movement off.
Implementation and accessibility
- Align the views while inspecting the original office.
- Start in “Source view”. Bind the control “Align the views” to one reversible value between zero and one.
- Source view → Paired comparison. Both views share scale and labels so illustrative changes are obvious.
- Retain the source, the visitor’s input and the identity of the property throughout the interaction.
- Inspect the two endpoints and the midpoint on a narrow touch screen. Verify the result using the keyboard.
- Give “Align the views” an accessible name and keyboard controls.
- Expose the before and after descriptions as text.
- Load the active study’s assets on demand. Stop rendering while its stage is off screen.
Give it to your AI
Download the working source and example assets. Match this reference number in the included catalog to its renderer.
Replace [ELEMENT] with the part of your project you want to change. The prompt includes the design brief, motion direction, definitions, and implementation steps.
Read the full prompt
Use AI Acceleration Design Ref #313 (Make a property comparison sheet, version 1) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/313. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: Both views share scale and labels so illustrative changes are obvious. DESIGN REF #313 · Make a property comparison sheet In everyday words: Both views share scale and labels so illustrative changes are obvious. Align the views while inspecting the original office. The look: Source view → Paired comparison. Both views share scale and labels so illustrative changes are obvious. Keep the agent’s property presentation as the visual subject. Say this to a designer: On my agent’s property presentation, align the views while inspecting the original office. Show “Source view” and “Paired comparison”. Both views share scale and labels so illustrative changes are obvious. Motion direction (starting points to adapt): Trigger: The visitor controls “Align the views” with touch, pointer or arrow keys. Entrance: Begin with the recognizable state “Source view” in view. Path: Source view → Paired comparison. Both views share scale and labels so illustrative changes are obvious. Timing: Follow the visitor’s input directly. For a replay, traverse the full study in about two seconds. Easing: Use linear tracking for scrubbing and a gentle ease at both ends of a timed replay. Hold: Hold “Paired comparison” while the viewer inspects the result or opens the brief. Exit: Retain the source, the visitor’s input and the identity of the property throughout the interaction. Design vocabulary: Align the views: Both views share scale and labels so illustrative changes are obvious. Reference endpoints: “Source view” and “Paired comparison” define the two checkable states of this effect. Reduced motion: Show the two named states “Source view” and “Paired comparison” on demand. Keep automatic movement off. Implement: 1. Align the views while inspecting the original office. 2. Start in “Source view”. Bind the control “Align the views” to one reversible value between zero and one. 3. Source view → Paired comparison. Both views share scale and labels so illustrative changes are obvious. 4. Retain the source, the visitor’s input and the identity of the property throughout the interaction. 5. Inspect the two endpoints and the midpoint on a narrow touch screen. Verify the result using the keyboard. Adapt the reference to my branding and content. Preserve existing functionality and semantic HTML. Reduced motion: Show the two named states “Source view” and “Paired comparison” on demand. Keep automatic movement off. Accessibility: Give “Align the views” an accessible name and keyboard controls. Expose the before and after descriptions as text. Performance: Load the active study’s assets on demand. Stop rendering while its stage is off screen. Avoid: Retain the source, the visitor’s input and the identity of the property throughout the interaction. Show me the working result, verify keyboard, mobile, loading/error and reduced-motion behavior, and explain any tradeoff. Do not publish or change unrelated elements.
Permanent reference #313 · version 1. Pairs with #040, #003.