--- title: "Viewer-Controlled Tutorial Zoom" date: "2026-09-14" canonical: "https://raytally.com/en/ideas/2026-09-14-screencursor/" generator: "RayTally · dev-prompt-v4" signal: query: "ScreenCursor" observed_at: "2026-09-14T00:33:17.454Z" sources: - url: "https://www.producthunt.com/products/screencursor" boundary: "Observed at 2026-09-14T00:33:17.454Z." - url: "https://chromewebstore.google.com/detail/screencursor-screen-recor/lkaencjejddgaildkdadahbdoecbcbeo" boundary: "No publication timestamp is present in the source record." - url: "https://developer.apple.com/documentation/screencapturekit" boundary: "No publication timestamp is present in the source record." - url: "https://developer.apple.com/documentation/coregraphics/cgevent/tapcreate%28tap%3Aplace%3Aoptions%3Aeventsofinterest%3Acallback%3Auserinfo%3A%29" boundary: "No publication timestamp is present in the source record." notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief." --- [Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-09-14-screencursor/) Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting. You are a senior product engineer. Turn the product idea below into a locally runnable MVP. ## Idea Viewer-Controlled Tutorial Zoom Tutorial creators publish a recording viewers can replay from either a cursor-focused view or the full interface, so they can inspect the part of the screen that matters to them. ## Product concept When recording a complex software interface, tutorial creators often have to choose between the full screen and the area around the cursor. Zoom in, and viewers lose the sidebar; keep the whole screen, and the buttons become too small. Instead of baking zoom shots into the video, the recorder saves the full-resolution screen, cursor path, and timestamp of every click. After publishing, the player follows the presenter’s actions by default, but viewers can switch back to the full interface at any time, pause and pan around the screen, or jump to a step through action markers on the timeline. Someone inspecting a parameter panel can zoom into the left side, while someone checking the final result can pull back—without waiting for the creator to edit another version. After recording, creators can label a few key actions and add a one-sentence note to each. When a viewer opens a marker, the player stops on the corresponding frame while retaining a few seconds of surrounding context, making it easier to see what happened before and after the action. The initial feature set is for desktop software tutorials and product demos: single-screen recording, mouse paths, and a draggable viewport. Complex multi-camera editing, automatic voiceovers, and deciding which shots matter for creators can wait until users genuinely need them. ## Why now (backed by facts) In the September 14 snapshot, ScreenCursor ranked sixth in Product Hunt’s new-product feed and promoted automatic zooming around actions. That makes a specific trade-off more visible for desktop tutorial creators: when the shot follows a button, viewers may no longer see the full interface. ## Direction (model inference, not independently verified) Target user: Independent creators making tutorials for design software, developer tools, or back-office systems. While explaining a specific action, they often zoom into a button that is too small, only to cut off the sidebar or results area. When viewers revisit a step, the area they need to inspect may not be the shot the creator chose at the time. This mismatch is more worth solving for tutorials that people follow repeatedly than for one-off product promos. Minimal entry point: Start with single-screen macOS recording for desktop software tutorials. Use ScreenCaptureKit to capture the screen, and system event monitoring to record mouse positions and clicks on the same time base as the video. At publishing, retain the full recording and an interaction-data file rather than generating a fixed zoomed version. The player defaults to a cursor-centered view and offers full-screen switching, panning while paused, and action-marker jumps. Creators add only titles and brief notes for key actions; do not attempt automatic step detection. Test short tutorials first for audio-video synchronization, click alignment, and text clarity after zooming, then decide whether to expand to other operating systems. The strongest case against: Once a full-resolution recording is published, viewers may also zoom into notifications, customer information, or material hidden in a sidebar. Creators must review every section before publishing, and the redaction work may offset the editing time saved. System-level mouse monitoring also has to contend with permissions, differing display scaling, and dropped events; if click markers drift from the video, viewers will jump to the wrong step. Keeping the full image does not guarantee local clarity: text may still be unreadable when compressed source footage is enlarged. Finally, a dedicated player adds hosting and distribution overhead. If creators reach viewers mainly through conventional video platforms, this interaction may be difficult to fit into their existing workflow. These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty. ## Punching above weight (model inference) Recruit the first creators from people already publishing desktop software tutorials. They have finished videos and can most readily identify moments where the sidebar and buttons cannot both be shown well. Invite them to make an interactive version from the same sequence and place a replay link beneath the original tutorial. In demos, let viewers switch directly between global and local views to test whether that control actually helps them understand the steps. Continue investing in acquisition only if creators can demonstrate the value themselves. ## Competitors & gaps (model inference) - ScreenCursor: ScreenCursor already automatically arranges zoom shots around clicks, drags, and keystrokes. After recording, creators can adjust each shot’s position, depth, and timing, then export a video. It already removes much of the manual work of editing camera moves, so it should not be characterized as merely following the cursor mechanically. It can also record windows outside the browser, though its product description notes that cursor positioning there is less accurate than in browser content. The more important distinction comes after delivery: ScreenCursor neither hosts recordings nor provides share links; viewers receive an exported file. Creators can revise the shot before export, but viewers cannot return to the full interface during playback or inspect a cropped-out sidebar themselves. The opportunity is to deliver the full recording and interaction coordinates to a player, rather than build another automatic zoom effect. The trade-off is equally clear: creators must adopt a new publishing workflow, and viewers must use a dedicated player; an ordinary video file cannot preserve this choice. ## How it makes money (model inference) Charge a subscription per creator seat, including video publishing and player hosting. Viewers can replay for free; do not charge at the point of viewing. ## Source context Theme: ScreenCursor Trigger Product Hunt launch: ScreenCursor — Screen recorder with auto zoom effects This records only that the launch appeared in Product Hunt's public feed and when it was observed. The feed provides no vote count; do not describe feed order as popularity or market demand. ## Sources - ScreenCursor: Screen recorder with auto zoom effects (https://www.producthunt.com/products/screencursor) - ScreenCursor - Screen Recorder with Auto Zoom Effects (https://chromewebstore.google.com/detail/screencursor-screen-recor/lkaencjejddgaildkdadahbdoecbcbeo) - ScreenCaptureKit (https://developer.apple.com/documentation/screencapturekit) - CGEventTapCreate (https://developer.apple.com/documentation/coregraphics/cgevent/tapcreate%28tap%3Aplace%3Aoptions%3Aeventsofinterest%3Acallback%3Auserinfo%3A%29) ## Deliverables - Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery. - Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary. - Do not show unverified market numbers in the UI or API. - Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge. - If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code. - If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype. - When done, explain what changed, how to run it, and how to verify it. - Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.