<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Coder Legion - Recent posts tagged demos</title>
<link>https://coderlegion.com/tag/demos</link>
<description>Powered by Question2Answer</description>
<item>
<title>I Built a Screen Recorder That Never Uploads Your Video — Here's How</title>
<link>https://coderlegion.com/25285/i-built-a-screen-recorder-that-never-uploads-your-video-heres-how</link>
<description>&lt;p&gt;For years, recording a quick screen walkthrough meant picking your poison.&lt;/p&gt;
&lt;p&gt;Loom and its clones upload everything to the cloud the moment you stop recording — fine until you're screen-sharing something under NDA, a client's dashboard, or your own unpublished code. OBS Studio and Camtasia go the other way: powerful, local, and completely overwhelming if all you want is &quot;record my screen, highlight my cursor, export a video.&quot; And almost everything in between slaps a watermark on your export unless you pay upfront, before you even know if the tool fits how you work.&lt;/p&gt;
&lt;p&gt;I wanted something in the middle: as easy as Loom, as private as OBS, with the one feature I keep missing everywhere — cursor highlighting and auto-zoom-on-click, so I stop narrating &quot;and now I'm clicking this button over here&quot; out loud in every recording.&lt;/p&gt;
&lt;p&gt;That's ScreenGlimpse.&lt;/p&gt;
&lt;p&gt;The realization&lt;br&gt;
Once I actually mapped out what I wanted, it came down to three requirements:&lt;/p&gt;
&lt;p&gt;Nothing leaves the device. No upload step, no &quot;processing in the cloud,&quot; no account required just to hit record.&lt;br&gt;
The recording should explain itself. A viewer should be able to follow where the action is happening without the narrator constantly saying &quot;up here&quot; or &quot;over there.&quot;&lt;br&gt;
No paywall on the basics. Recording, exporting, and using it daily should work for free — the paywall should be for depth, not for entry.&lt;br&gt;
What I built&lt;br&gt;
ScreenGlimpse is a screen recorder that runs either as a native desktop app (Windows, macOS, Linux) or straight in the browser with no install — same recording engine either way. Every recording, every encode, every export happens on-device. There's no backend that ever sees your video.&lt;/p&gt;
&lt;p&gt;The free tier (&quot;Glimpse&quot;) is unlimited local recordings with mic, webcam, and system audio, exported as WebM. The paid tier (&quot;Focus&quot;) adds the features that make a recording easier to follow and easier to share: automatic cursor highlight and click-to-zoom, 4K/MP4 export, no watermark, region screenshots with markup, a freeform whiteboard, and GIF export.&lt;/p&gt;
&lt;p&gt;The technical stack&lt;br&gt;
Electron + Angular/Ionic for the shell. Using Ionic for the UI meant the same codebase could ship as a desktop app and run directly in a browser tab, instead of maintaining two separate front ends for &quot;install it&quot; and &quot;just try it.&quot;&lt;br&gt;
Native cursor tracking via a global input hook (not browser mouse events) — this is what makes the cursor highlight and click-to-zoom actually work: it has to track the cursor and clicks system-wide, independent of whatever the browser's getDisplayMedia capture stream reports, and keep working smoothly during the recording itself.&lt;br&gt;
ffmpeg compiled to WebAssembly, running entirely client-side for encoding and export. No render queue on a server, no upload-then-download round trip — the trade-off is it's bounded by the user's own machine, which given requirement #1 was the right trade to make.&lt;br&gt;
On-device face/segmentation models (MediaPipe) for the optional camera effects — background replacement and camera filters run locally too, same privacy rule applied consistently instead of carving out an exception the moment a feature needed &quot;AI.&quot;&lt;br&gt;
Hosted checkout, not homegrown billing. Payment redirects to a third-party checkout page instead of embedding any payment UI or telemetry SDK in the app. It keeps the &quot;nothing leaves your device&quot; promise honest — the app itself never touches your card details or reports usage anywhere.&lt;br&gt;
What I learned&lt;br&gt;
Privacy isn't a feature you add later — it's an architecture decision. The moment you design &quot;record locally, but also let's add cloud AI effects,&quot; you've quietly broken the promise for a chunk of your users. Every feature I've added had to pass the same test: does this still work with the device offline?&lt;/p&gt;
&lt;p&gt;The paywall belongs on depth, not on entry. Free users get a genuinely usable recorder, not a crippled trial. That's the thing that gets someone to actually try it instead of bouncing off a pricing page.&lt;/p&gt;
&lt;p&gt;&quot;It just works, everywhere&quot; is more expensive than it sounds. Supporting Windows, macOS, and Linux with one codebase, plus a browser fallback with no install, meant a lot of the hard work was in the boring parts — packaging, auto-updates, platform-specific permission quirks — not in the recording feature itself.&lt;/p&gt;
&lt;p&gt;Try it&lt;br&gt;
Free in the browser, no account needed: screenglimpse.com. The desktop app (Focus) adds cursor highlight, 4K export, and no watermark for $5/mo or $50/yr — or pay once ($100) and keep it.&lt;/p&gt;
</description>
<category>Articles</category>
<guid isPermaLink="true">https://coderlegion.com/25285/i-built-a-screen-recorder-that-never-uploads-your-video-heres-how</guid>
<pubDate>Mon, 24 Aug 2026 11:13:39 +0000</pubDate>
</item>
</channel>
</rss>