In the past two weeks, this series has taken a look at how often consumers encounter errors while browsing online and some of the behaviors a user will display when discovering a bug. If you’re new to the party, I’ll encapsulate it here by saying mobile apps are rife with coding issues and the vast majority of consumers have little to no tolerance for low-performing software. What we haven’t discussed yet is the ripple effect of one user encountering a problem.

Errors happen. Despite best efforts, no piece of software is perfect. Unintentional issues with code, updates to existing frameworks, or unexpected interactions with other tools can all cause errors. As a result, it's critical for companies to deploy robust and reliable error reporting processes that help them proactively identify potential issues and improve operational outcomes.

Welcome back to the new Sauce Labs series ‘Every Experience Matters Stat of the Week.” In last week’s edition, we mentioned that about a quarter of consumers encounter an error or bug every day. While this indicated that errors are quite common overall, we didn’t dive deeper into how a customer may react when encountering those bugs. Are customers as forgiving as we might hope? Sadly, that is not the case. The results are dubious, to say the least.

Two popular mobile test automation tools are Selendroid and Appium. Both are loved by the developer community, and for good reason. In fact, they’re so popular that Selendroid is currently bundled into the Appium package in order to provide support for Android versions 2.3 through 4.1. Appium automatically switches to Selendroid when users want to run tests for these Android versions.

Open banking is a natural evolution in the API economy. By laying the foundation for web platform and mobile developers to build third-party products and services using any number of public (open) APIs, banks, financial services and insurance companies are ushering in next-generation customer experiences that are more frictionless and personalized.