If you follow me on Twitter, you may have recently heard me complain about iOS app developers releasing updates with a report of “bug fixes”. I feel like it is appropriate for me to explain why. Let me preface this: Adding “bug fixes” to a list of other changes is…adequate. The developer made numerous changes and did some clean up in the process. This isn’t ideal, but it is acceptable. Also, in the end, the app is the developers prerogative. But, if they do not want to go into detail about the bug fixes, maybe they should think about what that means. The problem with a “bug fixes” message is it does not answer these questions:
- What bugs did they fix?
- Did it fix the bugs I had?
- Why should I update if I don’t know what has changed?
This is a major problem. Fortunately, there is an easy way to fix this. It starts by investing more time into the release process. It may be more time consuming or leave developers vulnerable by admitting the app has issues. But the release cycle and transparency builds a great user experience. I have faith in developers that admit their faults. And because of this I love them. It’s all part of the user experience. Before I close, I should point out some developers that do a great job providing release details:
tl;dr: Updates are part of the user experience. Don’t keep your users in a fog and let them know what they’re getting.