Can I vibecode Arcade?

KINDA · weekend project

price $50/moyou'd save $600/yrbuild time one sittingcategory 📹 screen recordingreplaced by 0 people

The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Arcade, build an interactive product story from captured screens and hotspots. The hard boundary is capture polish, hosted playback, analytics, personalization, and collaboration, plus capture polish, hosting, and collaboration.

the prompt

Build a personal replacement for Arcade in an empty repository.
Use Tauri 2, React, TypeScript, ffmpeg, and SQLite; do not offer alternative stacks.
The core loop is: capture a screen or window with microphone audio, trim the result, annotate key moments with hotspots into an interactive product story, and export a shareable local video.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Offer screen, window, or region capture plus optional microphone audio.
Show an always-visible recording timer and make stop available from the tray.
Create a non-destructive trim view with crop, zoom, cursor highlight, and text callouts.
Render locally through ffmpeg with sensible H.264 and WebM presets.
Generate a poster frame, transcript, and Markdown summary beside each video.
Provide copy-file-path and reveal-in-folder actions instead of mandatory cloud upload.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out public cloud hosting.
Deliberately leave out viewer identity and engagement analytics.
Deliberately leave out enterprise workspaces and SSO.
Finish by running the tests and listing the exact commands used.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

People still pay for Arcade because the recording itself is easy; the subscription removes upload, transcoding, sharing, organization, and support work. The recurring cost buys OS permissions, codecs, rendering performance, uploads, storage, links, and viewer analytics, not just the visible interface.

what you lose

xcapture polish, hosted playback, analytics, personalization, and collaboration

xinstant hosted sharing

xviewer analytics

xteam libraries

xcross-device capture

prior art · use these instead of building, if you'd ratherCapOpen-source screen recording and sharing product with modern desktop architecture.↗

share on X ↗"I just replaced Arcade ($50/mo) with one prompt"

the numbers

Arcade pricing

plan	monthly	annual (per mo)	what you get
free	$0/workspace	$0/workspace	1 user; 1 published interactive demo plus 1 video; unlimited views; 200 AI credits/month
growth	$50/user	$42.50/user	Up to 10 users; unlimited demos and videos; 800 AI credits/month; 1 brand kit
enterprise	custom	—	Custom users, demos, security and support; up to 10 brand kits and 100,000 AI credits/year

free tier1 user, 1 published interactive demo, 1 published video, unlimited views and 200 AI credits/month

billingmonthly + annual; paid creators are seat-based

hidden costsVideos and generated visuals consume credits, roughly 50 credits per 30 seconds of video or per generated visual, while each additional creator requires a paid seat.