Scheduling and meetings decision
Add More Colors to Calendar
A single developer can build a local-only Chrome extension that provides automatic rule-based coloring and manual overrides in about a week, but reproducing the product's account sync and paid-subscription features requires servers and billing which raise scope and ops beyond the smallest useful replacement.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off24 h to build
$0/mo1 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Detect calendar events in the page DOM and render full-color bars; provide a popup/options UI to create/edit coloring rules and manual per-event colors; match events to rules (title/keywords) and apply colors; store rules and saved colors locally (chrome.storage) and compute readable text contrast.
What it still won’t have
- Cross-device sync tied to a user account (server-backed sync)
- Hosted account management and Stripe subscription flow
- Server-side backups or analytics
- Customer support workflow and in-app feature suggestion handling
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Add More Colors to Calendar does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a Chrome extension using Manifest V3, TypeScript, and React for the popup UI plus a content script (plain JS/TS) that modifies Google Calendar DOM. In scope: content script that detects calendar events and injects full-height color bars; popup/options UI to create/edit automatic rules (title contains / regex), manual per-event overrides, and saved colors; persist rules and saved colors in chrome.storage.local; implement automatic black/white text contrast; per-event UI affordances (hover color button) to set manual color. Out of scope: server-side account sync, Stripe billing, analytics, and cross-device sync. Include error handling, unit tests for the rules engine, end-to-end smoke test of content script applying colors, and a build step to produce a signed extension bundle for Chrome Web Store.
How we checked
How the score was reached
- Partly verdict base52
- 4 cited sources+3
- Evidence score55
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productAdd More Colors to Calendar - Chrome Web Store
- official productAdd More Colors to Calendar - Chrome Web Store
- official productAdd More Colors to Calendar - Chrome Web Store
- official productAdd More Colors to Calendar - Chrome Web Store
Integrity checks
What held up, and what did not.
