10 signs when developers should stop upgrading their software |
There comes a time in every software program where upgrades to add new features are a takeaway. I mean it’s like when you are too fat and you need to say no to yet … another … Twinkie.
Now there are marketing urges and developer urges. I’m talking strictly developer urges in this post. I’m not saying that from a marketing standpoint releasing some dolled up new version of your software doesn’t continue to promote your brand because obviously it does. The point is: are you adding features the software really needs or would it be better to make another, different program that incorporates and assists the original program? Or how about adding a plugin structure and regularly offering new plugins? This way those users who really want to tinker with your software every five minutes can do so. Those users who want to run the program so slow that the clock ceases to function correctly can go crazy.
And no, no, no I don’t mean upgrading for the sake of patching security holes or staying current with a new OS. That isn’t an upgrade, that’s essential, responsible patching. If you talk to users who get comfortable using a program with a certain interface, they don’t like it when developers change what they are comfortable using and yet some can’t resist. The guilty parties are scrambling, they know who they are.
There are plenty of examples out there of software which has gone too far with adding new features. AOL comes first to mind. I don’t remember any new version of AOL being that much better than AOL 3.0. In fact one of my first posts at this blog was about AOL’s upgradeitis although I didn’t call it that back then. I’ve written about upgradeitis over the years but it’s like that bad penny that keeps returning.
I think Wordpress, another example, succumbed to upgradeitis roughly two years ago. Sure, the new x.xxx design looks better but enough already on tweaking and tweaking and retweaking the interface. You have a mature plugin structure, why bother? Give it up folks, it’s a freaking blog client, not an old car worth restoring. And all these new tweaks seek to introduce old security problems. A friend’s comparison this morning: “WP is becoming like MS security patches.” So true.
And then there is Word. Good old Word. I think this word processor ceased needing new features somewhere around 1995 and challenge readers to point to an absolute must have feature that Word 95 didn’t have that Word 2007 has. Another friend of mine who has been a professional printer for 20 years was so disgusted with the new ribbon interface in Word that when he got a new computer he downgraded back to Word 2003.
That’s probably a good sign that your software has reached upgradeitis status, BTW: when the downgrading begins. Now let’s make a list since everybody loves lists.
10 signs you should stop upgrading your software … WHEN …
- … you think it’s time to change an established interface design
- … users start downgrading
- … you think users are bored of your software
- … you are bored of your software
- … sales are down
- … the competition upgrades
- … you want to add a feature that has little to do with the core function of the program (hint: optional plugin)
- … the year changes
- … it’s been too long since the last upgrade (hint: optional plugin)
- … there is a full moon out
Exceptions abound
There are always exceptions like Turbotax which is a good example of software that needs to continue to be updated. Why? The tax laws are constantly changing. This changes the core function of their program and they must upgrade. But if the tax laws don’t change and they simply want to add new features to an already feature-laden program? Stop already.
Have to give credit to a few good developers out there like Dave Winer who seem to understand there is a lifecycle to software. That it’s neither prudent nor wise to kick a good thing in the eye or keep poking the dead hunting for one more smile.
Did this post make you go hmm?
(Hmm, no ratings yet)
Loading ...Maybe Related Posts (plugin generated)
- The looming danger of bloatware
- Wordpress 2.1 includes autosave for drafts
- Academic or “anemic” software?
- Wordpress and TypePad add ‘widgets’
- AOL 9.0 Optimized BETA now available
- Tablet PC ignored in Word for Blogger plugin?
So true. Usually goes hand in hand with “featuritis” — loading the application with so many bells and whistles that the new user can’t even figure out how to use it.
When it comes to adding new interfaces — even if your users demand them, many other users will want to stick with the old. If you have to revolutionize it, make sure the old interface remains an option.
Comment by Sterling Camden — August 13, 2009 @ 3:09 pm PST
Another vote for So True.
I don’t want bells & whistles when it comes to software I need to count on. And, like you said, if you need to tinker with it, the old interface should remain an option. Like Word 2007. Although it might work for some, for others (like me) it totally stinks. Microsoft has an area on their site where they have an interactive guide for showing people how to locate and use things in Word 2007 by comparing where the features were in Word 2003. WTH was 2007 necessary if you need to use an interactive guide to figure it out by showing where the features are located with a 2003 comparison—this is one wheel they didn’t need to reinvent.
Comment by Janine — August 14, 2009 @ 6:26 pm PST
I heartily agree with everything except point number one, sometimes it is necessary to alter the user experience to accommodate new data or features you have recently integrated!
Comment by Nuri — August 17, 2009 @ 11:51 am PST
Must say unlike the above commenter I feel that if it ain’t broke, why mend it. The serial upgrades just seem to me to be a ploy to monetize something. If not the software itself then other products that are related
Comment by Ami — September 12, 2009 @ 7:00 am PST
Very true. As a software user and having a 3 year-old laptopt, I am very resistent in making software upgrades on it, because I know that the new versions were made for higher systems and will likely slow down my system. In the end, I think it comes down to the user to weigh down the pros and cons of upgrading, taking into consideration the limitations of his/her software and hardware and if there is a genuine need to upgrade.
Comment by amy — October 15, 2009 @ 5:07 pm PST