To improve Anbox Cloud, we can enhance the speed and flexibility of the platform. We can focus on optimizing allocations and CPU scheduling, as we are experiencing load distribution issues and experimenting with CPU planning that locks specific cores to instances, all while utilizing the default scheduler's mode for resource allocation improvements. For improvements related to the requirements, we can implement more CPU scheduling, fine-tune resource allocations, optimize our infrastructure, and adjust the Android execution model for specific workloads.
Anbox Cloud can be improved mainly in ease of setup and operational simplicity. The platform is very powerful, but the initial configuration can feel complex, especially around infrastructure, networking, images, GPU support, and scaling. Better guided setup, clearer troubleshooting messages, and more production-ready templates would help a lot. I would also improve the monitoring and reporting experience, especially around session performance, resource usage, latency, and failures. For QA and operation teams, having clearer dashboards and logs would make it easier to detect problems quickly. Overall, it works well, but it could be more user-friendly for teams that do not have Linux, LXC, or cloud infrastructure experience. I would add that the documentation could be more scenario-based. The official docs cover the components, but real production examples would help more, specifically for scaling, GPU configuration, networking, image lifecycle, and troubleshooting failed sessions. Also, integrations could be stronger. Better out-of-the-box examples for CI/CD pipelines, monitoring tools, observability dashboards, and automated QA workflows would make adoption easier. I also would appreciate clearer guidance around cost optimization because when you scale Android instances in the cloud, resource planning becomes very important.
Regarding improvements for Anbox Cloud, I see it as a perfectly executed solution that has not faced challenges as far as I know, but if I had to suggest a specific improvement, I would say that AI integrations could be better.
Everything seems to be very great, whether it is deployment integrations, the user interface, the pricing, setup cost, deployments, each and everything is on point. The ROI we are getting here is more than expected, so there is nothing I can remember as an improvement to the software. If I had to think of an area for improvement in Anbox Cloud, I would say AI is getting advanced day by day, and they could add some advanced AI integrations and an AI agent in their upcoming workflows.
IT Private Cloud & Infrastructure Leader at Sicredi
Real User
Top 5
Dec 4, 2024
In Brazil, it is difficult to find technical professionals with OpenStack or this technology skills. The solution is complex to administrate, and the initial setup requires significant experience.
Anbox Cloud is a platform designed to provide scalable cloud-based environments for running Android applications. It delivers a virtualized Android operating system, allowing apps to operate independently of user devices.Anbox Cloud enhances application delivery and management by virtualizing Android at scale on any cloud infrastructure. It enables organizations to offload processing from user devices to the cloud, improving application performance and reducing hardware dependency. The...
To improve Anbox Cloud, we can enhance the speed and flexibility of the platform. We can focus on optimizing allocations and CPU scheduling, as we are experiencing load distribution issues and experimenting with CPU planning that locks specific cores to instances, all while utilizing the default scheduler's mode for resource allocation improvements. For improvements related to the requirements, we can implement more CPU scheduling, fine-tune resource allocations, optimize our infrastructure, and adjust the Android execution model for specific workloads.
Anbox Cloud can be improved mainly in ease of setup and operational simplicity. The platform is very powerful, but the initial configuration can feel complex, especially around infrastructure, networking, images, GPU support, and scaling. Better guided setup, clearer troubleshooting messages, and more production-ready templates would help a lot. I would also improve the monitoring and reporting experience, especially around session performance, resource usage, latency, and failures. For QA and operation teams, having clearer dashboards and logs would make it easier to detect problems quickly. Overall, it works well, but it could be more user-friendly for teams that do not have Linux, LXC, or cloud infrastructure experience. I would add that the documentation could be more scenario-based. The official docs cover the components, but real production examples would help more, specifically for scaling, GPU configuration, networking, image lifecycle, and troubleshooting failed sessions. Also, integrations could be stronger. Better out-of-the-box examples for CI/CD pipelines, monitoring tools, observability dashboards, and automated QA workflows would make adoption easier. I also would appreciate clearer guidance around cost optimization because when you scale Android instances in the cloud, resource planning becomes very important.
Regarding improvements for Anbox Cloud, I see it as a perfectly executed solution that has not faced challenges as far as I know, but if I had to suggest a specific improvement, I would say that AI integrations could be better.
Everything seems to be very great, whether it is deployment integrations, the user interface, the pricing, setup cost, deployments, each and everything is on point. The ROI we are getting here is more than expected, so there is nothing I can remember as an improvement to the software. If I had to think of an area for improvement in Anbox Cloud, I would say AI is getting advanced day by day, and they could add some advanced AI integrations and an AI agent in their upcoming workflows.
In Brazil, it is difficult to find technical professionals with OpenStack or this technology skills. The solution is complex to administrate, and the initial setup requires significant experience.