Last month we launched uTest Apphance, a new mobile quality tool that makes it easy for mobile app developers to understand how their apps are working across a wide range of mobile devices, carriers and locations. Since then, the response has been incredible. Hundreds of customers have already signed up for Apphance, and each day we’re delivering mobile developers incredible amounts of information about crashes and bugs.
Still, as we’ve talked to our customers about Apphance, some of them have asked us to share with them a working example – an app where they could kick the tires and get to know how Apphance works.
We think that trying out Apphance should be as easy as possible. That’s why we’re pleased to announce new Apphance demo apps for iOS and Android (available in Github). These “Hello World” apps are basic projects that already have Apphance installed and ready to go. Because they’re open source, you can see how Apphance is installed and then modify the code yourself to get to know Apphance’s many features1. To get started, all you need to do is create an Apphance account, download the demo apps, and then compile them in Xcode or Eclipse. Complete instructions for getting them up and running can be found in the README documentation on Github.
To better help you get started with Apphance, we’ve also put together new installation tutorials. And for iOS and Android developers, we’ve created new instructional videos designed to walk you through the process of adding Apphance to your code. Both videos are around 3 minutes long, which just shows that yes it really is that easy to integrate Apphance into your app.
If you’re a mobile app developer who hasn’t tried Apphance yet, it’s now incredibly easy to give it a try. Create a free Apphance account, download the demo apps, and get started.
 Too really get a feel for how Apphance works, try deliberately adding a crash to the demo apps. For example, try dividing by 0. When you restart the app, a crash report will be sent to the Apphance servers. Ironically, I think this is the first time I’ve ever suggested that you add bugs and crashes to your code rather than fixing them.