What a week we had out at #iheartSDC! Our last day didn’t disappoint with an enlightened session by Marv Storey called Don’t Lose App Revenue Over Poor Customer Experience – we couldn’t agree more!
We learned that 75% of users desire help on their smart phones (Synthetix). Additionally, 72% of app users actually expect the company to support the app (Nuance). Marv pointed out that customers are willing to pay up to 2x when they know it will lead to a quality product and are much less likely to be dissatisfied with the price when there are no issues. Encountering just 2 problems can bring price dissatisfaction up to 50% (John A Goodman, ‘customer experience 3.0’ amacom 2014).
Having a real-time support strategy in place could go a long way to ensure customer success & satisfaction, especially since support in apps is typically satisfied with phone support, email support, external forums, and internet searches.
According to Marv, studies show that 53% of app users prefer phone support over the others for issues they encounter. These days, app developers tend towards email support because it is easy for them. However, app users are almost always dissatisfied with this because it is impersonal and there is no guarantee of a timely resolution. Phone calls are much preferred because of the empathy they generate and the customer feels like they can get real time resolution.
This was interesting to me because RevTwo falls right in the sweet spot between these two types of support. We marry the human touch that people love from phone calls with the ease of use of email, all while keeping your users within your app. It is also extremely easy for developers to integrate.
I found Marv’s presentation to be incredibly insightful, what do you think?
Exciting things are happening in San Francisco this week! The 2016 Samsung Developer Conference has taken over Moscone West and the RevTwo team and I have been lucky enough to get a first-hand look at several exciting new technologies coming out from Samsung.
Day 0 gave us a chance to get our hands dirty with the Knox API – Samsung’s mobility management platform that gives you the power of full security control over your enterprise devices. I also had my first experience with virtual reality in their filming for VR workshop. I eagerly snapped on the Gear VR headset and was instantly transported to Tahiti and immersed in the clear water, overhanging bungalows, and tropical aesthetic.
Needless to say, exposure to such exciting tech had us pumped for Day 1, which opened with an inspiring Keynote that had everyone excited about new areas in VR. Samsung is aiming for a star trek holodeck immersive experience.
Lots of innovative things on the IoT front and Smart Things platform. Connected cars are a reality and Samsung wants to make it easier to build apps for your car. Samsung now offers a small device that can be plugged into your car and provide you with diagnostics about your vehicle and statistics on your driving that can be used by insurance companies for reduced rates & safe driving bonuses.
We also had a chance to attend the Innovation Track, which was a great opportunity to hear from industry leaders about what they are building with Samsung technology and where they see it heading.
Bugs—developers hate them. Hands down, bugs are the most frustrating and challenging part of the app development process. Crashes suck, but at least then you can see where everything blew up and where the problem happened.
The worst kind of bug is the silent kind or the hairy tarantula as I like to call it–the one that sneaks in as a missing file or unsynced data and usually appears randomly. Everything works perfectly on your phone and desktop, but as soon as the app is in TestFlight, all hell breaks loose. Our co-workers and customers try to describe what they were seeing on the app. Frantically, we try to repeat the issue, plug into Xcode and reproduce the error—which usually doesn’t work.
I’ve been there—we had a complicated app that worked in online and offline modes with a rather smart syncing mechanism in between. It all worked great on my high speed Wi-Fi and with our small team during testing, but once it was in the hands of the customer, a bug surfaced.
Fixing it was a nightmare. Users couldn’t clearly explain to me what actually occurred or what caused it (there was no crash, just missing files and data that thought it was synced when it wasn’t), so replicating the problem was difficult. Not being able to see the issue made it seem impossible to make the pesky bug go away—I burned weeks trying to understand what exactly was happening behind the scenes.
A faster, better debugging experience
There is a better way and a faster path to building a successful app. RevTwo makes the debugging process less painful by giving developers tools to create a bug-free app and connecting them with users who need in-app support.
How do the tools work? Three simple steps (really!):
The RevTwo API is integrated into an app in 10 minutes or less, giving users the ability to submit help request tickets describing the issue they’re experiencing.
A developer can initiate a help session to view the user’s screen while talking to them on the phone to see how they’re using the app, and what buttons they’re pressing. Additionally, with RevTwo, developers get insight beyond the surface level, and can get details like:
Device system information to see if the user is running the latest iOS and what app version they’re using
Network settings such as Wi-Fi and Bluetooth
Memory usage and disk space to help pinpoint issues like memory leaks
App log details, in real time, just like in Xcode, as well as access to the log history without needing to reproduce the error
App file system access (not the whole phone, just the app—we are still bound by the sandbox) to view all the files the app has stored in its documents directory and any subdirectories within (with the capability to download and upload files directly to the app)
App SQLite database view, which allows developers to view the table structure and data that the app is operating on
The result is a developer finding and fixing a bug in record time, resulting in a happier user.In the end, I did track down that big, hairy tarantula of a bug, but it cost us time, money and a fair bit of sanity. Debugging can be like wandering a maze in the dark; tools like those from RevTwo let you turn on the lights.
Try it out for yourself; sign up for our free troubleshooting tools to help during TestFlight