Appium pros and cons

What needs improvement in Appium is its documentation. It needs to give more context on the libraries that Appium is using under the hood. For example, my team is using Appium for Android automation, and a lot of times, I feel that there's functionality that's available through the Appium interface, that exists within the UIAutomator, but there aren't a lot of useful or helpful resources on the internet to find that information, so it would be good to have some linkage with the underlying platform itself. Another room for improvement in Appium is that it's buggy sometimes. For example, at times, there's a bug in the inspector application that doesn't allow me to save my desired capability set, so it would be nice to get that bug fixed, but overall, Appium is a good tool. The Touch Actions functionality in Appium also needs improvement. For example, if I want to initiate a scroll on the device that I'm running Appium on, sometimes Swipe works, but in other situations, I have to explicitly use action chains, so I'm not too sure what's the better approach. What I'd like to see in the next version of Appium is a more intelligent and more intuitive AppiumLibrary, in terms of identifying menus and scroll bars, etc., because right now, I'm unsure if I have to do a lot of export reversals to get to the elements I'm looking for. It would be nice to have some functionality built in, which would allow me to easily get those exports.

I rarely use Appium nowadays because I'm now at the managerial level, but the last time I used it, whenever I selected and clicked on an element, Appium was very slow. I tried to debug it, but I still couldn't find the problem, so this is an area for improvement in the solution. Another area for improvement lies with the connector and server. For example, the effort to get into the local machine sometimes causes the emulator to become slow, which then leads to failure in testing, and this is the usual issue I've encountered from Appium. An additional feature I'd like added to Appium in its next release is being able to do automation in iOS without using XPath and the name of the element. In Xcode, you can use previous UI tests for detecting elements, but in Appium, you have to use Xpath and the element name instead of being able to directly put the X-UiPath, which is what you can do in Xcode. In iOS as well, sometimes the element doesn't have a name or a path. Sometimes, there's also no element.

We previously worked with native applications, and there weren't any good mobile app testing tools. We started working with React Native, which works well with Appium, but it would be good to see better integration; the way elements are displayed can be messy. React Native is very popular nowadays, so it's essential to have that compatibility.

One thing which can be really helpful is that there is some kind of a recorder made available rather than scripting everything.

The challenging part with Appium is that installation can be a bit tricky. It can be challenging to set up in Android versus iOS environments.

Image recognition could be improved. We have some images in our mobile applications. It should be able to run from the cloud, so we can automate the catcher.

We need some bug fixes for nested elements.

Support-wise, it could be better.

The user interface needs improvement because there are issues when setting up environment variables.

The setup and installation were a problem for us at first.