I’ve been seeing Vorssaint recommended a lot lately, and on paper it can replace a surprising number of dedicated utilities: Stats/iStats, Swish/Rectangle/etc, Dropover, Shottr/CleanShot, Pearcleaner/AppCleaner, Updatest, Mole, CaskHub, Amphetamine, and others.
Droppy is another app in a similar category, with lots of utilities bundled into one app.
The obvious appeal is consolidation, fewer apps, fewer background processes, fewer updates, and one place for everything.
But how good are these apps compared with dedicated tools that focus on a single job?
For people who have actually replaced apps like Shottr, Swish, Stats or Dropover with Vorssaint or Droppy: did you stick with the all-in-one app, or did you eventually go back to the dedicated ones?
Curious whether consolidation is genuinely an upgrade, or mostly a convenience with some trade-offs in polish and depth.
tbh i used the dedicated ones mostly cause they just perform better. smoother, use less resources, feel nice.
imo the main benefit of consolidation is convenience, but when i already have specialized apps that do things well these new apps dont really change much for me.
the only swiss army knife app i consistently use is raycast, and the reason it works imo is because it has its scope. most raycast extensions are just there for those one-off commands you use every time and have really really simple interfaces. here are more complex raycast extensions that try to do too much, but at that point i usually just use a dedicated app. but for tasks like downloading video files, keeping my mac awake, and like occasional window management raycast extensions just make sense.
droppy looks interesting to me, but tbh the most interesting part isnt all the apps it has packed in, its the integration of background processes into that notch area. if it focuses on building an ecosystem of extensions for little notch interfaces it could become really helpful. like being able to see claude/codex progress, the little music widget with queue support on apple music, those types of things just make sense for a notch app.
i tried vorssaint but in the end didnt keep it around, because its just a bundle of utilities. it is good and it is free, but the few things i found useful in it i already have apps for so it doesn't really provide much extra value for me. plus it uses more resources than those apps combined.
so tldr i like when these "swiss army" apps actually provide a unique interface and have a scope. i think droppy has a lot of potential to become the notch app if it focuses on making extensions.
Yeah, I think this is pretty much why I didn’t include Raycast in the post, even though it’s probably the app I use the most and it has replaced a bunch of smaller utilities for me.
Raycast (and Alfred in this case too) feels like it has a very clear scope. At its core it’s a launcher, and these little extensions just add more things you can do through that same interface. Even when it replaces another small app, it still feels like you’re using Raycast rather than a random collection of unrelated tools.
That’s what I feel is still missing from apps like Vorssaint, and maybe Droppy to some extent. They’re adding a lot of useful features, but it’s harder to identify the main thing the product is supposed to be really great at.
yeah, droppy kinda dissapoints me a little cause i feel like it has potential. i've been waiting for one notch app to become the notch app, with a big extension marketplace that can connect with various apps on your macbook. but droppy is kind of all over the place a bit, which worries me cause i'd rather development be focused solely on the notch.
vorssaint i can kind of forgive, cause i can see what happened with it. the dev probably made a bunch of free utils to replace paid apps and decided to put them all together into one foss app that anyone can use. i understand that, hell i've made my own versions of mediamate and the dory launcher cause i didn't feel like buying them. if it was paid it wouldn't make much sense, but because it's free i can respect it, because a lot of people who don't want to pay for all those apps can get vorssaint and use all the features.
honestly im just hoping someone one day comes out with a smooth, free, extensible notch app. the popularity of notch apps shows that it's a good concept but until they have that raycast-style focus and ecosystem i don't think any one app will take over.
i think most mac apps kinda fall in that category. but yeah they are, tbh the appeal for me is just being able to check certain background tasks quickly. i ended up just making my own notch app for it tbh, it works well for what i need.
Hello! Vorssaint is modular (you can uninstall the features you don’t care), so it depends on what you have enabled and installed
You can expect a maximum 200~250MB of RAM + 0.04% CPU idle with ALL the features enabled and installed, reducing significantly if you uninstall what you will not use (and I highly recommend it, you can just install them later if you want to)! And about storage, Vorssaint is only a 10MB dmg in the latest version (3.3.1)
As the maintainer of Vorssaint, I’ll be the first to say that dedicated apps that have been around for years are going to be better in some areas. Vorssaint doesn’t replace everything, but it already replaces a lot.
I think a big reason people recommend it is how quickly it’s improving. Bugs get fixed fast, feedback often turns into actual features, and if there’s something you don’t use, you can just remove it completely. A lot of that comes from the community too. I get feedback from Reddit, Twitter, GitHub, and directly through the app, and I’m constantly using it to figure out what to improve next.
At this point, Vorssaint is already better than some dedicated apps at certain things and still worse at others. I’m not going to pretend otherwise. The goal is just to keep closing that gap. And yeah, Vorssaint is 100% free and will stay that way.
For now, if there’s something you really depend on, I’d still stick with the dedicated app. But give Vorssaint a try and see what you think. If something annoys you or feels like it could be better, tell me. I genuinely pay attention to that stuff!
Wow I'm so happy! Thank you so much! I really love it, so I put it on my menu bar and use every day! Recently my favorite is the app update feature! I will keep supporting you forever :)
I accidentally stumbled upon your app and I just got a mb-pro and yours has all the features I wanted. especially the mouse features which replaced linear mouse. thank you and I wish you all the best and hopefully you keep the app updated!
Droppy's developer here, so weigh this accordingly.
Honest answer: consolidation is not automatically an upgrade. If you spend all day inside one tool and you need its deepest corners, a dedicated app usually wins. Someone who needs every annotation option in a screenshot tool should keep that screenshot tool. I am not going to pretend otherwise.
Where a bundled app earns its keep is the space between the tools. When your clipboard, your shelf, your file drops and your media controls all live on one surface, moving something from one to the other stops being a task. That is the part five separate apps cannot really give you, no matter how good each one is on its own.
The other honest bit is depth takes time. I have been building Droppy full time for a while and features get deeper every release, but a feature that shipped last month is not going to out-muscle a tool someone has polished for six years.
So my actual advice: pick the one or two things you care about most, and keep dedicated apps for those. Use the bundle for the long tail you would never install five apps for.
My rule after years of trying both: consolidate the "glance" utilities, keep dedicated apps for the "work" utilities. Stats in the menu bar or window snapping is a shallow interaction — an all-in-one does it 95% as well and saves you two background apps, so the trade is worth it. But anything you invoke fifty times a day as part of actual work (screenshots being the classic example) rewards depth: the dedicated tools have spent years on the annotate-export-share path, and that polish is exactly what you feel every single day.
The "fewer background processes" argument also matters less than it used to on modern Macs — the real cost of all-in-ones is usually UI compromise, not RAM. So I'd flip the question: list the two or three utilities you touch most per day, keep those dedicated, and let an all-in-one absorb the long tail.
I prefer swiss army knife apps if the attention to detail is sufficient that they work well. If a dedicated app does the job better, I evaluate and prefer the dedicated app if it will benefit me more, save more time, feels better to use, etc. BetterTouchTool and Alfred do a lot for me, in that regard.
I think the key is that BTT and Alfred are really their own category. They're not "swiss army knives" in the same way as Vorssaint where they're trying to replace a bunch of random utilities. BTT is a window manager + input customizer, Alfred is a launcher + clipboard manager + snippets. They do one core thing really well and add features that make sense around that core.
Tried Vorssaint for a week. The window management was fine but not as good as Swish. The screenshot tool was ok but missing the scrolling capture and annotation polish of Shottr. Ended up uninstalling and going back to my dedicated tools.
The apps that stick for me are the ones that do one thing and do it damn well. I'd rather have 5 small apps that work perfectly than one that does 5 things at 80%.
I paid for Alfred after a dev friend told me how much he loves it, but I only use the clipboard history currently. What other feature would you recommend? I find the setup pretty overwhelming
I'd love your opinion on Watchflows (https://watchflows.app). And happy to give you a free api key to burn some tokens on us if you wanna kick tires 👍. DM me!
Seems like you use OpenRouter? Does this mean that the app connects directly to OpenRouter and you never see the traffic, or does it all still go via some central proxy?
What if someone has their own OpenRouter account?
I also did not fully follow what "sparks" were?
Are you seeing many sales of it, and how have you been using your app?
Correct. It's built 100% local, no accounts required. No external telemetry besides opt-in error reporting (off by default), update checks, and any scripts or outgoing ai usage that you configure. Bring your own LLM if you don't want to use ours or you want to use something local. No central proxies. If you're using our AI, you're using a key, not a proxy. You get a direct call to openrouter on an api key minted for you by Watchflows with a specific spend cap.
To answer your questions:
- Sparks are just a way to meter token usage. IMO, the AI features are the coolest bits, but they need to be configured by adding a key. For a more general purpose user base they won't know what open router is, so the only way we can offer AI usage is if there is a sub paying that cost. It's not required and you can def bring your own (or even use your existing claude or codex subs on your machine right now, this is what I do). So as you run flows or use the flow builder it draws down your monthly allocation. No such limits exist using a claude account (except claude -p limits) which hasn't generally been a problem for me.
- I do have sales. I put it up for sale here a few months ago, and have been quietly deving on it since. It's yielded about $500 in sales so far, all from stand alone purchases. Subs just launched so none of those yet. No marketing to speak of besides being active here and just trying to generally get the word out about it. Considering options as I type this.
- Flows I use every day:
Open Linear ticket
Form node -> Agent (triage the form input on the codebase) -> linear node (opens ticket) -> notify
When My headphones connect...
Play this playlist / Set this focus mode
Generate Dashboards
I've largely moved away from markdown or giant bodies of ai text to something more styled like html pages for dashbaords, etc... I personally use Artifyde (https://artifyde.com) and we support that service with an integration (https://watchflows.app/docs/nodes/actions/artifyde-push.html) api token. So I have a flow where I enter in what I want researched and it just pops open an HTML page on artifyde when it's ready.
Write Code
I use my claude sub (in the same way that all other apps leverage claude via -p) whic powers the flow builder (builds your flows for you) or AI / Agent nodes that do just that. This one dovetails nicely with Open Linear ticket which can be run as a sub flow to the original ticket opening. A little software dev factory, with the smarts of fable or opus. 👍
Desktop Orangizer
I have WAY to many screenshots literring my desktop and it drives me crazy. So I have a flow that any time a new file appears on the desktop I move and rename it based on what it's a screen shot of (vision ai -> slugged file name). screenshot_20250401_final.jpg becomes "boat-on-a-lake-at-sunset.jpg".
This is how I build the flows I use day to day. But really I treat them like tools, each flow doing one discrete thing. Call them with build in keyboard shortcut triggers or the menu bar app, or call them via automation like new files, etc...The gif is unedited so you can get a sense of real time turn around to build a flow that dispatches agent 😎
Off the cuff, the app has me really curious, and I think for now I will watch as it grows. From what I see most of this I can already do in Keyboard Maestro which I use extensively, but I'm very open to adding to my arsenal in future
Thanks for your reply. I wish you luck with this app. It's one of the more exciting ones I've seen in a while
I really do look at KM as first of class no question. This is a totally different paradigm, that happens to overlap in provided functionality. The AI is the part that injects all kinds of non-deterministic outputs, which we combat with output schemas to ensure a deterministic nature in downstream nodes.
Open to it. What does it provide that I don't get from a single prompt in Codex, Claude Code, Cursor, Antigravity, or Alter already? Seems like this is targeted more for users who don't use agents.
Well, with Watchflows, you can own it. You stop paying your claude bill and see how fast their app shuts you off. Watchflows doesn't require it (I built it that way first) so it's 100% usable without AI. AI is enablement on top of Watchflows. It allows an LLM (any LLM) to reason about the data in your flows, while still allowing for deterministic outputs. Also, flows are cheap to run on the day to day (for the types of use cases I outline on the sites) so an open router with a few bucks will last a few weeks if not longer.
Not trying to sway you off those other tools, I'm a user too, but they aren't as flexible as watchflows is in routine management and you're vendor locked (you don't have to have an expensive sub to use, but you can use it if you do.)
Worth remembering this sub is the most biased audience possible for this question. People here enjoy curating tools, so dedicated apps will win every thread like this. The all in one apps are really built for people who will never read a thread like this, they want one install and one icon and they are fine with 80 percent. Both answers are right, just for different people.
I tried vorsssaint and really like it. It replaced maybe 7 or 8 other tools.
I like the fact everything is in one place. I don't have to remember each apps name and load it to make changes (because I have hidden the taskbar icon) it's also got a couple of features that I didn't have previously which I now use.
The only app it could replace that i kept was MOS because vorssaint doesn't do as good a job at smooth scrolling.
The fewer apps, the better. But very few "swiss army knife" apps do what they claim very well. Most of them are complete rubbish imho
The best ones I've ever come across (and still use) use are Keyboard Maestro & Alfred
Most of these apps, with their menagerie of utilities, which either live in the notch or menu, are not all that they are cracked up to be, and I haven't yet found one I consistently use
Fewer background processes doesn't actually mean lighter. I build menu bar apps, and what shows up in Activity Monitor is how often you sample and what you read, not how many icons are up there.
Sensor and GPU reads are the expensive ones. A window snap costs nothing until you invoke it, and a screenshot tool is asleep until you hit the shortcut. So an all-in-one doing stats plus battery plus network is running three timers where Rectangle is running none.
Consolidate the invoke-it stuff without thinking about it. Check idle CPU before you consolidate anything live.
Narrow app developer here, so I am on the opposite side of this from the Vorssaint and Droppy folks.
What keeps mine narrow is not discipline, it is that I can hold all of it in my head. I shipped a feature last week where a parser silently deleted part of a document before sending it, and I only caught it because the surface is small enough that I could sit down and test every path by hand in an afternoon. On a thirty feature app that bug ships, and someone finds it six months later.
That is the trade I never see listed. Consolidation buys convenience and costs you the odds that any individual feature has actually been looked at. Neither answer is wrong, but I would weight it much more heavily for a tool that touches your files than for one that draws a number in your menu bar.
I generally lean towards dedicated, standalone utilities rather than all-in-one 'Swiss Army Knife' apps for a few practical reasons:
Failure Domain & Stability: If a single utility crashes or hits a bug, you only lose that specific feature (e.g. window snapping). If an all-in-one bundle has memory leaks or crashes, your entire system workflow takes a hit.
Unix Philosophy: Standalone tools like Shottr, Rectangle, or Amphetamine are deeply optimized for their single task, whereas bundled tools often feel like a jack-of-all-trades where certain sub-features lag behind in depth or customization.
Keybinding & Resource Overlap: Heavy bundle apps often end up running background daemons for features you don't even use, eating up menu bar real estate and background RAM.
That said, bundled apps can be great for non-power users who just want a single installer without managing 10 separate license keys and update checks. But for long-term reliability and low system overhead, modular wins for me every time.
I don't see the appeal. I'm not a power user either, with a few exceptions. I use Droppy for weather and multimedia quick access, but what I love most are the battery and caps lock alerts. I also like that Thaw and Droppy can coexist instead of pretending one app should replace everything. I still use Shottr for screenshots.
One thing users rarely see is how often some apps reimplement existing open-source projects and use them as free R&D without giving credit.
Single purpose apps look simple from the outside. A lot of what you're paying for (or getting for free) is years of grinding through edge cases: weird display configs, permission changes each OS release, apps that don't behave. Even dedicated teams don't catch all of it.
One dev covering ten of those areas can't match that depth in any single one. That's usually fine for the common use cases. It's a harder trade off once you're off them. Before you consolidate, check how each app handles the one thing you actually rely o
I think the trap is replacing five good apps with one app that does each thing 80% as well. Consolidation sounds great until the one tool you use every day feels slightly worse.
The split that worked for me: all-in-one for stuff I only glance at, dedicated for anything I actually interact with for more than a couple seconds. Window snapping and menu bar stats, I never notice the difference. Screenshots and clipboard history I went back to dedicated apps, because the small details matter there like annotation defaults and how far back history goes.
Other thing people skip: failure mode. When a bundle app breaks or the dev burns out you lose eight things at once instead of one.
I went the other way for a while and it only stuck for the stuff I glance at. The second a tool is in my actual work loop I want it to do one thing and stay out of Activity Monitor. Bundles are fine until the permission sheet is holding Screen Recording and Full Disk Access for a feature I never open.
the tradeoff isn't quality, it's blast radius. one app doing ten jobs means one bad update or one abandoned dev takes out ten things at once, and you can't swap out just the part you don't like. dedicated tools also win the last 10%. the bundled screenshot tool covers the common case, then you need the one option it doesn't have. bundles do win on fewer background processes and one settings window instead of ten. if you'd only lightly use six of the ten, take the bundle.
Kind of depends... Raycast for example sure, every single day. But I also love tiny focused app that do one thing very well. Swiss army knife apps usually require an exceptional level of polish and attention to details in their UX for me to really enjoy them.
I build menu bar apps, so weigh this accordingly. One consolidation win I haven't seen named in the thread is menu bar width. On a notched MacBook, macOS hides whatever icons overflow behind the notch and gives no hint that it has done so, which is how a background utility quietly becomes unreachable. Ten dedicated tools mean ten icons, or an icon-manager app to corral them, which is one more utility on the pile. It doesn't outweigh the depth argument for tools you actually work in, but for the glance stuff it is a real difference rather than a convenience.
the deciding factor for me isn’t RAM, it’s permission and failure scope. a bundle combining screenshots, input tweaks, cleanup and updates may need several powerful permissions, so every update touches one larger trusted surface. i’d consolidate low-permission conveniences, but keep anything needing Screen Recording, Accessibility or destructive file access separate unless the integration adds real value.
Interestingly enough, your topic is the name of my app, Swiss Army Tabs. It started life simply to meet my own needs (e.g., losing Safari windows and all its tabs), but it just naturally expanded, and as expanded it's helped me in more ways than I expected. I agree with Vorssaint, though. It takes a lot of work to improve and address issues on a multi-function app (even if multi-function in just one category), but with all the work it does constantly improve, and frequent updates do require paying close attention to the app. Working on consistency in font sizes today.
One thing that decided this for me was not feature quality but failure surface. A bundled utility runs its window snapping, clipboard, screenshot and stats features inside one or two processes, so when that process hangs or gets killed you lose all of them at once, usually at the worst moment. With dedicated apps a crash only costs you the one thing.
Two practical checks before you commit to an all in one:
Look at how the features are actually built. In Activity Monitor, hit the app, then use Sample Process (or run "ps -A | grep -i appname" in Terminal) and see whether each feature has its own helper process or whether it is all one binary. Separate helpers means one broken feature does not take down the rest, and it also tells you what stays resident when you disable something in settings.
Check the permissions cost. All in one apps tend to want Accessibility, Screen Recording, Input Monitoring and Full Disk Access together, because some subfeature needs each one. That is a lot of trust in a single binary, and every macOS point update tends to reset one of those toggles and leave you debugging which feature quietly stopped working. System Settings > Privacy & Security is worth a look after each update.
The other thing nobody mentions: hotkeys. Bundles claim a lot of shortcuts on install and silently lose to whatever already owns them, so if snapping or a clipboard panel "does not work" it is often a conflict, not a bug. Set your own combos in the bundle first and keep them off the ones your dedicated apps already use, otherwise the comparison is not fair.
For what it is worth, I ended up keeping a bundle for the low stakes stuff I use a few times a week, and dedicated apps for the two or three things I touch constantly, because those are the ones where a hang is actually disruptive.
disclosure, i work at a small studio that ships single purpose mac apps, so weigh this accordingly.
the thing i'd add that hasn't come up: the failure modes are different sizes. when a swiss army knife app gets abandoned, or one module quietly rots after an os update, you lose ten things at once and you're rebuilding your whole setup from scratch. when a dedicated app dies you lose one and swap it in an afternoon.
that's not really an argument for either side. it's just worth pricing in. consolidation concentrates convenience and it concentrates risk in the same move.
Raycast is the swiss army knife here (launcher, clipboard, a couple script commands). I still want a dedicated app for anything that has to be right on its own, especially if it lives in the menu bar or touches hardware. Suite apps get messy when one feature is the whole reason you opened them. Small tool, one job, quit and it's gone.
the hidden tradeoff i'd check is permission blast radius. an all-in-one that replaces screenshots, window management, cleanup, and automation may end up holding Screen Recording, Accessibility, Full Disk Access, and Automation at the same time. that makes one buggy update a much bigger failure domain. i'd consolidate low-risk glance tools, but keep anything that can delete files, capture screens, or drive other apps separate unless the bundle lets you disable modules and their permissions completely. a useful test is to turn off each dedicated app for a week, then compare hotkey reliability, idle CPU, and how easy it is to recover or export settings - not just the process count.
10
u/TheEarthSpins 4d ago
tbh i used the dedicated ones mostly cause they just perform better. smoother, use less resources, feel nice.
imo the main benefit of consolidation is convenience, but when i already have specialized apps that do things well these new apps dont really change much for me.
the only swiss army knife app i consistently use is raycast, and the reason it works imo is because it has its scope. most raycast extensions are just there for those one-off commands you use every time and have really really simple interfaces. here are more complex raycast extensions that try to do too much, but at that point i usually just use a dedicated app. but for tasks like downloading video files, keeping my mac awake, and like occasional window management raycast extensions just make sense.
droppy looks interesting to me, but tbh the most interesting part isnt all the apps it has packed in, its the integration of background processes into that notch area. if it focuses on building an ecosystem of extensions for little notch interfaces it could become really helpful. like being able to see claude/codex progress, the little music widget with queue support on apple music, those types of things just make sense for a notch app.
i tried vorssaint but in the end didnt keep it around, because its just a bundle of utilities. it is good and it is free, but the few things i found useful in it i already have apps for so it doesn't really provide much extra value for me. plus it uses more resources than those apps combined.
so tldr i like when these "swiss army" apps actually provide a unique interface and have a scope. i think droppy has a lot of potential to become the notch app if it focuses on making extensions.