So you’ve researched and selected your mobile app development partners. You’ve scoped the project, reviewed contracts and are raring to go. But something is bugging you, quite literally.
Somewhere in the contract there’s a cost for bug fixes. You ask yourself, why should we pay to fix issues in software that our mobile developers have created in the first place? Why aren’t they delivering faultless code right from the start?
In this article, we discuss the topic of bug fixing and explain why we charge for bug fixes at Brightec.
A bug is an error in a software that can occur anytime during the development process. According to Wikipedia, “A software bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.”
Given that a bug is an ‘unexpected result’, the only way to truly define one would be to write down the expected result of every situation. We would require a way of documenting every feature in advance down to the most minute detail. Without this information, who’s to say what a bug actually is? Everyone involved may view a feature with a different expectation.
For example, we wouldn’t have advanced knowledge of Chrome releasing updates that would impact credit card transactions on a particular app. We also wouldn’t anticipate a rail travel app needing to include tickets booked with a ferry transfer. Not only is it impossible to define every feature in advance, it contradicts our Agile process to do so.
Ellie Jones, our QA Engineer, shared the following in her article on bug reports: “Bugs. No one wants to find one in their app but it’s inevitable at some point. It’s difficult to understand why something isn’t working as you expected it to. But it happens.”
You could say that the mobile app development process is all bug fixing. So much of an app developer’s time is spent breaking a feature for a test and then repairing it. This is an integral part of how development works.
The point at which you spot an issue determines if it is a ‘bug’ or simply part of the development process. If the issue is spotted before it is sent to the client, is it simply part of the development process? If it is spotted after, is it then a bug? Where’s the line?
If we were to offer free bug fixing, we’d need to extensively manually test everything before we sent it to the client so that all bug fixes are on our side of the chargeable line.
Whilst in theory we could fully test every aspect of the app, the reality is that most of the apps we work on are driven by complex data. We could never fully understand that data or our client’s businesses, so would never spot 100% of the ‘unexpected results’ anyway.
Given this, we only manually QA all our builds against the task descriptions which we believe catches 95% of issues. However, to reduce the cost to the client, the final complete testing sits with them.
Keeping costs as low as possible is something that is really important to us. We don’t want to charge our clients for something they can do themselves - testing. Equally, we don’t want to overburden our clients with unnecessary work - written-specification.
We believe that the efficiencies and cost savings created by our Agile approach more than cancel out any small costs that might be associated with final bug-fixing. So, while we do charge for bug fixes at Brightec, we do everything in our power to keep costs as low as possible for our clients.
If you’d like to enquire about bug fixing, get in touch with our team. We’d be happy to help!
Search over 400 blog posts from our team
Subscribe to our monthly digest of blogs to stay in the loop and come with us on our journey to make things better!
We develop intelligent mobile apps for iPhone & Android that deliver for you.
Want to connect? You can find us on Instagram, Facebook, X (formerly Twitter) and LinkedIn.
Here’s our privacy policy.
Here’s our Accessibility statement.
Copyright © 2024 Brightec Limited. All rights reserved.
