When comparing Rofi vs Ulauncher, the Slant community recommends Rofi for most people. In the question“What are the best app launchers for UNIX-like systems?” Rofi is ranked 1st while Ulauncher is ranked 3rd. The most important reason people chose Rofi is:
e.g.: <code>run: st toxic</code> Runs a tox client in the terminal emulator "st". <code>run: maim ~/Images/screenshots</code> take a screenshot with "maim" and save it to given location.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Can run commands
e.g.:
<code>run: st toxic</code> Runs a tox client in the terminal emulator "st".
<code>run: maim ~/Images/screenshots</code> take a screenshot with "maim" and save it to given location.
Pro Minimalist design, yet can use customizable themes
Also it's easy to make use of your own "plugin" (scripts).
Pro Case insensitive
Instead of having to worry about case sensitive characters, you can use caps or lowercase wherever you please without causing any issues.
Pro Customisable
Pro Great keybindings
They seem to be emacs based.
Pro Resource efficient
Pro Simple
Pro No resource usage when you're not using it
Other launchers often run in the background to be prepared for showing the launcher. Rofi doesn't do this.
Pro Clipboard history extension
Greenclip adds clipboard manager functionality.
Pro Greatly maintained
Pro Easily switch windows without mouse
Pro Simple
Ulauncher comes with very reasonable defaults, looks good and just works.
Pro Fast
Pro Allows custom shortcuts
Pro Themeable
ULauncher supports themes and comes with a good supply on install but more can also be made.
Pro Supports fuzzy search
You can enter app name with a typo and Ulauncher will still be able to find it.
Pro Supports extensions in Python
With Ulauncher you can easily add and update third party extensions. From kill process to windows switching, many of them work very well. The extension API is documented and if you know Python you can create and share your own extensions.
Pro Actively maintained
Unlike Albert or others, it is actually being maintained.
Pro Good extension ecosystem
Pro Good look
Ulauncher looks modern & can be customized with many themes.
Pro Direct plugin install from GitHub
Can fork, customize, and install instantly.
Pro Extensions are really easy to write by yourself
Pro Quick search
Pro Able to launch Kdialog, Zenity and Bash scripts
Extensions are easily created. Python script is all open to see. Not compiled like some.
Cons
Con One of the most poorly documented launchers for new users
Challenge:
Install Rofi and google how to actually start or use it. Sure, there's plenty of Arch users screaming about dmenu, showing off editing of config files, integrating it with i3 or this or that, but how do we actually:
1) Start it.
2) Use it.
Rofi seemed intriguing, because it was ranked #1 on slant, but it may be better to use a third party dock in Xfce, because there's simply no resource on how to use Rofi for a complete newbie.
Con Lacks a default "blank slate" launch behavior
Unlike Ulauncher, Albert and similar launcher there's no generic "enable everything" launch behavior. You can configure Rofi to do almost this, but it's whitelist based, so you'd have to reconfigure it if you install or uninstall a plugin, and Rofi has to know if the plugin should be part of the combi mode or treated as an isolated mode.
Con Lacks conventions for plugins
Some other launchers have stricter plugin/extension APIs, making the plugin behavior more consistent.
For example plugins in Rofi respond to your choice differently (at least by default). Some output the result to stdout (like the calc mode) and others add the result to the clipboard (the emoji mode/plugin). And there's no API for plugins to add their own config option. They can check your CLI arguments, but that's not a perfect solution as different plugins could implement the same argument to mean different things.
Con Lacks keywords to switch between modes
You can switch between modes with ctrl+tab by default, but if you have a lot of modes this is slow.
Con Issues on Wayland
If you use Wayland, then Rofi may fail to grab keypresses or inputs, or may fail altogether. Works fine if you switch to X11.
Con Issues when Caps Lock is active
When typing with Caps Lock activated, it's impossible to use Backspace. Rofi eventually freezes in this scenario.
Con Extensions store is confusing, lots of redundant extensions.
There are dozens of extensions, which is good, but as an average user it is hard to find what you are looking for. It is unclear to me how updating plugins work.
Con Needs more posibilities for extensions
Currently, extensions can run only when you type their alias and <space>. There is no way to see results from multiple extensions at once. The output is also limited just to rows.
Con Does not easily fit into a customized desktop without full GTK3 CSD support
