4 ways to improve mobile UX

01/01/20184 Minute Read

The most effective customer relationship services of today and tomorrow are probably served up through smartphones. As content offerings for marketing, customer service, and loyalty programs become digital, there’s a huge movement in board meetings to focus on the mobile customer experience. McKinsey & Company has found that digital customer care can offer huge improvements in satisfaction metrics, while driving huge costs savings for the enterprise.

But your app is only as good as your uptime. More demand for digitisation means a heavier workload for IT to keep customers—both internal and external app users—satisfied. The world’s shiniest mobile interface won’t make up for constant latency issues or repeated 502 errors.

Why your back-end really matters

Canadians are some of the most active citizens online, with 39 hours per month spent on the web on a desktop or laptop. Average time increased to almost 75 hours a month, or two and a half hours a day, with streaming and mobile devices, according to measurement firm comScore. Time spent engaged with streaming content has doubled during the past six years. While the explosive adoption of streaming video, media, and other forms of content is good news for your digitised brand experiences, it’s also a risk if IT departments can’t keep up with demand.

When latency or connectivity issues occur, your employees and customers could revolt. Recently, Slack was hit by a multi-hour outage caused by a third-party network failure, resulting in a panicked user base that took to social media to voice their contempt. Persistent connectivity issues with Instagram in April 2016 also resulted in social media outcry among their dedicated user base.

According to TechCrunch, a Compuware survey revealed that users expect an app to load in a minuscule two seconds, and only 16 percent of users said they would give an app more than two attempts if they experience latency or connectivity issues. Still not scared? Amazon could stand to lose $1.6 billion dollars in sales per year from a second of delay, according to Fast Company.

Your employees may not have the option to drop a company app, but they’re likely to get frustrated over productivity lapses. For IT pros, mobile customer experiences are more than just the user experience and quality of content available. It’s also a matter of consistency through smarter infrastructure.

Is your mobile infrastructure customer-ready?

There’s more to an adequate mobile infrastructure than basic components—it’s also about the quality and planning. Until 2014, Facebook’s company motto was “Move fast and break things.” In light of 500 billion API calls each day, they’ve now switched to “Move fast with stable infrastructure,” which Facebook CEO Mark Zuckerberg acknowledges is less catchy but more sensible.

This approach has lessons for brands who lack their billion person-strong user base. Here’s how to adopt it:

1. Strive for elasticity

When demand is unpredictable, IT may need to explore options for elasticity, defined by VentureBeat as the “ability to expand capacity as needed in an instantaneous and ideally automated way.” While this option has the potential to eliminate the latency and connectivity issues associated with static virtual machines, it includes some implementation challenges. IT pros must explore effective, policy-based communication between containers and related security concerns.

2. Fortify your VPN

If your internal or external app relies on proprietary or sensitive data for personalisation, establishing a Virtual Private Network (VPN) is needed to secure data communications. Ensuring your mobile app is connected to one can prevent interception of data. With stronger user authentication, you can serve up highly personalised customer experiences with minimised risk of data breach.

3. Don’t plan for desktop usage habits

When it comes to an initial app launch, there’s a danger in trying to translate desktop usage habits to mobile devices. Mobile engineering expert Farhan Thawar is a firm believer that analytics from web apps aren’t always a great indicator of how people will use a mobile app. Case in point: you may check your bank’s app once weekly, but you’re likely to open the mobile app several times per day.

Planning for mobile-specific usage based on existing analytics can allow you to better plan containerisation, demand, and other factors prior to launch.

4. Track and improve

Mobile infrastructure analytics are critically important to the continued success of your employee and customer experience. Looking beyond stats on adoption and page flow can enable IT to develop an end-to-end understanding of how their apps are working. IBM’s Luba Cherbakov cites the following benefits of an analytics-driven approach to mobile app infrastructure management:

  • Find opportunities for infrastructure optimisation.
  • Justify and make better infrastructure investments.
  • Simplify knowledge of app performance issues.

If your back-end infrastructure isn’t up to the job, your customers may opt to delete your apps and never re-download them, without even giving their features or benefits a chance. A positive mobile customer experience requires stability and consistency in content delivery. Without the behind-the-scenes effort of IT pros, the digitisation of customer relationships is impossible.

Josh Folland 23/01/2018 3 Minute Read

Making the case for colour printing

Using colour printing is a tried and true way to get your business noticed. But is the benefit worth the added cost? We find out here:

Tektonika Staff 11/01/2018 4 Minute Read

How IT Time Lords are regenerating their leadership skills

There's no doubt about it: Tech moves fast. But how do we as tech professional keep up with it?

Tabi Jackson Gee 30/11/2017 13 Minute Read

Millennial employees rewrite the office rulebook

The war for talent now requires running tracks, free beer and fishtanks. But kindness and culture might be better ways to hire and inspire staff.

Leave a Comment

Your email address will not be published. Required fields are marked *