UI version history
Git for user interfaces.
fossil keeps a visual history of your web app’s UI through the scans you run. Compare captured versions to see how the screens and flows have changed.
What did that screen look like?
A code change can tell you what was edited. A captured interface helps you see the experience that was there: the copy, the layout, the choices and the screens around it.
Capture your app before a redesign, name that version, then scan again after the release. Compare the retained results to review changes to the interface alongside the code.
Put the old interface beside the new.
During a UX review, compare captured versions to see what changed: a button’s label, a form’s layout or the choices in a signup flow. Keep viewport and scope comparable so you can discuss the same screens with your team.
An old screen is more useful with its path.
Return to the captured flow map to see the interface around an observation. A screenshot shows what was visible; the map shows where that screen belonged in the journey.
What “Git for interfaces” means here
Versioned visual evidence and comparison. fossil does not create Git branches, merge code, roll back deployments or restore the application itself.
Frequently asked questions
Does fossil continuously monitor my app?
No. You choose when to scan. The history contains the versions you captured, so changes between scans may be missing.
Can I restore an older interface?
You can revisit retained captured evidence. Restoring the running product requires changes in your own development and deployment workflow.
How long are versions available?
Retention depends on your plan. See Pricing for how long your captured versions remain available.