I have been creating custom browser automations for over a decade now. Using Browseract was the first time that I almost created a full working (real use) browser automation on first attempt. I created the full workflow, ran it - hit one issue (I messed up one selector description), fixed it and ran again. I was shocked that it worked haha, only needing one run to debug is completely unheard of for me.

It didn't need any further modifications afterwards either. Normally I need to spend a lot of time debugging and improving resilience. This was without checking any documentation or tutorials, just the tooltips in the main UI.

This was not a super basic automation also, it was for something that specifically tries to prevent automation. Using frequent page randomisation (layout, selectors, buttons, colours, label text etc. all change on basically every run), traverses two pages and also has the industry standard obnoxious captcha, set at the highest difficulty level.

One confusion was that I didn't know how to add a conditional wait step, as I'm used to needing them for a substantial amount of actions. Turns out, Browseract just handles that automatically too, which I also have never seen before. This simplifies things a lot and minimises the amount of logic needed substantially.