One of the keys to long term success on the app stores is releasing occasional app updates. Updates help address user concerns and will keep your app “fresh” in the minds of your users. If you wish to keep your app live for a long time, you will most likely release a sizable amount of app updates. If this is the case, how will you keep track of how many updates you have completed, and how will potential users know that you are actively updating your app?
Below are some of the most common types of app updates and how to use proper software versioning to help you, your users, and the app stores keep track:
Types of Updates:
Bug Fix (Revision):
The most common updates are usually big fixes. Bug fixes usually won’t change the structure or UI/UX of the app, but they do patch up any bugs or issues caught by users as they are trying out your app. Developers should try to roll out bug fixes as soon as possible after a bug is reported.
It could be that you are receiving a lot of bug reports from users all at once. How do you decide which to fix? Focus first on the bugs that affect the highest number of users, and then categorize others based on the severity of the bug.
You can keep track of bug fixes through proper software versioning. Software versioning usually follows this pattern: major version.minor version.revision
According to the common number scheme for software versioning, any bug fixes are considered minor revision updates. So, once you update version 1.0 of your app with your first bug fix, your versioning number should read: 1.0.1 (major version 1, minor version 0, revision 1)