iOS Development-Version number Introduction

This is a basic article that briefly describes the version number of IOS.

noun explanation

• version, usually the version number, is the identity that the app uses to advertise instructions to the user. There are generally 2 or 3 segments, such as: 2.1 , 8.1.2

VersionGenerally determined by the product department, completely different updates need to change the major version number, such asQQ 4.0Changes are very large, the major version of the changes will be more appealing to the user's eye, so some applications will frequently update the major version number, such asFireFox 20.0. The two-part version number includes both the minor feature update and the bug fix, and the three-segment version is basically a new feature addition and a big bug fix, and the third paragraph indicates that the stable version is basically fixing the bug

• Build, which refers to a unique compilation identifier, usually an incrementing integer (Android Force is a number, IOS can be a string)

Buildare for internal use and are used to determine a unique version. There is no big connection to the previous Version.

In IOS development, this 2 number can be any string or number.

The situation we are currently experiencing is:

• Version or Build was ignored. One of these two numbers is not going to change in a year.
• The Version and Build are reversed.

Getting a method is also simple:

nsdictionary*info= [[NSBundleMainbundle] infodictionary];info[@ "Cfbundleshortversionstring"];//versioninfo[@ "Cfbundleversion"];//Build

Why use version number 1. Easy Labeling and communication

The earlier mention of version number update will have a positive effect on the promotion. So the version number is not too long, if like this "we solemnly launched a certain 1.7.14.19257!", this will make users feel very dull and like TV shopping, but also not conducive to the spread. If it is "XXX 3.0, very different!" may result in better communication.

2. Easy to track bugs

A Bug in an application is certain, but a quick fix to the problem reflects the ability of the team and the programmer. We often meet developers who say I submit a version, but the download is still old. When we helped him solve the problem, he couldn't figure out which one was, and if he could show the current version in a place like "about", it would be easy to find the problem.

Or a colleague of the Test team, there may be several different versions of the branch in hand that are tested, and they need to accurately describe a beta version.

Reference post: http://segmentfault.com/blog/travis/1190000002423661

iOS Development-Version number Introduction