The new modern activities often don’t make sense. First off, the Use App/Browser makes it more difficult - instead of easier - to use variables to reference the object. Variable use is best practice, not re-grabbing the object with selectors every time.
Another example is the Click activity. If it has its own properties to store selectors, why must it be inside a Use Application/Browser scope? Why can’t we use it standalone like the old Click activity? I’m seeing this a lot of places, now, where things have been made more complicated not simpler.
When I use a Click activity inside a Use App/Browser scope, the Click activity still gets its own window selector. Why? It should be using the scope. So every time I add a Click activity I have to remember to fix the selector or delete it, when the selector shouldn’t be filled in at all.
Then I try to use Click as an image click, but the easy way to specify an offset (with the recorder) is gone. The old Click Image activity was better than the new combined Click activity.
It is starting to feel like when you’re deciding on these kind of changes you don’t get feedback from people like me who do this all day every day. This has always been a huge problem in the software industry - product managers and programmers who don’t actually know the experience of their users.