mobile
Reaction Picker
Holding a message opens a row of tapback reactions; a corner button opens the same row for keyboard and pointer use.
- mobile
- reactions
- long-press
- messaging
- tapback
Related pattern
The corner button is the only path for keyboard and screen-reader users, since a hold gesture has none.
Live preview
Hold this message to react.
Quick usage
usage
import { ReactionPicker } from "@pinky-ui/systems";
<ReactionPicker options={reactions} value={reaction} onValueChange={setReaction}><MessageBubble>{message.text}</MessageBubble></ReactionPicker>Install
Add @pinky-ui/systems as a dependency, or use the CLI to copy this component's source directly into your project — no dependency to manage, fully editable.
shell
npm install @pinky-ui/systemsshell
pnpm add @pinky-ui/systemsshell
yarn add @pinky-ui/systemsshell — copies source into your project
npx pinky-ui add reaction-pickerPrefer to run the whole repository locally instead?
repository
git clone https://github.com/florash/Pinky-UI.git
cd Pinky-UI
npm install
npm run devAccessibility
- Every gesture has a labelled button or keyboard path, and primary controls meet a 44px touch target.
- State remains readable without relying on colour or motion.
Performance
- Interaction state is local and bounded; gesture updates do not require a page-wide render loop.
- Timers and listeners are cleaned up on unmount.
Reduced motion
The same state change resolves immediately; travel, scale and spring motion are removed without removing the interaction.
When to use
- Touch-first product surfaces where the next action should stay close to the hand.
When not to use
- Desktop-only workflows or interactions whose gesture would hide the only available action.