Demo wall

17 things to poke at. Pick one, play with it, then try to break it.

  • What 60 fps costs

    Part 2 of 3D on the web. Four knobs on one scene, a frame budget, and a live reading of what each knob costs on your device.

  • The hero that does not block your LCP

    Part 1 of 3D on the web. A 3D hero looks great and loads late. Show the picture first, bring the scene in on idle, and measure what it costs.

  • 100 milliseconds

    A blind test. One of two buttons answers late. Find out how small a delay you can still feel, then see why that number matters.

  • Where does Tab go?

    Two shop screens that look the same. Press Tab and the focus takes completely different routes. The path is drawn on top.

  • Translate it until it breaks

    The same small panel, built twice. Switch to German, Arabic or 200 % text and count what breaks.

  • Glass you can still read

    Frosted glass looks great on a mockup and fails on a busy background. Drag a panel over a loud backdrop and watch the contrast being measured from real pixels.

  • The card that becomes the page

    A list card opens a detail page. Cut or morph? The same flow built twice, with the View Transitions API and a fallback that costs nothing.

  • Scroll animations that survive a frozen page

    The same scroll effect, once with a scroll listener and once with CSS scroll-driven animations. Freeze the page and compare what keeps moving.

  • Layout shift ate my click

    A promo loads late and the button you were aiming at moves. Watch a tap land on the wrong thing, then fix it with one reserved box.

  • The resilient input

    Strict fields reject what people really type. Pick an amount, a phone number, an email or a name and watch two fields read the same text.

  • Design tokens that survive a rebrand

    A token system is only as good as its middle layer. Skip it and the first rebrand works, the first dark mode breaks, and nobody can say why.

  • Beyond boolean hell: why isLoading && !hasError fails

    Nested booleans create impossible states nobody designed for. A small state machine keeps the interface out of them.

  • Focus is part of the design

    A dialog that works with a mouse is half a dialog. Where keyboard focus goes when it opens, while it is open and when it closes decides whether anyone else can use it.

  • Fast is a feeling: perceived speed beats measured speed

    People judge speed by when the interface answers, not when the server finishes. Optimistic updates move the answer to zero, and send you the bill as a rollback you have to design.

  • Springs keep their momentum, Bézier curves don't

    A cubic-bezier is a fixed path through time. A spring is a rule. Only the rule survives being interrupted.

  • Design the product card for the data you will actually get

    A card that works with the demo product breaks on the first real catalogue. Four toggles show where, and what a resilient card does instead.

  • Micro-feedback and perceived speed

    One button, three states and a spring. Change the network latency and the stiffness and feel why a button that answers at once feels faster than one that is.