So, you created this amazing mobile app for the employees at your company. Gone are the days of connecting to the VPN, and the painful experience of navigating the company intranet on your mobile device! Your app eliminates all that, and because it’s a hybrid app, it’s available for every device–even better! Your colleagues will surely install, use and love it! Or won’t they?
Get the facts, not opinions
The next wave of mobile application development is here, and enterprises now face the challenge of delivering a sizable portfolio of business-to-employee (B2E) apps. These B2E apps are typically not published to the official app stores, such as the Apple Store, Google Play Store, or Windows Phone Store. Instead, they’re published to enterprise app stores or distributed as “sideloading apps,” which are apps that can be installed on the device by simply scanning a QR code, for example.
Generally, B2E distribution options do not offer the possibility for the user to provide feedback about the app. Even if the option is provided, most developers still don’t know how (or even if) their apps are used. An employee can rate your app with five stars and even comment that “this app is the best thing since sliced bread”…just before uninstalling your app, never to use it again. What you need are facts–not opinions.
In-app usage statistics
The people using your app are probably not using it the way you think they are. If you really want to learn how users are navigating your app, you need to track events based on actual user interaction, and create conversion funnels based on those events. You’ll quickly find out where users spend the most time, and which parts of the app are not accessed at all. You can also track device information, average response times, and other performance-related statistics–all without jeopardizing the user experience (of course)! In-app usage statistics can provide you with the information you need to measure application usage and user engagement to increase workforce productivity.
Implementing a solution to collect (and report on) in-app statistics can take a lot of effort. Fortunately, most current Mobile Application Development Platforms (MADP) offer this functionality out of the box so that app developers can focus on app functionality, not developing analytics tools. If you’re not using a MADP (or your MADP does not support it), try to find an SDK that does the hard work for you.
Whatever you do, make sure you’re collecting in-app statistics because they will enable you to create better versions of your app…and that’s a fact 😉
Do you collect in-app statistics in your apps? Do you use a framework or did you develop it from scratch? Let me know in the comment section below.