Skip to content
Circle LensGet Circle Lens

Build story · October 2026

A simple zoom idea,
and the polish it took.

Circle twice with the mouse, or tap Shift twice, and a magnifying lens opens at the pointer and follows it anywhere on screen. That is the whole idea. Getting it to feel right took a renderer of my own, a gesture simulator, three edges, three settings panels, an installer, and ten releases.

A dark AI chat with a long answer. A round lens magnifies a line about an alert that fired late, at 1.8 times.
The lens on a long AI answer. Click the picture, or circle twice anywhere on this page: it has the lens built in.
opening animation, paced to the display
≈120 fps
memory while it waits
≈13 MB
of hand-drawn circles caught
99.8–100%
0.4 to 1.2, on 11 October 2026
10 releases

01 The problem

Why a lens, and why now.

I read far more long, generated text than I used to: AI answers, summaries, drafts. They are long and evenly weighted. Every paragraph looks as important as the one before it, so over a long passage my focus drifts and the one sentence that matters slips past.

On a compact laptop screen, small text also strains the eyes. The usual fixes make it worse somewhere else. Display scaling and browser zoom enlarge everything, and the layout of every other window and panel falls apart.

I wanted to zoom only what I am reading, only when I need it, and then have the zoom get out of the way.

02 Where it came from

A feature that wanted to leave home.

The idea started as the reading lens inside BoundStretch, my own cockpit app, written in React. Circle twice and a magnifier opens and follows the pointer, with a camera-like spring as it opens. Circle Lens takes that feature out on its own, in three forms:

  • A desktop app that works anywhere on the screen: Windows, with Mac and Linux in preview.
  • A browser extension for Chrome and Edge on any computer. It magnifies a capture of the tab.
  • A website script, so a site can offer the lens to its own visitors.

I built it with Claude Code as my pair programmer. Ten releases, from 0.4 to 1.2, went out on 11 October 2026.

03 Choosing the stack

Small enough to forget it is running.

A tool that sits in the tray all day has to cost almost nothing while it waits. That ruled out the comfortable choices.

Desktop technology options considered for Circle Lens
OptionCostDecision
ElectronAbout 150 MB on disk, 80 to 150 MB of memoryDropped
TauriWebView2 uses 30 to 60 MB, and it needs a Rust installConsidered
Go with plain Win32 callsStandard library only, no dependencies, one exe of under 5 MBChosen

04 Version 0.1

Windows’ own magnifier, and its limits.

The first version used the Windows Magnification API. It worked, at a cost:

  • Memory sat at 11 MB idle and about 45 MB with the lens open, because the magnifier loads Direct3D.
  • The lens updated at about 35 fps, and the opening animation was choppy. Each call cost about 10 ms on a 4K screen at 200% scaling.
  • A cold open stalled for about half a second.

It also taught me the lesson that shaped everything after it. A low-level mouse hook on Windows holds up every mouse event on the system until it returns. If the hook shared a thread with the UI, any stall in drawing would lag the mouse everywhere, in every app. So the hook moved to its own thread.

05 Version 0.2

Drawing the lens myself.

For 0.2 I dropped Windows’ magnifier. The app copies the screen around the pointer, with its own window left out of the copy, and composites the lens in software, in Go. The animations are reproduced keyframe by keyframe from the original CSS. A ticker thread waits for each display refresh, and a separate capture thread grabs the screen.

Opening · 560 msA spring from 55% scale; the blur and fade are done by 60%. Played at a quarter of real speed.

On a 120 Hz 4K laptop screen the opening draws 68 to 69 frames in 560 ms, about 120 fps. A steady frame costs about 1.4 ms across 8 cores, of the 8.3 ms a frame has. Nothing runs while the mouse is still.

Lens refresh rate

Version 0.1≈35 fps
Version 0.2≈120 fps

Memory with the lens open

Version 0.1≈45 MB
Version 0.2≈37 MB

06 The gesture

Teaching it what a circle is.

“Circle twice” sounds easy to detect until you look at how people actually move a mouse. I tested it by simulation: hand-drawn circles that wobble, drift, turn slightly oval and change speed, against ordinary mouse use such as reading sweeps, curved reaches, idle wandering and hover jiggle.

The simulation found real bugs. The 1½ and 2½ circle settings were caught only 2 to 28% of the time, slow 3-circle drawing 0 to 61%, and ordinary movement sometimes added up to “two circles” and opened the lens uninvited. The fixes: the last full turn must close on itself and be round, a 250 ms pause starts over, the time window scales with the number of circles, at least 64 px across, and 95% of each turn drawn.

Circles detected, before and after the fixes

1½ and 2½ circlesBefore · 2 to 28%After · 99.8 to 100%
3 circles, drawn slowlyBefore · 0 to 61%After · 99.8 to 100%

After the fixes, detection is 99.8 to 100% at every setting, with no accidental opens from realistic ordinary use at 1½ circles or more.

07 Flicker and shortcuts

People keep spinning.

Once detection worked, a new problem showed up. People keep circling for a moment past the point where the lens opens, so it would flip open, shut, and open again. The gesture now stays spent until the circling stops, and there is a gap between open and close, 1.5 s by default.

