EyeWorks vs GazePlotter

EyeWorks manages eye-tracking research from study creation through recording, analysis, and reporting. Its Design stage lets researchers script instructions, questions, images, web pages, videos, and external interfaces. Record captures eye data alongside keypresses, audio, scrolling, mouse clicks, and video for remote viewing. Analysis includes heatmaps, GazeTraces, GazeClusters, GazeStats, GazeClips, BeeSwarms, Dynamic Heatmaps, statistics, charts, graphs, and tables. Results can be exported to CSV or standard statistical analysis packages. Optional modules add cognitive workload, scene-camera recording, multi-display tracking, and face and eyelid tracking. Scene Camera supports mobile and tablet apps, physical media, objects, and real-world environments. EyeWorks is described as compatible with eye trackers from all major manufacturers, with native integration for leading simulation products and an SDK for customer software. Editions are Design, Lite, Pro, and Premier. Pricing is on request. The software supports Android and iOS; Windows Phone devices are supported through Scene Camera. EyeTracking was founded in 1999 in Solana Beach, California.

GazePlotter is a free tool for researchers and non-programmers to visualize eye-gaze data without writing code. Its analysis options include scarf plots, AOI comparisons and timelines, transition matrices, recurrence plots, scanpaths, scanpath similarity, metric timelines, and metric correlations. The metrics library covers dwell time, fixation duration and counts, latency, AOI transitions, recurrence, scanpath similarity, and eye-movement types. It imports formats from Tobii Pro Lab, SMI BeGaze, Gazepoint, Pupil Cloud, Varjo, OGAMA, and custom CSV files, detecting file types automatically. Workspaces can be exported as JSON, figures as PNG or JPG, and segmented data, events, and metrics as CSV; ScanGraph export is also available. Metric CSVs can be exported in long or wide form for use in R, Python, SPSS, JASP, or jamovi. The maker says data is processed locally in the browser, and documentation describes an offline-capable Progressive Web App. It is listed for web browsers, Windows, macOS, Linux, Android, and iOS, and is open source under GNU GPL v3.