I rate Appium nine out of 10. It's one of the most stable solutions for mobile automation. It inherited a lot of functionality from Selenium, a popular tool for automation. We can write advanced code and achieve every mobile app channel using Appium. 

If you want to use Appium faster, you need to do things right during installation.  We should be aware of the programming language. We need to use some framework to make our life easier while using Appium.

I would suggest checking whether you have knowledge of the programming language. You must also understand the flow, the architecture, and how the application that you're going to test will behave, whether it's a native application, hybrid application, or web-based application. Then, based on the nature of the application and the technical expertise you can decide whether to use Appium.

You have to be very careful while doing the installation. There are about 40 to 45 steps involved in the set up of Appium for Android devices and approximately 60 to 65 steps for iOS devices.

Data transformation can be tricky, but transferring of the controls is very easy. Predefined tools and methods are available, and you can import those libraries and use them as per your requirements.

Overall, I would give Appium an eight out of ten.

The solution is easy to use. If you have resources available for Java and are looking for free tools, then you should go for Appium. But you should evaluate some other tools as well. Also, if you have experience with selenium, you must prefer Appium, as 95% of selenium libraries are similar.

I rate the solution as a nine.

My advice to others is they should use the solution if they have experiences in any technical language, such as Java and C#.

I rate Appium a nine out of ten.

We're just end-users. 

I'm not sure which version of the solution we're using. Typically, we go with the latest update.

We deploy both on the cloud and on-premises. We use it for some of our cloud-based solutions, however, it's primarily on-premise where we integrate various devices and we do the end-to-end testing.

It's good to start with a very stable framework, so that will enhance the reusability that will reduce the maintenance down the line or other that will reduce the ease of maintenance down the line.

I'd rate the solution eight out of ten. With it being open-source, and de to the lack of the cost, it's a critical factor for many of our customers and that's the bread and butter for service provider automation. We have some skilled resources we can take care of it. 

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

I rate the solution a seven out of ten. 

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.

I would rate Appium a nine out of ten.

I give the solution eight out of ten.

There are a lot of helpful documents available online if you require support with the solution.

When it comes to mobile automation, I recommend this solution because of its performance, and scalability over the competition.

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. 

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

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.

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.

My advice to others is they should have Java installed on their system initially, then later Node should be set up. They will possibly need iOS or maybe Windows installed, but this depends on their use case. The Appium license should be given by your team member for the tool on your system.

I would recommend this solution to others.

I rate Appium a ten out of ten.

This is the best test automation tool for any mobile test automation engineer.

I rate Appium an eight out of ten. 

I would rate this solution 8 out of 10. 

There are lots of newer tools on the markets that make testing easier. My advice is to look at alternatives, not necessarily alternatives to Appium, but at least alternatives to generating Appium scripts.

I would say start lean, gain small wins and incrementally add more. Example: Start automating test cases for one browser and slow expand to multiple browsers.

We are a customer and an end-user.

I’m not sure of the exact version of the solution. It’s likely the latest.

I’d recommend the solution to others. I rate it seven out of ten.

Appium, Appium Studio, and Appium Inspector are from the same product family.

Appium is the biggest user base that we have today in terms of open-source. It's not difficult to find a solution when we talk about the maintenance of the scripts.

If you are looking for fast scripting and self-healing features, there are other solutions available that you have to pay for.

I would definitely recommend it in cases where you are using integration automation, you have a relaxed timeline, and stability is the main factor.

I would rate Appium an eight out of ten.

Overall, Appium is the best. It is not made as a commercial tool.

I would rate Appium as a nine out of 10 because it has the flexibility, simplicity, and it is elegant. It is technically more advanced, and even a beginner can start using Appium very quickly, and master it in less time.

This solution is one that you need a little bit of time and patience to learn, but once you learn it, it opens the gate to work on many other similar types of tools or wrappers that are created, keeping Selenium at the core. 

Overall, the product is good. On a scale of one to ten, I am only deducting two points because you cannot automate & run the iOS application on the Windows OS. You require Mac machines for iOS automation. Also, installation and configuration are also tedious for new users.

I would rate this solution eight out of ten.

I would give Appium a rating of seven out of ten.

Good luck, not sure how you can do it better. It has flaws, but is still much better than any other cross-platform mobile automation tool.

I would rate this solution an 8 out of 10.