this is just bad coding have you attempted to contact the developer (search internet for website, email address et al) and at the last resort, contact apple and complain. sometimes unless a developer hears about a problem, they may not know about it. when people have reported problems to me in the past, i review and update accordingly.
Yeah, I tried emailing the developer, never heard back. Eventally I found a better program that does the same thing. In retrospect, I never would have bought it. Oh well J
I don't see apple making any cleaning of the apple store. I think they are still competiting on number of app with android.
I can see how I might leverage this from a business standpoint, but I don't think I will. My issue with it is I think it encourages bad business practices more than it does any good. Lots of disadvantages to treating updates as new releases: 1) 'Update Spam' Developers might spread out minor bug updates, or start finding regular small changes to turn their title into a 'living app'. (E.g., seasonal icon changes)... overall it'll be irritating for users and unfair to honest developers who choose not to do 'update spam'. 2) Those developers who create a full-featured, bug-tested app at release, which does not need updating, will be penalized. 3) It takes away one of the few promotional avenues for indie developers releasing a new title, as they'll get swamped amongst the updates. If Apple wants to reward developers updating their app, maybe create a 'recently updated' list... even though to me that seems somewhat silly.
