Problem or limitation
Once users run an algorithm with custom inputs, there is no way to revisit previous executions. If they want to compare different inputs or replay an earlier visualization, they must manually enter the values again and rerun the algorithm.
Proposed solution
Introduce an Execution History panel that automatically stores recent visualization sessions locally in the browser.
Implementation steps:
- Store each completed visualization in
localStorage.
- Save:
- Algorithm name
- Input values
- Visualization settings (speed, etc.)
- Timestamp
- Add a "History" button in the visualizer toolbar.
- Allow users to:
- Replay a previous execution
- Delete individual entries
- Clear the entire history
Alternatives considered
A backend-based history synced across devices was considered, but local storage is simpler, requires no authentication, and keeps the feature lightweight.
Use case
Students frequently experiment with multiple inputs while learning. Being able to instantly replay previous executions makes comparing algorithm behavior significantly easier.
Additional context
History should persist across browser sessions while keeping only a limited number of recent executions (e.g., the latest 20) to avoid excessive storage usage.
Problem or limitation
Once users run an algorithm with custom inputs, there is no way to revisit previous executions. If they want to compare different inputs or replay an earlier visualization, they must manually enter the values again and rerun the algorithm.
Proposed solution
Introduce an Execution History panel that automatically stores recent visualization sessions locally in the browser.
Implementation steps:
localStorage.Alternatives considered
A backend-based history synced across devices was considered, but local storage is simpler, requires no authentication, and keeps the feature lightweight.
Use case
Students frequently experiment with multiple inputs while learning. Being able to instantly replay previous executions makes comparing algorithm behavior significantly easier.
Additional context
History should persist across browser sessions while keeping only a limited number of recent executions (e.g., the latest 20) to avoid excessive storage usage.