Trust you can verify, not just promise
Closed window managers ask you to trust a privacy policy. An open one lets you check. With flingdows on GitHub, you can read precisely how the Accessibility permission is used, which is to move windows and nothing more, and rebuild the app yourself so the binary you run matches the code you read.
For software that touches every window on your machine, that verifiability is worth more than a few dollars saved. It is the difference between being told it's fine and seeing that it is.
Make it yours
MIT is a permissive license, so you are free to fork flingdows, change how the physics behaves, wire in your own gestures, or borrow pieces for another project. If your idea of the perfect fling differs from the defaults, the code is right there.
It also means the project can grow with its users. The roadmap, including corner and edge snapping presets, lives in the open, and contributions are welcome rather than walled off.
frequently asked
- Where's the source code?
- On GitHub. flingdows is open source under the MIT license, so the full code is public to read, build, and fork.
- Can I build flingdows myself?
- Yes. You can clone the repository and build the macOS app from source, then run the binary you compiled.
- Can I fork it or reuse the code?
- Yes. MIT is permissive, so you can fork, modify, and reuse the code, including in your own projects, with attribution.
- Is open source why it needs Accessibility access?
- No — any app that moves macOS windows needs Accessibility access. Being open source is what lets you verify it uses that access only to move windows.
Last updated June 6, 2026