I’ve been using UiPath on a Mac while learning and building different automations, and one thing I keep running into is that the experience can be quite different from what most tutorials/documentation assume.
A lot of UiPath content seems to be written around a Windows setup, so as a Mac user, sometimes I have to figure out an alternative way of doing something or understand whether a feature is simply not available in the same way.
I’m curious about other Mac users in the community:
- Which UiPath features have been the most difficult to use on Mac?
- Are there workflows where you eventually had to switch to Windows?
- Are there features you would particularly like UiPath to improve for Mac users?
I’d be interested to hear how others are dealing with this, especially people who use UiPath regularly rather than just experimenting with it.
Hi @anon41666530,
I agree that UiPath can feel quite different on Mac compared to Windows, especially when following tutorials that are mainly written for Windows.
From my experience, if you are working with Windows-specific applications, Excel automation, desktop UI automation, or some Studio activities, using a Windows VM or Windows machine can make things much easier.
For learning and building automations, a Windows environment is generally more convenient because most UiPath examples, activities, and troubleshooting guides are based on Windows.
It would be great if UiPath could provide more Mac-specific documentation and examples so Mac users don’t have to find workarounds themselves.
Hope other Mac users can also share their experience.
UiPath is primarily Windows-focused. When automation depends on Windows applications or Windows-specific activities, you would use a Windows environment rather than trying to force the workflow to run on Mac