Which would you choose: an app which delights your customers and boosts your business, or one which may save hundreds of pounds in development costs but which could be vulnerable and potentially harmful to your business?
What makes an app a
To be high quality, an app has to do what it is supposed to without crashing unexpectedly, leaking data and so on.
Good code is only the tip of the iceberg for a stable app. There are other reasons for instability too. Developers build apps to a specification based on requirements that have to be communicated, and it's not uncommon for requirements to be misunderstood or miscommunicated.
Imagine an app that's been designed to be used by ten people at once, but which was supposed to be able to handle 10,000 concurrent users. A misunderstanding like that can lead to an app that's effectively useless, without any coding errors on the part of the programmer.
Just to make things even more complicated, apps may stop working due to some external factor beyond the control of the developer. For example, many apps are integrated with
Let's get back to quality for a moment. You'd think that to be high quality an app would have no bugs or code defects. But here's the inconvenient truth: software development is orders of magnitude more complex than almost any other human
Fixing bugs costs money, and apps are developed to a budget. Therefore the more bugs that get introduced, the more of that budget is used up by bug fixing activities, and less is available for making the app more useful.
That means that developing a
Defects in the requirements and app design phase can actually be corrected fairly easily, but the cost of correcting
To be a really
(This last item is very important. Imagine an API upon which your app is changed by a third party. Until you can update your code to restore compatibility with the new API, your app will lose functionality - or even not work at all.)
How do you maximise the chance that people who download your app actually use it, and continue to do so?
We can talk about ensuring you have a
- Look appropriate for your target market (business users, consumers, etc)
- Be simple and intuitive to use
- Offer obvious and immediate value to the user
- Deliver that value reliably and securely.
The effects of poor quality apps
Producing poor quality consumer apps
But the consequences for business to mobile apps are far more serious. Why? Because if you offer a poor quality business to
- Frustrated and angry customers
- Miscommunications within your staff and conflicts with suppliers and business partners
- Data leaks and security breaches leading to loss of reputation, and high remediation costs
- Slow processes, failed
transactions,and lost business.
All of this means that when it comes to apps - especially business to business ones - skimping on quality is a false economy: it’s just not worth it. The amount of money you might save is small, but the cost to your business can be very high indeed.
And that means you're actually faced with a startlingly simple choice: offer a