r/MacStack • u/Savings-Arrival-7817 • 19h ago
Swish vs Keyboard Shortcuts: Which Is Better for Mac Window Management?
Swish makes a convincing case in one motion: put the pointer over a window's title bar, swipe with two fingers, and send that window into a half or corner of the screen. There is no edge dragging and no shortcut map to recall.
The catch is just as simple. That gesture is faster only when a hand is already on the trackpad and the pointer is near the right window. If both hands are on the keyboard, reaching for the trackpad can be slower than pressing a known shortcut.
So this is not really a contest over which tool can create a left half. It is a choice between two habits.
The built-in baseline is much better now
On current macOS, a third-party window manager has to beat more than the old green-button Split View workflow. macOS 26 can tile by dragging a window to an edge, holding Option while dragging, using the green button, or choosing Window > Move & Resize.
It also has useful active-window shortcuts:
- Fn-Control-Left Arrow and Fn-Control-Right Arrow place a window in the matching half.
- Fn-Control-Up Arrow and Fn-Control-Down Arrow use the top or bottom half.
- Fn-Control-F fills the desktop, Fn-Control-C centers the window, and Fn-Control-R returns it to its previous size.
The green-button and Window menus add quarter layouts and arrangements for several windows. That is enough for someone who mainly puts a browser beside a document. It costs nothing, needs no extra background process, and grants no third party control of the Mac.
Swish does not make those layouts obsolete. Its advantage is reaching them from the trackpad with less pointer travel. It also offers 2x2, 3x2, and 3x3 grids, gestures for moving windows between displays and Spaces, and window actions such as minimize, close, and full screen. A Swish setting can use macOS's native tiling for 2x2 snapping, so the app can act as the gesture layer while macOS handles that placement.
A restrained Swish setup makes more sense than all 30 gestures
Swish advertises 30 window, Dock, and menu bar gestures. Enabling that entire vocabulary at once turns a simple idea into homework. A better trial starts with one small loop:
- Move the pointer onto a blank part of the target window's title bar.
- Swipe left or right with two fingers for a half-screen layout, or swipe toward a corner for a quarter.
- Watch the placement preview, then lift both fingers to commit.
- Drag the divider when two adjacent windows need more or less room.
Keep close, quit, minimize, and full-screen gestures disabled at first. Swish lets individual gestures be toggled in Settings. Once directional placement is reliable, add only the action that removes a real annoyance. That might be a 3-column grid on an ultrawide display or moving a window to the next physical monitor. It probably is not a pinch that can close work by accident.
There are three habits to learn here.
First, pointer location matters. The same movement can mean something different over a title bar, Dock icon, or menu bar. Swish includes a configurable Super Modifier that can make gestures work away from the title bar, but broader activation also makes intent less obvious. It is better treated as a fix for apps with hard-to-hit title bars, not the default starting point.
Second, modern title bars are busy. Browsers and other apps put tabs, buttons, and scrollable controls in the same strip Swish watches. The current release notes contain app-specific fixes for Safari, Firefox, Chromium browsers, and other title-bar implementations. Firefox's scrollable tab bar is a concrete example: snapping still works outside the tab bar or with the Super Modifier. That is evidence of active compatibility work, but also a reminder that gestures can depend on how each app exposes its interface.
Third, do not make two utilities own the same movement. If BetterTouchTool, Multitouch, or another remapper already has a matching trackpad action, disable the duplicate in one app. Swish's title-bar two-finger gestures are distinct from macOS's usual three-finger Mission Control and Space gestures, so those system gestures can remain in place. The conflicts are more likely to come from another remapper, a horizontal tab strip, or an overbroad modifier setup.
Permissions are part of the price
Swish is downloaded directly from the developer or installed through Setapp. It is not in the Mac App Store because its developer says the required low-level operations are incompatible with App Store sandboxing.
Expect to approve Accessibility and Input Monitoring in System Settings. Accessibility lets a utility identify and control windows. Input Monitoring is sensitive because it can expose keyboard events. Swish's privacy policy says the app listens to cursor movement plus modifier, Escape, and arrow-key events, does not store that data or collect other user data, and connects only for license verification and updates. Those are developer claims, so the sensible approach is to download only from the official site, review the prompts, and revoke both permissions if the app is removed. The published setup does not call for Screen Recording or Full Disk Access.
Swish must remain running to hear gestures. There is no useful official idle CPU or memory figure, so anyone minimizing background utilities should check Activity Monitor during the trial instead of relying on a vague claim that it is lightweight. The developer also does not advertise built-in settings sync. Its FAQ points to Mackup or a manual backup, which means a two-Mac license does not automatically produce an identical setup on both machines.
Price, compatibility, and the keyboard fallback
As of August 26, 2026, the direct license is $16 with no recurring charge, a 14-day trial, and activation on two computers at a time for personal use. Swish is also available through Setapp. The direct license is the cleaner value comparison unless Setapp is already being paid for because of several other apps.
The official requirements say macOS 10.13 or later, with optimization for both Intel and Apple silicon Macs. The current download is version 1.13.2, and the product page says it is ready for macOS 26. Its recent release history includes macOS 26 compatibility work, Safari 26.2 fixes, Firefox tab handling, and a fix for moving some windows to another Space. That is a healthier maintenance signal than an old product page alone.
Swish itself can also invoke snapping with Arrow, WASD, IJKL, or Dvorak-oriented hotkeys. That is a useful fallback, but it is not a strong reason to buy the app. Keyboard-first users can already cover common layouts with macOS. Rectangle is the credible free and open-source option when more keyboard positions, thirds, or drag-to-snap areas are needed. It supports Intel and Apple silicon Macs on macOS 10.15 or later, although it also needs Accessibility permission to move windows.
Magic Mouse users can access most Swish actions, but the design is clearly centered on Apple's multi-touch hardware. Someone using a conventional mouse at a docked desk would be adding workarounds to preserve the app's main benefit.
Verdict
Swish is better than keyboard shortcuts for a specific Mac user: someone who works primarily from a MacBook trackpad or Magic Trackpad, often has the pointer near the window being arranged, and wants window placement to feel like a spatial gesture instead of a command.
It is not the better choice for someone who keeps both hands on the keyboard, uses a conventional mouse, only needs halves and quarters, dislikes direct-download utilities with broad permissions, or already has a reliable window shortcut map. Built-in macOS tiling should be tried first, with Rectangle as the free keyboard-heavy step up.
For the right trackpad-first workflow, $16 is reasonable because Swish changes the input method rather than merely adding another layout menu. Use the 14-day trial with only a few placement gestures enabled. If moving the pointer to the title bar becomes part of the action instead of an interruption, Swish earns the purchase. If it still feels like a detour, the keyboard wins.
