EyeZen v1.2.0: Bringing Local-First Workspace Customization to the Browser

EyeZen v1.2.0 is officially available!

After building the desktop foundation of EyeZen with Rust, Tauri 2, React and TypeScript, I've reached a new milestone: a functional browser edition with local settings persistence and a dedicated documentation website.

Why a web edition?

EyeZen started as a desktop application focused on workspace personalization, comfort preferences, profiles and break routines.

However, many features—such as changing themes, creating profiles and organizing break reminders—don't require access to native operating-system APIs.

Version 1.2.0 makes these capabilities accessible directly from a browser.

What's new in v1.2.0?

1. EyeZen Web

The browser edition includes ten appearance themes, nine starter workspace profiles, customizable profiles, scheduled routines, break reminders and accessibility preferences.

Users can personalize their environment without installing the desktop application.

2. Persistent local browser settings

A major part of this release involved implementing reliable browser persistence.

EyeZen stores settings locally, validates saved data and handles malformed records rather than silently overwriting them.

Settings can also be exported and imported as JSON.

The web and desktop editions use compatible settings schemas, although synchronization is manual rather than automatic.

3. Permission-aware reminders

EyeZen supports optional in-app break reminders and notification functionality.

Browser notification permission is requested through an explicit user interaction.

Reminders depend on the active application or browser tab and remain subject to browser and operating-system restrictions.

4. A new documentation website

Version 1.2.0 also introduces comprehensive public documentation.

It covers:

• Application features and configuration
• Web versus desktop compatibility
• Installation and setup
• Privacy and local storage
• Architecture and accessibility
• Troubleshooting and frequently asked questions

5. Maintaining honest platform boundaries

The browser edition cannot tint unrelated desktop windows, enumerate physical monitors or change hardware brightness.

The installed desktop application retains optional software-based visual tint overlays on supported environments.

Neither edition claims medical benefits or hardware-level display calibration.

Communicating these differences clearly is important when building trustworthy cross-platform software.

Built with open technologies

The project uses:

• Rust and Tauri 2 for native desktop functionality
• React and TypeScript for the interface
• Vite for web builds
• GitHub Actions for automated builds and deployment
• GitHub Pages for the static browser application and documentation

EyeZen is open source under the Mozilla Public License 2.0.

Try EyeZen

Web edition: https://sanskarin.github.io/EyeZen/

Documentation: https://sanskarin.github.io/EyeZen/docs/

GitHub release: https://github.com/sanskarIN/EyeZen/releases/tag/v1.2.0

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

What's next?

EyeZen will continue evolving through better workspace customization, platform compatibility, accessibility improvements and stronger real-device testing.

If you use EyeZen or work with Rust, Tauri, TypeScript or cross-platform applications, I'd welcome your feedback and contributions.

What would you prioritize next for EyeZen?