useBudOff
A drop of the primary plastic buds out of one element, flies to another and is swallowed by it, which swells as it lands — so the eye follows cause to effect. Its front leads and its tail lags, so it draws out on its own. Returns a function, budOff(from, to, options): from is the element the drop buds out of, to the one it lands in, and the options are below. budOff returns a function that calls the drop off before it lands: it's gone and onArrive never runs, for when what it was flying to is reset first.
Feel Something leaves the thing you pressed and lands where it counts.
Preview
Or let the agent fetch it: get_component("bud-off") on the Echo MCP server.
Installation
First time? Run npx echo-ui-cli init once — it sets the project up, and add refuses to run before it.
At a glance
- Version
- 0.3.0
- Weight
- 1.1 KB · 28.5 KB with what it imports · 278 B of CSS (minified and gzipped; React not counted)
- Reduced motion
- No drop: onArrive runs at once.
- Sound
- A soft gulp as it lands, inside a SoundProvider.
Usage
import { useBudOff } from "@/echo/bud-off";
const budOff = useBudOff();
const send = (e: React.MouseEvent<HTMLButtonElement>) =>
budOff(e.currentTarget, outbox.current!, { onArrive: () => setSent((n: number) => n + 1) });Composition
useBudOff → a drawn drop over the page, removed when it lands
Examples
Into a count
Show the new number when the drop gets there.
const budOff = useBudOff();
budOff(button, badge, { onArrive: () => setShown((n: number) => n + 1) });Call it off
Reset before the drop lands, and it never arrives.
const cancel = budOff(button, badge, { onArrive: () => setShown((n: number) => n + 1) });
// …the count is reset while it flies:
cancel();Accessibility
- The drop is decoration (aria-hidden): whatever it means has to be said by what it lands in.
- It never takes focus and never blocks the pointer.
Tested against WCAG 2.2 AA on every release:
axe— No axe violations, in the component's own gallery and on its page.keyboard— Every action is reachable and operable from the keyboard alone.focus-visible— Focus is visible on every focusable part, in normal and forced-colors mode.forced-colors— State stays visible when the look's colours are replaced by the system's.target-size— Every target's real hit area is at least 24×24px, at every density.reflow— Content reflows into 320px and survives a doubled text size.
Not covered: screen-reader: not yet verified by a person. Everything above is a machine check; a person has not yet driven this component with a screen reader.
Motion & sound
- Motion tokens
springs- Reduced motion
- No drop: onArrive runs at once.
- Sound
- A soft gulp as it lands, inside a SoundProvider.
Props
| Prop | Type | Default |
|---|---|---|
onArriveWhen the drop lands: update what it landed in here. | function | |
sizeThe drop's radius, px. Defaults to 10. | number |
Anti-patterns
- Never make the drop the only sign something happened: update what it lands in.
- Never fire it on something the user didn't do: cause and effect is the point.
Changelog
- Every item needs
echo-ui-core0.3.0 (all components). The drawn device, readability past AA and the design tests live in core, and the components that use them are built against it, so each item now declaresecho-ui-core >=0.3.0 <0.4.0. Update core with the items:npm install echo-ui-core@^0.3.0(or your package manager's), thennpx echo-ui-cli update. An item whose files didn't change is the same code under a new version; the 0.2.0 files stay published. - Six more that change shape as you use them, all on
Morph.SaveButtonnarrows into its own progress while your save runs, widens into a lit "Saved" and flows back.Timeropens into durations; the others run into the one you pick, which drains as the time runs and rings.Stopwatchbuds a Lap button from Start, and every lap is a drop that lands in the lap count.VoiceNoterecords from the microphone: your voice swells the Stop button, and the take becomes a note that fills as it plays.AddToBagsends a drop from the button into the count beside it.useBudOffis that drop on its own, from any element into any other.Morphnow keeps a button's identity across states when it has the samedata-morphname, and draws filled caps as levels. - Comments only, no behaviour change. Comments in the component source used to cite documents, milestones and ticket numbers from Echo's own planning, none of which exist in your project. The citations are gone and the sentences around them stay. Where a comment was only a citation, it now says what it meant. Three development warnings (
HardwareButton'sengraved/captionchecks andStatusDot's missing-label check) also dropped the ticket code at the end of the message.echo-ui diffwill show changes in most items; none of them are to code. - An item's version is now a function of declared data, not of how the changelog is formatted. The version an item ships under is published once and never rewritten, and it used to be inferred from prose: a regex for a bolded "Breaking" run across the whole unreleased section, and attribution by "does a bullet mention this name in backticks". One breaking entry therefore moved every item that changed that cycle, and an entry explaining that "
MenuandSheetare unchanged here" filed itself as a change to Menu and Sheet — which it really had. - The agent brief says Echo has not shipped.
llms.txtand the MCP server's instructions led withnpx echo-ui-cli init, and that name on npm is a reserved stub with no executable — so a model following the brief wrote an install step that fails with npx's own error. The brief now opens with the caveat, and the docs carry it on every surface that shows a command. One switch (CLI_RELEASED) silences all of them at launch, and a test refuses to let one move without the others. Affectsall componentsonly in what the brief says about installing them; no item's props, CSS or rendered semantics change. - Echo's home is
echo-ui.com. The registry, the docs and the packages all move to it fromecho.nawwara.studio. Nothing was published under the old host, so noecho.jsonanywhere points at it and there is nothing to migrate — this is the last release where that is true. - Weights, line heights, letter-spacing, z-index, border widths and icon sizes come from the theme scales in
all components, with the old value as a fallback, so components keep working withecho-ui-core@0.0.1. Strays moved to the nearest step: most by under a pixel; HardwareButton icons are 14/16/20px (were 15/17/19). Stopwatch: a lap still in flight when you Reset no longer comes back (BUG-74). Its drop landed after the reset and put the old count back, so the next first lap briefly read "2 laps". To do it,budOff(…)fromuseBudOffnow returns a function that calls the drop off before it lands; ignoring it changes nothing.- Content now reflows into a 320px screen (400% zoom) and survives a doubled browser text size (WCAG 1.4.10, 1.4.4), across
all components.Select's 180px floor,NumberField's readout,SegmentedandStepsas flex items,EmptyState's grid columns, andAvatar's fixed-pixel disc all gave way;Panelcounts its padding inside a width you set (box-sizing: border-box), so a<Panel style={{ width: 220 }}>is now 220px wide overall rather than 260px.