Feature Requests

Have an idea for a new tool or improvement? We would love to hear it. Every request is read and prioritized based on user feedback and feasibility.

How We Handle Feature Requests

  1. Acknowledge: We confirm receipt within 3 business days.
  2. Evaluate: We assess alignment with our mission, feasibility, and user demand.
  3. Prioritize: Requests with high user demand and low complexity get built first.
  4. Implement: If we build it, we announce it in our changelog.
  5. Decline: If we cannot build it, we explain why in our reply.

Real use cases help us prioritize features that solve genuine problems.

Provide your email only if you want us to notify you when the feature is implemented.

This form uses mailto handoff. If your email client does not open, please email feedback@omnicolor.pages.dev.

What We Prioritize

Feature requests are evaluated on:

  • User demand: How many users have requested similar features?
  • Mission alignment: Does it help people work with color more effectively?
  • Feasibility: Can it be built without a backend server?
  • Performance: Will it slow down the site?
  • Accessibility: Can it meet our WCAG 2.2 AA standards?
  • Maintenance: Can we support it long-term?

We prioritize small, well-scoped requests that solve real problems over large, speculative features.

What We Probably Won't Build

To set expectations, we are unlikely to build:

  • Anything requiring a backend server, database or user accounts
  • Features that require paid API subscriptions
  • Features that violate our privacy principles
  • Social features or user-generated content
  • Cryptocurrency, finance or trading tools
  • AI-generated color descriptions using paid AI APIs
  • Tools that duplicate other categories that already exist elsewhere