AppPulse Suite Review

We can collect data about the user experience and check if the app is well-designed.

How has it helped my organization?

It really gives us the feedback in order to be sure that we have built and tested apps appropriately. These are the apps that we are releasing to our public domain or internal user.

What is most valuable?

We collect data about the user experience with real life data. This does not come from the testing part, but rather from the user part. We want to be sure that what we have tested and designed is really used as expected by the user.

We can collect data about the user experience and see how the user is behaving with the app, or check the behavior of the app itself. This is done in the context of the device that we are targeting.

It is interesting to check if the app is well-designed regarding the user's expectations. For example, we check if we have too much data transfer, or if the consumption of the battery is okay. We take into account the number of actions that you being done.

There are two levels of feedback coming from the solution. One is the user experience, which is really important. The other part is the design regarding the usage of this app in real life.

I'm working with a pharmaceutical company and that means that we have to instrument the app. This is a little bit similar to "big brother". In the context of a medical collection of information, we are facing some issues about regulation for data privacy. For example, localization is quite a sensitive issue for us. We are using AppPulse, but not as extensively as we expected, due to the limitations and the regulations that we have to meet.

What needs improvement?

The regulations should be better customized for the kind of data that we cannot send to the SALs environment. Certain things can't be sent to the SALs environment, otherwise we in breach of one of the legal regulations in the FDA.

We know that we do receive this kind for information. There is a white paper coming from HPE ensuring that the data will be anonymous. This information is new, so we need to be sure that we are not putting personal details or better privacy at risk, in terms of compliance regulations.

Sometimes the user does not really use some of the functionality, or he extensively uses other functionality, which for us is not so important.

What do I think about the stability of the solution?

I have no concern about the stability of the solution. It works well. There are no major issues related to that. The behavior of the solution is as expected.

What do I think about the scalability of the solution?

In terms of scalability, we are not using it extensively. From a scalability point of view, we do not have an extensive number of applications that we are monitoring through this solution. I cannot really answer that question.

How is customer service and technical support?

Technical support was good for the installation and for the support of the initial support of the software. This stage is quite simple, smart, and easy to use.

Of course, there are elements that are a little bit more complex for us to understand the functionality of the solution. Afterwards, when you are looking at the different layers, such as consumption of the battery, or about user experience and so on, it is quite intuitive.

Which other solutions did I evaluate?

We did not evaluate alternatives. We actually purchased the Mobile Center Suite, so this solution's mobile app came with it. In the first mode, we actually demonstrated it to the mobile developers, the guys responsible for mobile management of the apps.

I know that they already had something in place. And we were quite amazed with what is possible without changing the code. That is a very important thing in regulated environments.

If you deploy an app in production, it should be identical to the same app that you are testing without any code changes. If you test an app and afterwards, you change the source code just to allow monitoring, then you are going against the regulations.

What other advice do I have?

I work in a pharmaceutical environment which is highly regulated. Our corporate users are using applications and software following procedures and guidelines which are predefined, to maintain compliance.

However, users using mobile apps (company/internal app or public/patient app) and the associated device are not intended to strictly follow the rules and guidelines for regulated apps. Most of the time they are trying to use them not exactly as expected: skipping steps, not using the app for what is was designed to do, using functionalities which are considered less important. So, initially we did not extensively test all the various network conditions.

Having the real/user pathway is helping us to adjust what is important for the user and develop appropriate testing strategies.

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Add a Comment
Sign Up with Email