Appium Reviews

Our company uses the solution's library to test and automate mobile devices including Android and iOS. 

The solution provides one roof or framework for both iOS and Android code bases. 

The library is extensive so the driver interacts with most functions or actions on mobile devices such as tap, swipe up, write down, touch actions, and opening or closing sessions. 

The solution needs to support more actions such as locking a phone or adding a fingerprint. 

Some action methods have been combined to one touch action but this should revert back for easier customization. 

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

Some actions are not supported across languages such as JavaScript, Python, and C# so documentation, examples, and boilerplates are needed. 

I have been using the solution for seven years.

The solution is stable. 

The solution is not designed for scalability but can be scaled via cloud services or a local device farm. 

We currently have two users but may add more in the future. 

The solution is open source so does not offer technical support. 

If you have issues, you can Google answers or ask developers direct questions through their repository. Forums are also available for support. 

I have used multiple automation frameworks including Nightwatch.js but most were integrated with the solution's libraries. 

The setup is a bit complex for use with iOS. 

Even Android setups require a couple of steps that need to be completed each time. 

We implemented the solution in-house and it only took a few minutes.  

The solution is an open source library so just needs to be added to the package list. Anyone can install it on their system which also happens in your CI/CD. 

The solution is open source so it is free. 

Almost 80% of the market uses the solution and we did not evaluate other options. 

The solution is a fit when you need both iOS and Android frameworks because it combines them under one roof.

If you only test on a specific platform, you can use base libraries or drivers. For example iOS works on XCUI drivers and Android works on UiAutomator. 

The solution is the go-to library right now with few alternatives. 

I rate the solution a seven out of ten. 

We use Appium to test our native applications for iOS and Android. The solution is deployed locally and integrated into our instance of GitHub Actions for CI/CD functionality, so it's a hybrid deployment. 

Using Appium with React Native allows us to reuse our tests for both Android and iOS. If we had to use one tool for Android and another for iOS, we would need two repositories, two tests, and a lot more coding for us to do. I think React Native is the only real solution available nowadays for black box testing the way we prefer to do it.

We develop apps using the React Native framework, and Appium integrates well for testing those apps. The Appium automation framework also has good integration with GitHub Actions and plenty of other tools and frameworks, including BrowserStack. 

Appium also offers plenty of testing interactions, including swipes and other actions. It provides more interactions compared to other solutions like Selenium HQ, which is another tool we work with.

Appium Inspector is another excellent feature that provides us with a lot of information when dealing with app elements. One of our uses for this is determining which selectors are faster, as we want our apps to be as fast as possible. 

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.

Appium doesn't recognize IDs placed by our developers on nested elements when we use React Native for iOS; it just sees the whole page and one element. We use coordinates to get around this, but it isn't the best system, and nobody in the community has been able to help us.

iOS is also strict in general when it comes to signatures and developer accounts, which creates additional headaches for iOS testing compared to Android. It would be great to see a more streamlined setup for iOS, but that might be more of an Apple issue than an Appium one. 

We have been using the solution for about four years. 

The solution is relatively stable, but sometimes tests can become flaky. This could be because of Appium, or due to a cloud-related issue, it isn't exactly clear. It's more stable than it was four years ago, so the product has improved, but there is still room for better stability. 

The solution is scalable. Once it's installed on the machines or in the cloud, everyone can run it and I don't think it matters how many staff members use it. We have nine end users in our organization. 

Appium is an open-source solution so there isn't a number to call for technical support. However, there is a large user community, so it's easy to find help for issues. 

The initial setup is very straightforward; it's just a download with a desktop installation. Setup time depends on your internet, but I would say it takes minutes.

Appium is open source; we can use it for free.

We looked at Espresso and XCUITest, which are native testing apps for Android and iOS, respectively, but we can't use those for both in React Native. We carried out a POC for Appium, and there were no viable alternatives. It allows us to use one tool and one repository for both mobile operating systems.

I would rate the solution eight out of ten. 

Appium is a great tool, and I recommend it. Working with iOS requires patience, and setup can be somewhat demanding, but there are no such problems with Android. Overall, the solution does what we need it to do.

Our use case for Appium is writing end-to-end tests for mobile applications. We also use it for some data extraction for an end-to-end user desk.

For the particular use case we used Appium for, we felt that it served our purpose completely, and we haven't had any issues with the Python Client for Appium. Appium has been a good solution for us.

I haven't explored other solutions in this particular area, but what I like best about Appium is the fact that it shares functions with Selenium. The extension of Selenium functions allows me to use all of the methods that exist in that domain, and it just makes it simpler for me. I've been using Selenium for some time as well, so using Appium just seems like a natural fit for me.

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've been using Appium for almost two and a half years now.

