Sticky Video Player
A playing video shrinks into a corner when scrolled past and keeps playing.
What it adds
A miniature docked player that takes over when the inline video scrolls out of view, with a close control.
What your agent is told to do
5
What your agent is told to do
5-
1
Dock only when the video is actually playing and the original position has left the viewport, and undock automatically when the user scrolls back to it.
-
2
Move the same player element rather than creating a second one. Two players means two audio streams the moment the timing is slightly off.
-
3
Give the docked tile a visible close control and a way to jump back to the video in the page. Closing it must pause playback, not merely hide a video that keeps talking.
-
4
Position the tile using the same layer and offset tokens as the app's other fixed elements, so it sits above the page but below anything modal.
-
5
Do not dock on a paused video, on a muted background loop, or on a video the user has never interacted with. An element that follows people down the page uninvited is the behaviour ad blockers exist to remove.
Edge cases it handles
8
Edge cases it handles
8- Detach only after playback has genuinely started. Docking a paused or never-played video puts a small black rectangle in the corner of the page for no reason.
- Once the viewer closes the docked tile, remember that for the rest of the page visit. A player that re-docks on the next scroll is worse than one that never docked at all.
- The corner is crowded. Check what else occupies it — sticky footers, chat launchers, cookie banners, toasts — and offset the tile or pick a different corner rather than covering a control the user needs.
- Moving a video element in the DOM can reset it in some browsers. Capture the current time, playback rate, volume, and muted state before the move and restore them after, and verify the video does not restart from zero.
- On a narrow screen a corner tile eats a serious share of the viewport. Either disable docking below a breakpoint or reduce it to an audio-style bar rather than shrinking a video until it is unwatchable.
- Fullscreen and picture-in-picture must take precedence. Do not dock a video that the browser has already handed to another presentation mode.
- The transition must respect reduced motion. Reuse the app's Reduced Motion Support so the tile appears without a flying animation when that preference is set.
- The docked tile must be reachable by keyboard and its controls focusable, and it must not steal focus from wherever the user was reading.
Definition of done
9
Definition of done
9- A video docks only after playback has started and its inline position has scrolled out of view.
- Scrolling back to the video returns it inline with playback uninterrupted.
- Playback position, volume, and muted state survive the move in both directions.
- Closing the tile pauses the video and suppresses docking for the rest of the visit.
- The tile never covers sticky bars, chat launchers, cookie banners, or toasts.
- Docking is disabled or reduced on small viewports.
- Fullscreen and picture-in-picture sessions are left alone.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Picture-in-Picture Mode
Picture-in-Picture Mode
Let viewers pop a video into a floating window and keep using the rest of the app.
What it does
A control on the video player that hands the video to the browser's floating always-on-top window.
How it works
- 1 Add the control to the app's existing video player rather than building a separate popped-out player. Two players competing over the same element is the main way this feature goes wrong.
- 2 Keep the app in sync with the floating window in both directions. Pausing, seeking, or changing volume from the floating window must update the in-page player, and closing the floating window must return playback to the page at the same position.
- 3 Decide explicitly what happens when the user navigates away from the page that owns the video. Either keep the floating window alive and reconnect when they return, or end it cleanly, but do not leave a floating window playing a video the app has forgotten about.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/picture-in-picture-mode
Audio Waveform Scrubber
Audio Waveform Scrubber
Show the shape of a track so listeners can see the quiet and loud parts and click to them.
What it does
A waveform rendered from precomputed amplitude data, doubling as the seek control on the audio player.
How it works
- 1 Compute the amplitude data on the server when the file is first stored, and serve it as a small dataset the page can draw. Do not decode the audio in the browser to build the waveform.
- 2 Replace the plain scrub bar in the app's existing Audio Player with this surface rather than adding a second seek control beside it.
- 3 Draw played and unplayed regions distinctly, and keep the playhead position exact under click, drag, and keyboard seeking on the same surface.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/audio-waveform-scrubber
Hover Video Preview
Hover Video Preview
Hovering a video card plays a short silent clip so people see what it is before clicking.
What it does
A silent, short-loop preview that plays inside a video card on deliberate hover and returns to the poster on exit.
How it works
- 1 Generate a short, low-resolution, silent preview clip during video processing and store it alongside the poster frame. Do not play the full source file behind the card.
- 2 Require a deliberate hover before doing anything. Wait several hundred milliseconds after the pointer settles, then load, so a cursor crossing a grid does not fire a dozen requests.
- 3 Give touch devices an explicit preview control on the card, since hover does not exist there. A long-press or a small preview button is fine; silently doing nothing on mobile is not.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/hover-video-preview
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.