What Shipped Since April
Overview
The April roadmap laid out a plan. This is the honest version of what came out of it between then and now — four things that are finished and in your hands, and a short list of things that are not. The full, versioned record lives in the changelog; this post is the summary with the reasoning attached.
One extension instead of four
+We were shipping four browser extensions — color, accessibility, devtools, and a suite that contained all of them. An audit turned up the uncomfortable truth: they were the same binary four times over, with the build stripping tab buttons off the ends. Four store listings, four review queues, one product.
So they are now one product. Capabilities load lazily rather than being compiled out, which is what made the merge possible without a heavier download. Along the way the extension got a Side Panel surface, a sidebar that survives narrow widths, universal pickers that upgrade native form controls on any page, a custom right-click menu built inside a shadow root so host-page CSS can't break it, and a search box over the settings.
The accessibility rule set inside the extension went from 20 checks to 97 in the process, and the suite's test count went from 55 to 72.
The Analyzer learned accessibility properly
+The Analyzer's A11y+ tab used to be a thin contrast checker. It has been rebuilt on a 112-rule engine covering ARIA 1.2, accessible-name computation, and APCA contrast, and it now reports what it found rather than just a score: an accessibility tree, a screen-reader transcript of the page, color-vision simulation, and a VPAT export.
The constraint that shaped the work was the performance budget. The Analyzer route has very little headroom left, so all 112 rules and their stylesheet load on demand — open the tab and they arrive; ignore the tab and you never pay for them.
Payments that actually charge the right amount
+One-time checkout through Razorpay is live, with server-side signature verification and webhook fulfilment, backed by a test suite and a real end-to-end purchase.
The part worth writing down is a bug we found in our own design. The browser used to send both the amount and the thing it wanted to buy, and the server charged what it was told — so a one-rupee order could claim the most expensive plan. Price and entitlement now come from the same authority: an order that claims a plan is priced from the catalogue on the server, and the claim is rewritten to its canonical name so fulfilment can only grant exactly what was charged for.
Analytics landed alongside it: first-party, consent-gated, no third-party trackers.
VS Code, and the rest of the plugin line
+The VS Code extension reached 0.13.2 — color and accessibility intelligence in the editor, including a project-wide scan and a Studio view, sharing the same color core as the website rather than a reimplementation of it.
It joins the plugins for Figma, Sketch, Penpot, Raycast, and Alfred. All of them are free, like the tools they wrap.
What isn't done
+Since the roadmap promised more than this, here is the other half of the ledger — the things that are still unbuilt, so you don't have to guess from the marketing copy:
- Token top-ups aren't on sale. Tokens come with a plan; you can't buy them separately yet.
- Accounts are single-user. Team seats, shared workspaces, and role-based permissions are designed but not built.
- Cloud sync is partial. Account settings sync; saved palettes and projects still live in your browser.
- No SSO, no white-label embedding, no contractual uptime SLA. These are on the list, not in the product.
The pricing page now says the same thing in the same words. If any of these matter to you, tell me — that's what moves them up the list.