Would you rather see more frequent updates with fewer features in each, or less frequent updates with more features? Let us know!
sickpuma (guest) 21 Jun 2009 00:54
I'd prefer frequent updates with fewer features.
That way the users can start to use the new features sooner.
Whenever I'm on the app store and I am not sure if I want to get an app or not, one of the deciding factors is if the app gets updated a lot. When I see something like "the next update was submitted to apple" and users writing reviews that mention how an application is constantly updated, it makes me more likely to buy the app because I know that even if I don't like the version I downloaded, there is still a chance that the developer will listen to my comments and implement the features I request. I think updating frequently would more likely get you the reviews that mention how the app is always updated.
It's also easier to try out the new features and remember them when there are only a few changes. When you get an update that introduces 10 new features, for example, the user might forget to try some of them.
With all that in mind however, I still think that updates shouldn't be too frequent. For example if the only thing an update contains is something cosmetic (such as a font change), and the user gets lots of these small updates that aren't very beneficial, they will probably get annoyed that every time they open up the app store, they have to update your application. If it's a major new feature that most users will probably benefit from, it can be in an update by itself. An example of this would be your solution to the auto fill with the embedded browser. An update that contains a few useful features that aren't as big, would probably need at least two or three bundled together, depending on how useful each one is. Cosmetic changes should probably bundled with whatever update is currently in the works, and never released by themselves, unless it's a drastic change. The amount of users that requested the feature should also be taken into account. So that even if it is a minor feature that was implemented, but a significant amount of users requested it, it could be released on it's own.
That's just my opinion, I hope that helps.
lol this should probably be a blog post or something like that.
sickpuma (guest), 21 Jun 2009 00:54
Yuumoushin (guest) 23 Jul 2009 23:09
My vote: more frequent updates.
What I may consider a marginal change to the application, someone else may consider substantial. And vice versa. The ability to see the development of the app over time keeps it fresh, and to a degree, more "interactive." That being said, the commenter above brings up a valid point: it needs to be frequent enough to provide an added value, but not so frequent such that it delves into the realm of annoying.
I think the same can hold true for the blog - last update was in May, which merely touched on the password feature, but perhaps there are other suggestions, etc. that might add to those of us that use the application? Even a tip or trick regarding a specific use or feature? The forum helps, but requires a bit more searching.
Yuumoushin (guest), 23 Jul 2009 23:09
Cantello (guest) 18 Aug 2009 07:55
My vote is for more frequent updates as well. Also, try to keep the users entertained by posting bits and bites in your blog. Makes it easier to follow what you guys are up to.
Cantello (guest), 18 Aug 2009 07:55
Kyle (guest) 15 Dec 2009 22:29
I think updates a little more frequent would me great. Maybe every quarter or so? But not every month.
Kyle (guest), 15 Dec 2009 22:29
