HeadSpin would benefit by adding code coverage. On the front end, when we execute our automation or do a manual change, we don't know what percentage of the code has been tested. If HeadSpin could provide the coverage percentage, that would be helpful.

There is definitely room for improvement in terms of marketing. Marketing is something that is not that great. If you look at some of the other companies in the space, they have a lot of published case studies and tested models. They make a lot of noise. They have got some of their best customers talking about them, which is where HeadSpin needs to work.

They should automate their onboarding. A lot of things are still manual. They can create a video assistant or something like that to completely automate the entire process. 

There is a great scope to improve professional services. The time to deploy is quite long. They can increase and improve the scope of their professional services and set up automation through scripts. They do it at this stage, but they're very expensive.

I would love to see them come up with project-based costing for companies that are startups or low on funds.

Apart from these, they have been on top of the game in terms of features. I can't think of any other new set of features at this point in time because they're already on top in terms of innovation.

First of all, it's very laggy. Not with the UI, but when you interact with the remote devices, I think the latency is seven to nine seconds. That means that there is a seven- to nine-second delay on average when you click on certain things. If you want to do some testing or check the devices manually or check the application in a particular device manually, it is really laggy. That's a disappointment because sometimes we would like to do manual testing when our local devices are not available.

Secondly, tvOS devices can't be connected to Wi-Fi. For example, suppose you are doing multi-region testing, meaning you want to test one application in multiple regions. You have to change the location and use a different Wi-Fi or VPN for each device. Mobile devices can be connected, but it's not there yet for tvOS devices. Here's another example: Apple TV is connected to LAN, and if you have LAN, it cannot switch between regions because the LAN is for a particular user. Since the Wi-Fi support is not there, you can't switch it to, let's say, UK or Denmark because it's connected to LAN. That's one drawback and disadvantage we are facing because our application supports around 12 to 14 regions.

HeadSpin could improve on the user interface because it is very poor. The checks that are done on the iOS devices are very difficult, but for Android, it runs great. For all iOS devices, the user interface and how it interacts with the device are very poor.

HeadSpin needs to improve the hardware. With the mobile, the battery life reduces and must be continuously charged. HeadSpin should focus on hardware tests and installing mini-computers instead of mobiles to improve the hardware.

As an additional feature, HeadSpin can add the ability for different reports. For example, if I configure something, I want to be able to show it to management by producing a specific report. It will reflect more value and make it easier for management to make spending decisions. In addition, if management can see these kinds of reports on all devices and applications we configure, they can allocate money for the proper purpose.

Support and pricing could be improved.

They are developing web applications, but their support for that is not good enough when you compare them with their mobile support.

They have some features for web projects and some for mobile projects. It would be good if we can use similar mobile project features for web projects.