SMF·ARCADE
Can a prompt replace Arcade?
Screen recording — screen recording, walkthroughs and product demos
Exhibit tracking slip
Verdict
Capturing a browser flow as a series of screenshots with clickable hotspots — so a viewer clicks through an interactive replay instead of watching a passive video — is a real weekend build, reusing this catalogue's Scribe capture approach as a starting point. What doesn't survive: Arcade's polish in hotspot auto-detection accuracy and its analytics on how viewers actually click through a shared demo.
Exhibit A — The prompt
Received on31.07.2026Build an interactive-demo capture tool, extending this catalogue's Scribe capture approach with clickable replay instead of a static guide. Use a Chrome extension (Manifest V3) that, while recording, captures a full-page screenshot at each click along with the clicked element's on-page coordinates and size, building a sequence of screenshot-plus-hotspot pairs. On export, generate a self-contained HTML page that replays the sequence: show the first screenshot with a pulsing hotspot over the recorded click location, and advance to the next screenshot only when the viewer clicks that hotspot — an interactive walkthrough, not a passive video. Support adding a short text caption to each step, editable after capture. Export as a single HTML file with embedded images, portable, no server required to view it, or optionally host it yourself for a shareable link. Do not build automatic hotspot-accuracy tuning beyond straightforward coordinate capture, viewer analytics, or team-shared libraries — those are out of scope; this produces one interactive demo per capture, viewable standalone. No API key or account needed.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 polished automatic hotspot detection accuracy
- B.2 viewer click-through analytics
- B.3 team-shared demo libraries
- B.4 custom branding on shared demos
Prior art
Exhibit C — Why people still pay: capture polish, hosting, and collaboration
Capturing screenshots with click coordinates is simple; making the hotspot detection reliably accurate across any website's UI, and giving teams analytics on how prospects actually click through a shared demo, is the ongoing product work.
Questions
How is this different from a screen-recording video?
The viewer clicks through it themselves, step by step, rather than watching a passive video — each step shows a hotspot where the original click happened, and advances when the viewer clicks it too.
Does it show me analytics on how people click through my demo?
No — that's out of scope. You get the interactive demo itself, but not data on how viewers actually interact with it.
Can I share it without hosting anything?
Yes — it exports as a single self-contained HTML file with embedded images, viewable by opening the file directly, no server required.
What does it cost to run?
Nothing — it's a browser extension with local export, so there's no hosting cost unless you choose to host the exported file yourself for a shareable link.
Related tools
Receipt