I built SpaceHop to fill the gap left by the lack of a Windows alternative to SpaceLauncher. Tap the space bar to type normally; hold it with other keys to launch apps, run scripts, or turn off your monitor. It’s a single exe with no runtime dependencies or admin privileges required, and a native settings interface.
I built it in under a day on a Mac, using a Windows VM, automated self-checks, and hands-on testing. After optimization, launching apps is nearly as fast as opening them directly, though I’m not sure the occasional window-switching issue is fixed.
What struck me most was how much AI accelerated development. A good idea is no longer a moat; what matters is making software feel effortless and indispensable. The source code and download are available—give it a try.
On the Mac, SpaceLauncher is one of those productivity apps you can't live without once you've tried it. Hold down the space bar and press another key, and you can do just about anything—not just open apps, but run scripts too. Windows has never had a good alternative. I used to have the idea but not the skills to build it. That's changed. I've built quite a few apps lately, and it was time to finally scratch this itch.
What I wanted to build
Having built a few apps before, I knew that features weren't enough: performance mattered just as much. So before I started, I set a few requirements:
The most important part was distinguishing a tap from a hold. Tapping the space bar should work normally; an action should only fire when you hold it down and press another key:
Building Windows software on a Mac
My development environment is on a Mac, but things like keyboard hooks, the system tray, and window switching can only be properly tested on an actual Windows desktop. Then I remembered that tw93, the creator of Mole, had written on his blog about how he developed Mole for Windows on a Mac, so I borrowed his setup: run a Windows virtual machine in Parallels, cross-compile on the Mac, put the build in a shared folder, and run it in the VM. I also set up GitHub Actions to run the same self-tests on windows-latest.
During testing, I kept watching the VM's screen: the program was sending keystrokes, opening windows, and taking screenshots on its own, while Claude Code read the reports and kept making changes. I was honestly amazed at how smoothly and efficiently the two worked together. It really brought home how low the barrier to building software has become.
Trying it out and fixing bugs
Once development was done, it was time to test and fix bugs. First came a few small UI/UX issues I found just by clicking around: the checkboxes next to shortcuts wouldn't respond, changes to the “Key timing” values weren't saved, and switching the leader key from “Tap” back to “Hold” changed it from Space to F12. The automated self-tests missed all of these. It took a person clicking through the interface to find them, and they were quick to fix.
Then there was performance. Even in casual use, I noticed that opening Edge through SpaceHop always involved a pause, while clicking the Edge icon opened it almost instantly. At first I thought the keyboard hook was slow, so Claude Code measured it: there was no measurable overhead between the keypress and the launch request. The delay was in the launch itself. The app list stored Start menu shortcuts, and just having Windows resolve one took a hundred or two hundred milliseconds. Once I changed the code to read the shortcut itself and create the process directly, it was about as fast as launching the exe directly.
That one was quick to find and quick to fix.
I should also be honest about this: when I hold down the space bar to switch back and forth between Edge and File Explorer, sometimes the switch doesn't happen. Claude Code couldn't reproduce it in the VM no matter what it tried, so it only made some defensive changes. I can't say for sure whether it's actually fixed. I've been using SpaceHop for a while now, and it feels great to use. There may still be bugs I haven't found, but nothing major, and they should be quick to fix when they turn up.
A little bonus: turning off the display
Windows isn't like macOS here: on a Mac, you can press ESC at the lock screen to turn off the display. Windows has no equivalent. My old workaround was a script on the desktop that I'd double-click whenever I wanted the screen off. It was clunky.
To my surprise, the SpaceHop that Claude Code built based on SpaceLauncher came with a “Turn off display” action by default. It had a bug at first: the screen would go dark and immediately light up again. Releasing the shortcut keys counted as keyboard activity and woke it back up. I changed it to wait until there had been no keyboard activity for 0.7 seconds before turning off the display, and now it works beautifully.
Wrapping up
The other thing that surprised me was, again, how fast development went: this app took less than a day from start to finish. That's much faster than my previous two projects. Partly it's because I have more experience now and know which pitfalls to avoid. But it's also because Fable 5.2 really does exactly what I ask, and it's incredibly fast.
People keep saying ideas are the most valuable thing, but in the current landscape, I don't think a good idea is much of a moat anymore. A big company can take your idea in an instant and pour enormous resources into pulling ahead. Even anyone at the controls of an AI can quickly build a copy. What lasts is making something so natural to use that you can't live without it.
Code and downloads are here: github.com/Jaaayden/spacehop. Give it a try.