Appium is stable so far, performance-wise. I never had any performance issues with Appium scripts, and I could potentially do as many Appium programs as I want, and I'd only be limited by the compute capacity of the particular machine that I'm running it on, so no issues there.

Appium has decent scalability, and I've primarily used the Appium-Python-Client. What the Appium team could look into would be the possibility of running Appium in a cluster because currently, there's not a lot of in-depth documentation on how to do it.

For example, the way Selenium Hub works with Kubernetes, if Appium can have that functionality of working with Kubernetes, then that would ensure the greatest scalability for Appium.

I've never had to reach out to the Appium technical support team. I'm not even aware of the support channels for Appium, but I haven't had to reach out ever.

I wasn't sure of what other solutions existed out there. I just came across Appium, and I thought that Appium suits my use case, and it's open source, so that helps.

The initial setup for Appium wasn't as straightforward. I was an individual contributor that pitched this idea to my organization about using Appium, and I was solely responsible for researching it, writing code, then deploying it. It wasn't too straightforward, but in the end, I was able to get it done.

I did the deployment of Appium all by myself.

There were implicit monetary benefits that have come from our use of Appium, so ROI wasn't explicit. We got cost savings, reductions in downtime, stability, etc., from using Appium, which translates to ROI.

I'm unsure if there's any cost associated with Appium. I got the free package which includes the server GUI application and the inspector application, and it was free to download, and that's all I need to get my work done.

I'm not aware of any additional costs associated with the tool. Essentially, if you want to run Appium in a production environment, you'll need to hook it up with an emulation service, and though that's outside the scope, that has to tie and deliver the entire solution.

I'm using the Appium-Python-Client version 2.1.2.

In my company, between four to five people use Appium.

The number of people required to maintain Appium depends on the number of tests you've written. In my company, a single person can maintain it.

Right now, Appium is being used pretty extensively within the company. My team runs and tests four to five different applications, and that list will be extended, so usage of Appium will go up in the future. It's not going to go down.

The advice I would give to anyone on Appium for the first time is to look into the underlying automation, for example, the UIAutomator for testing. I would urge you to also look into the different functionalities offered by the base automation and essentially use those features provided by the base automation within that context because that's going to give you the biggest branch of data.

My rating for Appium is seven out of ten, based on the work I'm doing on it.

My company is a customer of Appium.

We primarily use the solution for UI validation of mobile applications. It's a mobile development platform. We have an application where we have to test the front end and how it is cloning.

It's easy to connect the product. Within a single command, we can easily connect to the device. The connectivity is just that easy.

We get a list that shows all devices that are connected to the system.

It is a very easy initial setup.

Support-wise, it could be better. Whenever we get some issues, it may take some time. I'd like them to be more responsive. 

There's not too much public documentation or information. If we Google information or something else regarding the Appium, there won't be much compared to Selenium. Selenium is also open-source. Appium details are limited.

It is difficult to understand. Recently, there were major changes in Appium. Understanding those changes, was a bit difficult. There just wasn't enough transparency.

I've been using the solution for one and a half years. 

The solution is pretty stable. That said, either from the application side or the Appium side, sometimes, I get some error that is not correct. Even if the application is open, sometimes it throws some error, however, maybe it is from the emulator side. I'm not sure. 

If I run the same test case, and in the same execution, I don't see that error again. It's random, yet may be from our side. I don't think it's from Appium. However, I'm not sure. 

The solution is scalable. The capacity is very good. 

We have three QAs using the product.

Technical support is not as responsive as we would like them to be. They often are late to reply. Sometimes to topic diverts towards something else. It's open-source, which means support is always a bit of an issue. 

Neutral

We also have used Selenium, which has more information available. Selenium is also open-source. Both are pretty similar. 

The solution is very easy to set up. It's not an issue at all. It took one or two days to connect the emulators. It was pretty simple and straightforward. 

I'd rate the initial setup at a five out of five in terms of ease of deployment. 

This is an open-source tool.

We are end-users. We tend to use the solution on a weekly basis.

I'd rate the solution at an eight out of ten. 

I'm using Appium for the automation of applications on Android and iOS.

Appium has improved my company because it makes it easier to connect devices to automation scripts because the library is easy to use. You can also detect mobile elements faster in both Android and iOS.

The best feature of Appium is that it allows you to inspect the element. With the Appium Inspector, you don't have to install another application to do the inspection. I also like that Appium has Android device connectivity. Currently, most people use Appium as automation software, and I haven't found any other tool that's more powerful than Appium.

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.

