reversa-visor

To document a legacy interface from screenshots without runtime access, you can extract screens, components, and navigation flows from static images. This builds structured UI specs and state documentation for later use without requiring the system to run.

Yes, you can map navigation flows using static images by identifying primary and alternative routes between documented screens. The process maps navigation routes and records state differences across the same screen when multiple screenshots are provided.

The best way to extract form fields and UI elements from legacy screenshots is element-level documentation. This process extracts and documents form fields, tables, list actions, navigation structures, and user feedback components like toasts and modals.

Yes, UI documentation from screenshots requires reading Reversa configuration files. These files determine the output folder and documentation granularity before producing per-unit screenshots storage, spec files, global inventory, and Mermaid flow outputs.

To track loading and error states for legacy UI documentation, capture multiple screenshots of the same screen. The process records the state each screenshot represents, including loading, empty, filled, error, and confirmation states.