Not everyone wants to draw, so one shortcut also opens and closes the lens: Shift twice. I avoided Ctrl twice because PowerToys’ Find My Mouse already uses it. You can record your own, and since 0.8 the zoom keys and an optional close key are yours to set too.

08 Moving fast

Zooming out when you move fast.

At a high zoom, the lens shows too little to see where you are going. So fast pointer movement or fast scrolling eases the zoom out in proportion to speed: to half the zoom at full speed, never below 1×. It glides back in as you slow down.

The same chat twice, side by side. On the left the lens is still at 4 times; on the right it has eased out to 2 times while the pointer moves fast.
Still at 4× (left), and eased out to 2× while moving fast (right).

09 Edge feel

Three edges, one kept.

The edge of the glass decides whether the lens feels like an object or a pasted rectangle. I tried three:

  • A water-droplet edge, a 1 to 2 px refraction. Dropped: not noticeable, and it cost time every frame.
  • A wide zoom ramp across the outer quarter. Dropped: far too much.
  • A thin convex rim, a 14 px band where the zoom eases off, like real glass. Kept, as a switch, and skipped during animations so they stay at 120 fps.
Two lenses over a dashboard tooltip: flat glass on the left, and the convex rim on the right, where the zoom eases off in a thin band at the edge.
Flat glass (left) against the convex rim (right).

10 Closing

A close that reads as a close.

My first close faded the glass while it shrank to 62%, so it read as a glitch: the lens seemed to dissolve rather than put itself away. Now the close takes 340 ms. The glass draws in to under half its size while fully opaque, then fades and blurs out as it goes down to 30%.

Before · 300 msFaded the whole way while it shrank to 62%.
Now · 340 msShrinks first, fully opaque, then fades and blurs out.

11 Tray and settings

The parts you see every day.

The settings panel went through three designs. The first, in 0.2.2, was Windows 11-style and followed light or dark mode. The second, in 0.4, was a compact dark panel: one line per setting, 425 px tall instead of 560. In 1.1 it took this page’s calm monochrome look, with the keys you set shown as keycaps. In 1.2 the magnifier mark gave way to a plain ring: the lens itself.

Three settings panels side by side: two tall Windows 11-style panels from version 0.2.2 in dark and light, and the shorter, compact dark panel of version 0.4.
0.2.2 in Windows 11 dark and light, and the compact 0.4 panel.
The tray panel: a white Open lens button with a Shift twice keycap, chips for circles, zoom, size and wait, the shortcut, zoom keys and close key as keycaps, switches, and a links row.
The panel today, in the same look as this page.
The first tray icon, a magnifying glass with a circular arrow inside, at five sizes on dark and light taskbars, on, open and paused.
The first tray icon, drawn in code for each size’s pixel grid. Since 1.2 it is a simple ring.

12 Installing

Installable, without asking for admin.

A tool nobody can install is a demo. From 0.4 the exe installs itself: per user, no administrator, a Start menu entry, starts with Windows, and Uninstall in Settings. Since 0.6 it keeps itself up to date, and since 0.7 it does all of it through one window of its own.

Six Circle Lens windows side by side in a near-black look: install, installing, ready, uninstall, the first page of the How to use tour, and What’s new.
Setup today: install, installing, ready, uninstall, the tour, and what’s new.

The exe is not code-signed yet, so browsers call it “not commonly downloaded” and Windows shows “Windows protected your PC” the first time. Both mean unfamiliar, not harmful: keep it, then choose More info and Run anyway.

Kept and dropped

What it took
to get a circle right.

  1. Origin

    A reading lens in BoundStretchKept

    The feature started inside my own cockpit app, in React: draw a circle twice and a glass follows the pointer.

  2. 0.1

    Windows’ own magnifierReplaced

    About 35 fps, Direct3D loaded for 45 MB, and a half-second stall on a cold open.

  3. 0.2

    Its own rendererKept

    Copy the screen around the pointer, leave its own window out, draw the glass in software. About 120 fps.

  4. Gesture

    Taught what a circle isKept

    Simulated hand drawing caught some settings at 2 to 28%. After the fixes: 99.8 to 100%.

  5. Flicker

    People keep spinningKept

    It waits until the circling stops, then a 1.5 s gap, so spinning on never closes it again. Shift twice joins the gesture.

  6. Edge

    A water-droplet bendDropped

    A 1 to 2 px refraction at the rim. Not noticeable, and it cost time every frame.

  7. Edge

    A wide zoom rampDropped

    Easing the zoom across the outer quarter of the glass. Far too much.

  8. Edge

    A 14 px convex rimKept

    Only a thin band at the very edge eases off, like real glass. Kept, as a switch.

  9. Close

    A close that reads as a closeKept

    340 ms: the glass shrinks first, fully opaque, then fades and blurs as it goes on shrinking.

  10. 0.4.0

    Installable, and on GitHubKept

    A compact settings panel, and an exe that installs itself per user. Released as open source under MIT.

  11. 0.5.0

    On websites, tooKept

    The lens as a 7 KB script on npm, magnifying a live copy of the page the way BoundStretch’s original did. This page runs the same idea.

  12. 0.6.0

    Keeps itself up to dateKept

    About once a day it checks the GitHub releases, verifies the download’s size, SHA-256 and version, and swaps in while the lens is closed. One switch turns it off.

  13. 0.7.0

    Setup in the same languageKept

    A setup window instead of plain Windows dialogs, and a tray panel in this page’s look. A screen reader still gets Windows’ own dialogs.

  14. 0.8.0

    Your keysKept

    Change the zoom keys and add a close key, like Esc. They’re taken only while the lens is open and handed back the moment it closes.

  15. 0.9.0

    A tour, and a calmer panelKept

    How to use, a four-page tour in your own keys, and What’s new, both inside the app. A lighter tray panel, and a tray icon that turns blue while the lens is open.

  16. 1.0

    Version 1.0Kept

    Stable everywhere: the Windows app, the extension and the website script install, update and uninstall cleanly and keep your settings. And a proper app icon.

  17. 1.1

    The same calm look, in the appKept

    The setup window and tray panel took this page’s monochrome look, and the app icon became a near-black tile with a blue glass.

  18. 1.2

    A lens, not a search iconKept

    The magnifier mark became a thin ring with a glint, the lens itself, on a new white app icon.

