3 ms·

For web automation Selenium IDE is easier and more robust than UIPath. And for Windows automation in general there are many tools like e. g. AHK, Sikuli or UI.

For web automation Selenium IDE is easier and more robust than UIPath. And for Windows automation in general there are many tools like e. g. AHK, Sikuli or UI.Vision that combine Selenium features with RPA features. And they are free, open-source or at least very low cost compared to UIPath.

ethbr0 6y ago
AHK [0], Sikuli [1] , and Ui.Vision [2] are extremely limited vs what a proper RPA framework will give you for Windows automation. If your needs are minimal (e.g. test automation, because you don't care if it breaks 10% of the time), that's probably enough. But they're definitely not the same class of tools. [0] https://www.autohotkey.com/docs/commands/Control.htm https://www.autohotkey.com/docs/commands/Control.htm [1] http://doc.sikuli.org/match.html#Match http://doc.sikuli.org/match.html#Match [2] https://ui.vision/rpa/x/desktop-automation https://ui.vision/rpa/x/desktop-automation
- eastendguy 6y ago
  I have used all three and none of them "breaks 10% of the time". Why would it? Of course, these tools are more lightweight and lack the advanced scheduling, monitoring and robot distribution features ("Orchestrator") that UIPath offers. But if one needs only straightforward task and test automation they are a good and reliable alternative.
  - ethbr0 6y ago
    Among other things: Citrix remote app compression, resolution changes, screen magnifier software for users with disabilities, lock screens. These are all things I've had break visual matching in prod deployments. The scheduling, monitoring, and distribution are (IMHO) the least interesting parts of UiPath. They're pretty trivial to build with other tech. But a matching engine that offers a plethora of high level rule options, coupled with deep inspection capability, and fast runtime matching? That's a pretty big building block.

3 ms·

For web automation Selenium IDE is easier and more robust than UIPath. And for Windows automation in general there are many tools like e. g. AHK, Sikuli or UI.

by eastendguy 6y ago

ethbr0 6y ago
AHK [0], Sikuli [1] , and Ui.Vision [2] are extremely limited vs what a proper RPA framework will give you for Windows automation. If your needs are minimal (e.g. test automation, because you don't care if it breaks 10% of the time), that's probably enough. But they're definitely not the same class of tools. [0] https://www.autohotkey.com/docs/commands/Control.htm https://www.autohotkey.com/docs/commands/Control.htm [1] http://doc.sikuli.org/match.html#Match http://doc.sikuli.org/match.html#Match [2] https://ui.vision/rpa/x/desktop-automation https://ui.vision/rpa/x/desktop-automation
- eastendguy 6y ago
  I have used all three and none of them "breaks 10% of the time". Why would it? Of course, these tools are more lightweight and lack the advanced scheduling, monitoring and robot distribution features ("Orchestrator") that UIPath offers. But if one needs only straightforward task and test automation they are a good and reliable alternative.
  - ethbr0 6y ago
    Among other things: Citrix remote app compression, resolution changes, screen magnifier software for users with disabilities, lock screens. These are all things I've had break visual matching in prod deployments. The scheduling, monitoring, and distribution are (IMHO) the least interesting parts of UiPath. They're pretty trivial to build with other tech. But a matching engine that offers a plethora of high level rule options, coupled with deep inspection capability, and fast runtime matching? That's a pretty big building block.