Skip to main content

Studio · Roadmap · 10 items

Roadmap.

What we’re actively building, what’s queued, and what we’re researching. The honest version — anything that ships moves to /changelog. Anything that gets dropped just disappears, no theatre.

Last edited by hand · paired with /pulse · /changelog

Now

3

In progress this week.

  1. Per-claim receipts on case-study metrics

    Every quantitative claim on a case-study page gets a small `?` linking to a verifiable measurement. Shipped first where real analytics history exists; other case studies stay un-annotated rather than fabricated.

    Started 6w ago

  2. Cursor-aware variable typography on the hero

    The home hero headline tracks cursor proximity through the Geist weight axis. Touch + reduced-motion users get the static weight. A craft signal — visible in two seconds, costs nothing in performance.

    Started 6w ago

  3. /errors — lessons shipped publicly

    Honest list of mistakes we shipped, what fixed them, and what we learnt. Every entry dated, with a link to the commit that fixed it. Honesty is positioning when nobody else does it.

    Started 6w ago

Next

4

Queued — starting in days, not months.

  1. Time-of-day ambient palette

    Subtle accent tinting across the site that shifts with London hour — warmer in the evening, cooler at night. Hooked into the same engine that powers the Pulse "studio open" indicator.

  2. PSI-backed performance receipts

    PageSpeed Insights run at build time for every public route, scores stored as static JSON, badges rendered on /pulse and per-page. The Lighthouse score on /pulse stops being our claim and becomes Google’s.

  3. Mobile typography pacing pass on long pages

    A second look at /now, /colophon, /uses on 360px-wide screens. Tightening clamp values, reflowing dense grids, fixing places where editorial labels eat the horizontal budget.

  4. Newsletter widget in the client dashboard

    Subscribers see studio shipping cadence inside their dashboard so the relationship doesn’t live only in their inbox. Same data the public newsletter goes from, scoped to logged-in clients.

Exploring

3

Research. No commitment yet — these get published only if they earn their place.

  1. Open-source extraction of BrowserFrame + AnimatedCounter

    Two of the components we keep reusing across client projects. Publishing them as `@gosmartr/ui` would be a marketing artefact and a forcing function for genuinely reusable design. Researching maintenance commitment.

  2. Studio soundtrack — per-project track on case studies

    Every project gets one track that played while we built it. Optional Spotify embed at the bottom of each case study, default off, screenshot-worthy when on. Personality move.

  3. Long-form essay series on /journal

    One properly-written 2,500+ word piece per month with marginalia, pull-quotes, real depth. Replaces the temptation to write five short blog posts that say nothing.

Want something on this list? Tell us about it