We use AppPulse to look at two of our most important applications. Our contact centers that take calls from our customers, and our website that our customers use to pay bills online, etc.

We have a lot of quick wins. I call them quick because AppPulse has only been in the environment for a short time. We've been able to find misconfigured network segments, we've been able to find data we've never had before, like our logo transfer from our content delivery network, and how long it took to move over. We've found issues around daylight's savings time, and customer portals that we probably would not have found on our own without AppPulse.

We've had a very quick return on our investment as far as being able to monitor applications that we hadn't been able to monitor before, and then able to catch problems that we previously had not been able to catch. For example, with the way we have AppPulse deployed, we were able to catch a problem at a particular call center where the application was running roughly 10 times slower than other call center sites. We were able to catch that and help remediate that. It affected a lot of call takers with very slow-running application and we were able to help resolve that quickly.

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.

To fix a crash we need to know the root cause. The detailed log is sent frequently to the developer to help improve the next version. I've worked with developers before, but since using HP AppPulse, we work together to provide the client with the best validation possible.

The service also features FunDex, which is a score related to how enjoyable the application is to use. The score starts at 100 and an app loses points for various transgressions, such as crashes and sluggish performance. Developers can drill down and see how and why various points are being lost from their app’s score.

We only get one chance to make a good first impression, so let's make sure our app launches quickly.

In order to provide our user with a unique experience, we have committed ourselves to give a fast, reliable, and error-free application that are monitored and updated regularly.

A good user experience consists with a fast app launch, continues with a catchy UI and easy booking flow without any delays and crashes.

We adapted the product into the development lifecycle and adopted it across our key UI and development teams. We improved the product stability and performance, as well as the user perspective, and can now see why, and how many, customers experience bad applications during launch time. Then, we can redesign the product so it will be improved for a smoother, nicer appearance when our users next start the application.

We learned within 24 hours that users were spending 43 seconds on the registration page and 53% were leaving before registration. We had not known this for years, and after we stopped development initiatives, and started using single sign-on, we got the registration down to two seconds, a five-fold increase, and increased completion to 98%.

This was a big improvement because people don’t want to sign up for something new. As soon as we found out the issue, we instantly saw an increase in stars and number of downloads. When we first started the analytics, we had a .4% conversion rate from the free version to the paid one, and after about a year a 1.15% conversion from free to paid, an additional 4% up-sell.

What we learned is that the analytics are more important than the app itself. If you don’t know what users are experiencing, it's like driving at night with no lights, and you can't make the most calculated decisions without the full developer roadmap. It also helps us align the developer road cycle, identify the user experience ahead of ego, etc.

You can test your app all day long. If you don’t know where to search and on what device, you will lose precious time. We launched the Take It app in France last June, and we had 10,000 active users. Five percent of our users experienced crashes, so we decided to add AppPulse Mobile to our app, and crashes dropped from five to 0.44 percent. During the same time period, our users jumped to 120,000.

Another example, Take It is a social photo sharing app, and we noticed that some of our users needed more than 20 seconds to upload a photo, and we were losing customers who were also leaving poor reviews. Through AppPulse Mobile, we were able to identify this issue and address it. Now, our app takes only two seconds to upload a photo and the UX is much stronger.

Our business marketing and technical aspects have improved.

It immediately enables us to see all the versions that our customers use, and helps us manage the different ones available. It helps us to figure out the day-to-day usage and preferences of our customer. There are features that we have been working on for years and we need to know if our customers are using them to determine their value.

We gain understanding of how our users use our mobile apps and then we see how we can possibly improve. Its a great tool when I discuss our mobile app with both the technical guys and with our business side. The solution is easy to understand for our business side, but at the same time gives us enough technical details so we can pinpoint possible causes of what’s low and what can be developed.

It increased the customer satisfaction for the usage of my smart apps, and it reduces the number of crashes, proactively, so I know before the issue happens. I do the testing, and during the QA and the pre-production environments.

Customers are seeing the benefits immediately, mainly in the back office. They are able to develop more quickly versions in which users can see the application to correct and monetize it. This is the most important thing of all.

We can understand why an application crashes, and this helps us to reduce corruptions in an application and to make it easier for a client.

The FunDex is a valuable feature for our organization. For example, if I am seeing user-points used by FundEx, and I understand what is missing, so using the FundEx code, I can identify where exactly the problem is and I can fix my application.