Show HN: I built a tool to solve window management
I built this because I couldn't find a window switching/management solution that worked for me. I tried all kinds of different solutions, virtual desktop extensions, obscure GUI window managers, you name it. Overtime I realized I wanted something that prioritizes one window at a time, is keyboard driven with has minimal if no GUI elements. I figured this part out, but knew something was missing. I had my eureka moment when I realized I could combine my switching method with a prediction algorithm. This led to the creation of Smart Switcher.
Smart Switcher is a data driven window switcher aimed at improving the overall window switching experience. It logs data on your windows switching, then a prediction algorithm analyzes this data and uses it to predict which window you would want to switch to next. When you need to switch windows, you press the switch shortcut to switch to the next predicted window. If this isn't the window you wanted, press the override shortcut to switch to the next most likely window. You can press the override shortcut as many times as needed until you arrive at your desired window.
It’s a paid app with a demo and trial version. There is a introductory discount and some additional discount tiers for early adopters.
Any feedback is appreciated! Thanks!
Personally (as someone with ADHD), this would just relentlessly grind my gears. My thoughts are unpredictable by nature and so I value the "reliability" of knowing my chrome is two alt+tabs away, etc.
If an algorithm started messing with this and changing throughout the day... Damn, I'd go crazy.
No comments yet
So after switching, they will need a short moment to reorient: understand where they were taken, check if it matches where they wanted to go, and then either switch again or stop the switching process to resume work. In UX design, it's better if you can complete a longer process without having to halt and reorient many times in the process (like opening a menu that was hidden and wait for a loading animation to complete, until you can actually read the menu items are).
If it's impossible to keep a mental model of where you are in the system, and how you can move to another specific window, then actually EVERY window switch requires much more effort and conscious thought.
I think windowing systems, virtual desktops, spotlights, stage managers, exposés, mission controls, are all too complicated... I don't know what the solution is, and I think it's great that people are working on novel solutions. But I do know I want to easily switch between 2-4 windows without the order randomly changing.
The main problem with them is system support, they are buggy when tacked on top of a desktop OS (PaperWM), or require a pretty finicky custom setup (Niri).
Alt+tab is an optimal controller.
Maybe operating on the order of items in the queue, and use your prediction to sort windows, allowing faster selection? Even that disrupts sense of place - I know what applications I have open and where they are, and if I'm using alt+tab over 5 or more, I know the order in which I've opened them, and "where" I need to go to navigate to them.
There are second and third order impacts to changing interface behaviors, so the superficial benefit you might gain will be lost by creating friction at different levels.
A single key is insufficient for granular control, and no AI widget short of human level AI is going to capture the edge cases, which will create friction, at which point I will aggressively remove the offending piece of software.
I'd go back to the drawing board and work on a more complex model of window switching and all the ways in which people use alt+tab, and see if there's a use case for your idea at a different level. As it is, for me, it would interfere with a reliable and predictable interface, and I would be very unhappy.
Having to iterate through your windows is not optimal. I use sway, with windows divided across workspaces. So if I want to switch to my web browser I hit super+1. If I want to switch to my code editor I hit super+2. If I want to switch to my terminal(s) I hit super+3. I use 4 through 0 for other random windows (for example, I usually launch games or videos on 0. If I'm working in two code bases I generally put the editor and terminal for the 2nd code base on 4 and 5).
What takes you O(n) takes me only O(1).
Super+h/j/k/l (left, down, up, right) to move focus spatially feels much more natural, given that you can know at a glance which window is to the left of yours but they typically give no indication about whether a window is the 6th most recently touched or the 7th...
One way to implement this is to use window manager with one workspace per window (or multiple related windows) and use a single hotkey to switch to it. Very muscle memory efficient and takes no confirmation delay.
Top middle is browser. Bottom left is everything chat and communication. Center left is the editor. Whatever is out of place is mercilessly closed or moved if I'm feeling generous.
I also use a tiling WM (awesomeWM). I tend to keep one window per workspace, and then merely select multiple workspaces if I need to see multiple windows in tandem.
For my work Windows laptop, I've installed a virtual workspace manager.
Sounds like tiling window managers like sway or i3. Those don't have any sort of predictive switching but otherwise:
My personal hot take is also that most people who think they really need another monitor are just addressing these symptoms because they're exhausted by alt-tabbing through 15 windows. They would be more productive on a single screen with a nice workspace configuration, though there are of course plenty of good reasons to want multiple monitors.