Roadmap

What we are planning, what we are building and what is coming next. No fixed dates — software is unpredictable and we prefer honest over optimistic.

This roadmap reflects our honest current plans. Timelines are intentionally vague because we prioritize quality over speed. Features may change, be delayed or be dropped entirely if we discover a better approach. See our Changelog for what has actually shipped.

Currently Building

The following features are actively in development:

Modern CSS Color Function Support

In Progress

Support for OKLCH, OKLab, LCH, and the CSS color() function across our converter and picker tools. Modern browsers now support these — we are catching up.

Expanded Accessibility Testing

In Progress

Adding APCA (Advanced Perceptual Contrast Algorithm) alongside WCAG 2.2, so designers can preview both standards and see where they diverge.

Next Up

Features planned for the next development cycle:

Palette Sharing via URL

Save a palette, get a shareable URL that recreates it in the tool. Client-side only, no accounts required.

WCAG 3.0 Preview

Early preview of WCAG 3.0 contrast model alongside our existing WCAG 2.2 checker.

Enhanced Image Color Extraction

Better dominant color algorithm using k-means clustering for more accurate extraction from photographic images.

Color Contrast for Charts

A dedicated tool for checking whether series colors in charts are distinguishable, accounting for CVD and color blindness.

Under Consideration

Features we are evaluating but have not committed to:

Figma Plugin

An official Figma plugin that connects OmniColor's palette and accessibility tools directly into the Figma workflow. Would require significant additional work.

Browser Extension

A lightweight browser extension for quick color picking on any page. For now, our bookmarklets serve this purpose.

Dark Mode

A native dark mode for the OmniColor site itself. We have designed the color system to support this, but implementing it well takes time.

Multi-language Support

Translating the site's UI and content into Spanish, French, German and Japanese. Requires significant content translation work.

Not Planned

Things we are actively not planning, for transparency:

  • User accounts: Would require backend infrastructure and go against our static-site philosophy
  • Paid tiers: The site is and always will be free
  • Mobile apps: The PWA works well enough — native apps would require significant additional investment
  • AI-generated color suggestions using paid APIs: Would introduce costs and privacy concerns
  • Social features: Comments, profiles, followers — not what OmniColor is for
  • Analytics-driven personalization: We do not track users enough to personalize

How We Prioritize

When deciding what to build next, we weigh:

  1. User demand: How many people are asking for this?
  2. Mission alignment: Does it help people work with color more effectively?
  3. Effort vs impact: Does the work justify the improvement?
  4. Maintenance cost: Can we support it long-term?
  5. Accessibility: Does it meet our WCAG 2.2 AA standards?
  6. Performance: Does it slow the site down?

We reject many feature requests that do not fit our philosophy — this is why the site stays focused and fast.

How to Influence the Roadmap

The best way to get a feature prioritized is to request it clearly:

  • Submit a feature request with a genuine use case
  • Tell us how it would help your actual work
  • If you can, describe a specific workflow it would improve

Feature requests with real-world use cases get prioritized far above generic suggestions. Requests that come from real workflows (not just "would be cool if...") get built.

See What Has Shipped

Our changelog documents every new tool and feature released.

View Changelog