EyeZen v1.1.1: Bringing Screen Comfort to Multiple Monitors

EyeZen v1.1.1 is now available on GitHub.

This release focuses on an important improvement to the desktop experience: making warmth and intensity preferences produce actual visual changes across supported desktop environments.

The problem with v1.1.0

Earlier EyeZen versions provided controls for adjusting screen comfort preferences.

Users could change warmth and intensity values, save their preferences, and switch between workspace profiles.

However, those settings didn't actually change the desktop display.

The application remembered the configuration, but a key part of the expected experience was missing.

What changed in v1.1.1?

The latest release introduces a software-based, multi-monitor tinting implementation.

On supported desktop sessions, EyeZen can create transparent, click-through windows that visually modify the appearance of detected monitors.

The implementation introduces several improvements:

1. Multi-monitor tint overlays

EyeZen enumerates monitors reported by the operating system and creates an overlay for each detected display.

These overlays are designed to allow normal mouse interactions with the applications underneath them.

2. Adjustable warmth and intensity

Users can modify two important properties:

• Warmth: Controls the amber tint applied to the screen.
• Intensity: Controls the strength of the tint and a modest darkening effect.

The result is a configurable software overlay rather than a hardware-level display adjustment.

3. Dynamic display handling

While Screen Comfort is enabled, EyeZen rechecks monitor configuration approximately every 20 seconds.

This helps it respond to changes in monitor count, geometry, and positioning.

4. Profile synchronization

Applying workspace profiles or restoring settings after restarting the application updates the desired overlay configuration.

5. Better control and safety

The release introduces an emergency system-tray action for disabling screen comfort.

Selecting Color-accurate work also removes EyeZen's overlays, allowing users to work without the application's software tint.

Technical implementation

EyeZen uses:

• Rust for native desktop functionality.
• Tauri 2 for the desktop application architecture.
• React and TypeScript for the user interface.
• Native desktop windows for applying visual tint overlays.

The implementation avoids changing physical monitor brightness, gamma ramps, ICC profiles, or operating-system night-mode settings.

This distinction matters because drawing a transparent overlay and changing a monitor's physical output are fundamentally different operations.

Platform support

The implementation currently targets Windows 10/11 and macOS desktop sessions, although additional real-device testing is required.

Linux X11 support is experimental and depends on compositor capabilities.

Linux Wayland is not supported for this overlay functionality.

Some exclusive-fullscreen applications and protected desktop contexts may appear above the overlays.

Testing and future improvements

Automated checks cover application code, tests, linting, and installer builds.

However, passing automated checks does not prove that an overlay works correctly across every monitor configuration or desktop environment.

Additional testing is needed for mixed-DPI monitors, display hot-plugging, system suspend/resume, and other real-world conditions.

I welcome bug reports, contributions, and feedback from users testing different desktop setups.

Download EyeZen v1.1.1

GitHub Release:
https://github.com/sanskarIN/EyeZen/releases/tag/v1.1.1

Source Code:
https://github.com/sanskarIN/EyeZen

EyeZen is open source under the Mozilla Public License 2.0.

The goal is to build a transparent, privacy-focused desktop customization application where features do what they claim, and platform limitations are communicated clearly.

If you're interested in Rust, Tauri, cross-platform desktop applications, or local-first software, I'd love to hear your thoughts.

What has been your biggest challenge when developing or using multi-monitor desktop tools?