What I learned

Simple to use
is not simple to build.

Each of these was invisible when it worked, and obvious when it did not.

01

Measure before you polish

Frame rate, longest gap, memory: Windows’ magnifier looked fine until the numbers said 35 fps and a half-second stall. The rewrite was chosen by the numbers, and every change after it was checked against them.

02

Simulate the hands

A gesture that works when I draw it carefully is not a gesture. Simulated circles that wobble, drift and change speed found settings that worked 2% of the time, and ordinary mouse moves that opened the lens uninvited.

03

Polish is mostly subtraction

Three edges tried, one kept. Two panel designs, then a calmer third. The glows, gradients and sparkles went too. What stayed is what you notice only when it is missing.

04

The boring parts make it real

Install without an administrator, update safely, uninstall cleanly, keep settings across all of it. None of it shows in a demo, and all of it decides whether people keep a tool.

05

Borrow the screen politely

The mouse hook runs on its own thread so it never lags the system. Keys are taken only while the lens is open. Nothing runs while the mouse is still, and nothing goes online except the optional update check.

Updates

Since the first release.

Every version, newest first. The full notes are on GitHub.

  1. 1.3 preview

    Mac and Linux, in preview

    Preview builds for macOS 14 or later and Linux on X11, with the same gesture, lens, zoom and menu as on Windows. Early and unsigned, and not yet self-updating; Linux was tested on a real X server, the Mac build not yet on a real Mac. Help test them.

  2. 1.2.3

    Clean builds, reliable updates

    Windows Defender’s cloud check misjudged two published setup files as threats, a false positive on those files rather than the program. Fresh builds scan clean, and every release is now watched. Updates no longer fail with “Couldn’t update”: the new copy waits for the old one to close before it swaps in.

  3. 1.2

    A lens, not a search icon

    The magnifier with its arrow became a thin ring with a soft glint: the lens itself. It is the tray icon, the panel’s mark and the extension’s button, and the app icon is now that ring on a white tile. The welcome screen says “Circle twice. Read anything.”

  4. 1.1

    The same calm look, in the app

    The setup window and tray panel moved to this page’s monochrome look: near-black, white primary buttons, light switches, no gradients or glows. The app icon became a near-black tile with a white magnifier and a blue glass, its one colour.

  5. 1.0

    Version 1.0

    The Windows app, the browser extension and the website script are stable: they install, update and uninstall cleanly, and keep your settings.

  6. 0.9

    A tour, and What’s new

    How to use, a four-page tour in your own keys, and What’s new, both opened from the tray panel’s links row. A lighter panel, and a tray icon that changes while the lens is open.

  7. 0.8

    Your keys

    Change the zoom keys and add a close key, such as Esc. They are taken only while the lens is open and handed back the moment it closes, so even plain Esc is safe.

  8. 0.7

    A setup window of its own

    Install, update and uninstall through one window with a progress ring and a Try it now button at the end. With a screen reader running, setup uses Windows’ own dialogs so it stays readable.

  9. 0.6

    Keeps itself up to date

    About once a day it checks the GitHub releases. A download must match the size and SHA-256 GitHub publishes, and report the expected version, or it is deleted unrun. One switch turns it off, and then the app never connects on its own.

  10. 0.5

    On websites, too

    The lens as a 7 KB script for any website, on npm as circle-lens or one script tag. Like BoundStretch’s original, it magnifies a live copy of the page rather than a screenshot.

  11. 0.4

    Installable, and on GitHub

    The exe installs itself, per user, with no administrator. Released as open source under the MIT licence.

Free · MIT licence

Circle twice.
Read the line.

Work with me

Have a project in mind?

I build with teams on focused projects, and I am open to long-term roles too, full-time or fractional. Tell me what you are working on.

Book a call on Calendlyhi@fauzul.com

Or find me on LinkedIn.