This is the plan Zarek built for ShotGlass — 58 steps, every piece of copy written, generated from one URL.
Do this for my productShotGlass
Copy — the post text Zarek writes for each channel, ready to copy and paste.
Channel-by-channel launch copy, drafted to each platform's voice and limits. Zarek writes each channel on demand — so your launch builds instantly and copy fills in automatically.
draft · target 2026-09-08
Show HN: ShotGlass - Mac screen recorder with auto-zoom and cursor smoothing Hi HN, I'm Jake, the creator of ShotGlass (https://shotglass.app/). Most product demos require jumping between a screen recorder and an editor just to add zoom cuts, smooth out jittery mouse movements, and hide desktop mess. I built ShotGlass to handle those post-production steps automatically right after recording. How it works technically: Instead of capturing a flat video stream with the cursor baked into the pixels, ShotGlass records window coordinates, display metadata, and cursor events as separate data streams alongside the video feed. By decoupling these layers: 1. Cursor paths are rebuilt post-capture using bezier curves to remove erratic twitching while keeping precise click timing. 2. Window bounds are tracked across multiple displays via macOS APIs, allowing the renderer to calculate zoom targets and 3D perspective transforms without manual keyframing. 3. Background padding and desktop replacement happen on a separate compositing pass, so desktop clutter never touches the final output. Current limitations: - macOS only. It relies heavily on ScreenCaptureKit and macOS window server APIs, so a cross-platform version is not currently viable. - Performance on older Intel Macs: rendering multi-window 3D perspective transforms on dual 4K/5K setups can spike GPU usage. It runs far better on Apple Silicon. - Non-standard UI toolkits: custom canvas-based apps (like some Electron apps with non-standard window frames or custom OpenGL views) can occasionally confuse the automatic window boundary detection. I'd appreciate feedback on: - The auto-zoom heuristics. Does it track your focus points naturally, or does it zoom too aggressively on small UI changes? - Multi-monitor workflows: edge cases where window switching across displays feels jarring. - Export defaults: what codecs and container presets you actually need for documentation vs. web embeds. You can check it out at https://shotglass.app/. I'll be around in the comments to answer questions about the capture pipeline.
No image assets yet — capture a screenshot or generate an OG image on the Assets page.