My main use case for Genymotion Cloud involves running Appium test cases and CI/CD pipelines in Android devices, allowing me to avoid manually carrying physical devices. I am using Genymotion Cloud for running Android emulators and testing the builds for Appium test cases or CI/CD pipelines. Using Genymotion Cloud for my CI/CD pipelines and Appium test cases significantly helps my workflow compared to using physical devices, as I utilize test cases for checking automation testing for Android builds. I generate the builds using a CI/CD pipeline, automatically upload to Genymotion Cloud, open the emulator, and use that application to check if it's working fine or if there are any issues. When I need to check on specific configuration devices such as Samsung or Xiaomi, I can create those on Genymotion Cloud and verify that my application UI displays correctly on each device and configuration. I mostly use Genymotion Cloud for Appium test cases and CI/CD pipelines for development purposes, as it allows me to run builds without the need to carry physical devices. I simply go to Genymotion Cloud, create any device, and run my builds, testing on each device configuration, which is very helpful for testing and development purposes.
My main use case for Genymotion Cloud at my previous company was testing an enterprise reporting application across different variations of Android versions. Testing on different flavors was tricky until I discovered that Genymotion Cloud was quite easy to use. I started using Genymotion during my Android development around 2015 and was one of the early customers of the desktop version before transitioning to the cloud platform. A specific example of how I used Genymotion Cloud for my reporting application was that we did not have to purchase different high-end devices to test certain features. If I needed to test on a high-end phone, I could simply use a Genymotion device for that purpose. It was also easy to set up, especially with the wide range of Android phones available. With iOS, device options are limited by default since there are only a couple of brand devices, but Android has many variations across different vendors, making it really difficult to obtain those devices. This was particularly challenging for our QA team sitting in multiple locations, as we did not want to purchase numerous devices and distribute them to geographically dispersed QA members. With Genymotion Cloud, the solution was straightforward. We simply created a Genymotion Cloud account for every QA engineer and used it from there.
My main use case for Genymotion Cloud is to emulate user behavior in Android phones to perform automation that helps with business intelligence for identifying potential customers and getting information about similar products as ours that is being used. One of the workflows with Genymotion Cloud that I built is a pipeline wherein I use some of the toolings in Python programming to emulate the user behavior of navigating to the Play Store, installing applications, surfing the application, and getting the screenshots of individual pages so that I can automatically generate descriptions, reviews, and images, and use cases of various mobile applications. The main use case, the automation that I perform with Genymotion Cloud instances, allows me to gather data about various mobile applications in different categories and spaces and identify correlated applications to the data that I generate from Genymotion Cloud instances. This allows me to generate correlated data about various mobile applications in the same space or different spaces so that our business team can reach out to potential customers that might be interested in using our product because they are similar to our customer segment. I use AWS Cloud, and through AWS Cloud, I use Genymotion Cloud. I use multiple Genymotion Cloud instances, perhaps over 100 at a time, to emulate user behaviors. It helps me parallelize my processes so that I could emulate behavior on various applications on multiple instances of Genymotion Cloud and get the insights from individual Genymotion Cloud instances to the master instances to then proceed to business intelligence data infrastructure.
Chapter Lead at a energy/utilities company with 10,001+ employees
Real User
Top 20
Dec 2, 2025
My main use case for Genymotion Cloud is to generate diagrams. I work for an oil and gas company, so we use Genymotion Cloud to generate data by utilizing all the data from IoT devices in our platform. We use Genymotion Cloud for Android virtual cloud devices. We install our application, then execute automated tests. We get the results, then we turn off the devices. We use Genymotion Cloud for automated Appium, Espresso, and Roboto framework.
Genymotion Cloud provides a powerful virtual device solution ideal for app developers needing reliable deployment and testing environments in a cloud-based infrastructure.Harnessing cutting-edge cloud technology, Genymotion Cloud offers scalable and efficient virtual devices for app deployment and testing, allowing users to access Android devices globally through the cloud. This enables seamless integration with development workflows and simplifies the process of app testing across different...
My main use case for Genymotion Cloud involves running Appium test cases and CI/CD pipelines in Android devices, allowing me to avoid manually carrying physical devices. I am using Genymotion Cloud for running Android emulators and testing the builds for Appium test cases or CI/CD pipelines. Using Genymotion Cloud for my CI/CD pipelines and Appium test cases significantly helps my workflow compared to using physical devices, as I utilize test cases for checking automation testing for Android builds. I generate the builds using a CI/CD pipeline, automatically upload to Genymotion Cloud, open the emulator, and use that application to check if it's working fine or if there are any issues. When I need to check on specific configuration devices such as Samsung or Xiaomi, I can create those on Genymotion Cloud and verify that my application UI displays correctly on each device and configuration. I mostly use Genymotion Cloud for Appium test cases and CI/CD pipelines for development purposes, as it allows me to run builds without the need to carry physical devices. I simply go to Genymotion Cloud, create any device, and run my builds, testing on each device configuration, which is very helpful for testing and development purposes.
My main use case for Genymotion Cloud at my previous company was testing an enterprise reporting application across different variations of Android versions. Testing on different flavors was tricky until I discovered that Genymotion Cloud was quite easy to use. I started using Genymotion during my Android development around 2015 and was one of the early customers of the desktop version before transitioning to the cloud platform. A specific example of how I used Genymotion Cloud for my reporting application was that we did not have to purchase different high-end devices to test certain features. If I needed to test on a high-end phone, I could simply use a Genymotion device for that purpose. It was also easy to set up, especially with the wide range of Android phones available. With iOS, device options are limited by default since there are only a couple of brand devices, but Android has many variations across different vendors, making it really difficult to obtain those devices. This was particularly challenging for our QA team sitting in multiple locations, as we did not want to purchase numerous devices and distribute them to geographically dispersed QA members. With Genymotion Cloud, the solution was straightforward. We simply created a Genymotion Cloud account for every QA engineer and used it from there.
My main use case for Genymotion Cloud is to emulate user behavior in Android phones to perform automation that helps with business intelligence for identifying potential customers and getting information about similar products as ours that is being used. One of the workflows with Genymotion Cloud that I built is a pipeline wherein I use some of the toolings in Python programming to emulate the user behavior of navigating to the Play Store, installing applications, surfing the application, and getting the screenshots of individual pages so that I can automatically generate descriptions, reviews, and images, and use cases of various mobile applications. The main use case, the automation that I perform with Genymotion Cloud instances, allows me to gather data about various mobile applications in different categories and spaces and identify correlated applications to the data that I generate from Genymotion Cloud instances. This allows me to generate correlated data about various mobile applications in the same space or different spaces so that our business team can reach out to potential customers that might be interested in using our product because they are similar to our customer segment. I use AWS Cloud, and through AWS Cloud, I use Genymotion Cloud. I use multiple Genymotion Cloud instances, perhaps over 100 at a time, to emulate user behaviors. It helps me parallelize my processes so that I could emulate behavior on various applications on multiple instances of Genymotion Cloud and get the insights from individual Genymotion Cloud instances to the master instances to then proceed to business intelligence data infrastructure.
My main use case for Genymotion Cloud is to generate diagrams. I work for an oil and gas company, so we use Genymotion Cloud to generate data by utilizing all the data from IoT devices in our platform. We use Genymotion Cloud for Android virtual cloud devices. We install our application, then execute automated tests. We get the results, then we turn off the devices. We use Genymotion Cloud for automated Appium, Espresso, and Roboto framework.