I've been using Appium for more than four years.

Appium is a solution that's quite stable.

Appium is a scalable solution. A lot of devices are connected to Appium, and the solution runs every day for integration testing, with new test cases added daily. Appium keeps growing, and it's scalable.

A separate team works with the Appium technical support team whenever there's an issue, so I have no experience contacting support.

I've only used Appium, and I haven't found a solution that's as good as Appium.

Setting up Appium is quite easy because a lot of documentation can be found on the internet. From setup to deployment, it only takes less than one hour if there's no problem, but usually, the problem is on the environment side, not in Appium itself. Sometimes the emulator doesn't connect to Appium, and sometimes there's a broken dependency, for example, Node.js isn't supported, or a certain percentage of Node.js must be used.

As far as I know, Appium is a free solution. It's not for commercial use.

I'm using the latest version of Appium.

My current company has a lot of programmers, so I don't have the exact figure on how many people use Appium, but in my previous company, two people deployed the solution on the cloud server.

The only time maintenance is required in Appium is when there's a new update, and my team would first ask about how stable the new version is, then that's the time the team upgrades the version of Appium.

In the AP department, seventy to eighty people use the solution. The users only create the automation path and then test it on the local machines with Appium, then deploy it on the cloud server. The AP users aren't in charge of maintaining Appium.

I'd recommend the solution to other users. Most of the companies here in Indonesia use Appium, and on a scale of one to ten, my rating for Appium is nine out of ten.

My company is a customer of Appium.

It's normally used to test mobile applications, and to interact with some power applications. It's mainly for mobile testing applications?

I like the app inspector. It's quite a good and useful tool for us. I like that we can use it almost out of the box. 

It works well on Android. 

The solution is stable.

It's very scalable. 

The solution is free to use. 

I'm facing a lot of issues with my new juniors when they set up Appium for iOS. For Android, it's easy, however, for iOS to interact with it on iPhones or something. It requires some additional libraries and some additional installation. Sometimes it's not working. While Android works well, iOS continues to be an issue. 

There are a lot of issues on GitHub discussions and Stack Overflow, et cetera, and it's still not resolved. When we use Appium Inspector and just Appium, we are not able to inspect nest elements. Half of the elements are nested. Especially for React Native, it's not visible in Inspector, and we cannot interact with this element. We need some bug fixes for nested elements. 

We'd like a one-button click where you hit it, and everything is automatically installed. 

I've used the solution for three or four years, maybe less. 

Generally, I'm not facing any issues with stability, so I am quite satisfied. There are no bugs or glitches. It doesn't crash or freeze. 

I'm not facing any issues with scalability. It's not a problem to expand. 

We have a team of ten using the solution right now. We use it on a daily basis. We have daily test runs, using Appium, and have test cases to update, to add on a daily basis.

We have zero direct interactions with Appium. If we need help with something, we just use some resources from the internet or some documentation. Aside from eh issues we've had with nested elements, this has always been enough for troubleshooting. 

I have no experience using other automation tools for our devices. We only use Appium.

It's not difficult to set up and deploy. However, it does take time. We use Macbooks. We don't use Windows. It's more complicated to set up on iOS than on Windows. It can take two to four hours to configure everything once you have it deployed. For example, if you have ten devices, the time is two to four hours each, so it can take a while. 

I'd rate the solution two or three out of five in terms of ease of deployment. 

This is a free tool. 

Based on the issues we've had, I'd rate the solution six out of ten. 

We use Appium mainly for mobile test automation, while Selenium doesn't support mobile testing. In my personal use of the tool, I primarily convert manual test cases into automated test cases. We also link our test cases between Selenium and Appium with cases from Jira

The solution helps with test automation. We focus mostly on Java.   

One area where I think Appium could improve is in addressing security concerns for our data. Currently, we're unable to use cloud solutions like CloudForm due to security restrictions on our servers. We also face challenges in updating packages for the same reason. It would be beneficial if the solution could provide better support for auto-reporting and easier connections to mobile device farms.

I have been working with the product for six months. 

I rate the product's stability as six out of ten. 

I rate the solution's scalability a four out of ten. 

The solution's deployment is not simple.  

The solution is open-source. 

I rate Appium a seven out of ten. 

Appium helps me to do as much as much as I want to. 

The tool needs to add a dependency manager. 

I have been using the product for three to four years. 

I rate the tool's stability an eight out of ten. 

I rate Appium's scalability an eight out of ten. My company has five users. 

Appium's deployment is straightforward. 

I rate Appium an eight out of ten.