thomq: Though, I don't know where you got that version number of 0.29 you posted (5 days ago, July 26 perhaps?). As of July 5th, it was listed as version 1.0 on the App Store (for iPhone devices), with it's latest version as 1.1.1 as of August 1.
Tekkaman-James: The iOS version number is not the actual version number, it's an arbitrary number assigned by Apple. If you actually check the log-in screen of the app itself, the current version number is 0.31. You're right that the number may not mean that it's only 1/3 finished, but we can at least agree that it isn't version 1.0 in any interpretation
(other than Apple's).
In some software design the version is as follows.
MAJOR.MINOR.FIXES. Major version numbers usually denotes major changes in the software, and full releases. Minor includes added features, fixing bugs, and improving stability. Fixes usually would be hot fixes that shouldn't change compatibility as long as the
MAJOR.MINOR is identical.
For Linux development it's a little different. You have the major kernel number, and then the minor is sorta just as important. The exception being that odd numbers are
'development' versions, so 2.5.xxx would be a dev version, and when they are ready they are moved into the 2.6.xxx kernels, or the entire tree gets effectively renamed once it's completed. The fixes then would be non-dev addons and fixes.
To note the numbers aren't percentile, so a patch of 0.1111 is possible, and it should probably get a v1.0 when it's deemed ready for customers and release... Making me wonder why it was pushed while it was so obviously not ready and broken. The idea of testing server loads and finding bugs they weren't aware of does come to mind. However I recall Blizzard doing this with Diablo 2 by releasing a 300Mb early (
free) copy of Diablo 2, which only included the Barbarian, and the first act.