Skip to content
Pinky UI

mobile

Story Progress

Segmented auto-advancing progress across a media sequence — hold to pause, tap either half to step, the Stories reading pattern.

  • mobile
  • stories
  • progress
  • auto-advance
  • media
Related pattern

The hold-to-pause gesture has no keyboard equivalent, so the tap zones are real labelled buttons rather than a bare pointer surface.

Live preview

Hold to pause · tap a side to step

Segment 1 of 3

Quick usage

usage
import { StoryProgress } from "@pinky-ui/systems";

<StoryProgress count={items.length} duration={4000} onComplete={close}>{media}</StoryProgress>

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/systems

Prefer to run the whole repository locally instead?

repository
git clone https://github.com/florash/Pinky-UI.git
cd Pinky-UI
npm install
npm run dev

Accessibility

  • 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.