During the effort to integrate SmartBear’s AlertSite UXM into our Continuous Quality Lab’s Monitoring solution we swapped stories about our own experiences with poorly performing apps. Two came to mind, the WatchESPN failure during the USA versus Germany World Cup match and a mobile banking app based on a third party platform. These discussions prompted the focus on third party content’s impact on performance and availability.
For mobile apps, performance is only as strong as its weakest link. Often, that weakest link might be third party content.
Almost every app with widespread adoption leverages a third party component to enhance its functionality, usefulness, appeal or revenue. Imagine, for instance, a restaurant app without location-based functionality, or an e-commerce app without a shopping cart.
Indeed, third party content plays a pivotal role, but can unfortunately play an even greater role in poor user experience. To illustrate, here’s hypothetical example:
A global bank decided to build their mobile banking solution on a third party platform. Limited in-house skills drive the decision to outsource development rather than developing in-house. The decision was driven by cost, time to market and risk considerations to white-label the platform. Shortly after launching, consumers begin to experience performance-related issues not encountered in during functional testing: crashes, freezes, timeouts, error messages, etc. Vocal consumers began tweeting #