14 ms·
My pet theory is that every software product has a "peak version". Before that peak version, the product is not yet in a complete state, and it is fairly obviou
by flohofwoe 7y ago
My pet theory is that every software product has a "peak version". Before that peak version, the product is not yet in a complete state, and it is fairly obvious, both for the developer and user, what features are missing. Once the peak version is reached, new features are not added because they improve the product, but to justify selling the product again to existing customers, and to 'keep the team busy'.
Instead of really improving the product, features become checkboxes on the roadmap. Which eventually results in degrading the quality of the product, it becomes bloated, the UX becomes confusing (especially to new users), and existing features start to suffer because the "maintenance surface" becomes bigger and bigger.
What should happen of course is that the product's feature set is frozen at the "peak version", and only bug fixes and optimizations are happening, that's a hard sell to the bean counters of course, especially with subscription models and "software as a service" which they like so much. From the customer's point of view, bug fixes and optimizations are expected to come for free, because they are fixing defects in the original product and don't add any value, right?
Eventually progress and success is measured in features added, not in satisfaction of individual customers. And as long as KPIs are looking alright - meaning the 'average customer' (which doesn't exist btw) isn't pissed off enough to look elsewhere, all is good, even though everything is terrible.
- dade_ 7y agoThere should be an award of shame for this and I nominate Visio 2003.
- Finnucane 7y agoWord for Dos 5.0. If you are old like me, you may remember thinking this was a pretty good word processor, and when Word 6.0 came out, it seemed a bloated mess in comparison. It's been downhill ever since. Mac OS X 10.6.8. It was good, and stable, and nothing that has come after has really added value to the product.
- vbezhenar 7y agoiOS 6. I'm using latest iOS and the only useful feature for me is fingerprint recognition and that is more about hardware. They added tons of new features but I wouldn't miss any of those features.
- overcast 7y agoPassword manager integration is a pretty monumental feature I couldn't live without.
- UIZealot 7y agoAgree on iOS 6. For me it's not that the later versions don't offer good and useful features. It's just that I'm disgusted everytime I have to look at that god aweful UI. Jonny Ive truly has no taste.
- NeedMoreTea 7y agoThey've also added a whole load of negative features, or needless complexity, and taken away the helpful in the name of fashion. Maybe I liked coverflow. Or an analogue clock on the lock screen. Maybe I liked big album art on the lockscreen when playing music instead of the absurdly tiny thumbnail of now. Snow Leopard, iOS 6, Word 6 (or 2003 if we have to take the modern era), all seem easy choices, yet the companies doing it never seem to notice they jumped the shark. Dropbox 10x the size with built in messaging anyone? Thought not. :)
- gurkendoktor 7y agoSwipe to go back is one of the unexpected improvements in iOS 7 that I think many people would immediately miss when going back.
- asark 7y agoThey've added new features I like, but that was the sweet spot of discoverability and aesthetic. It's been downhill since. I'm also not loving making it a more general-purpose OS—the iPad/iPhone as a slab of metal & glass that could become any of several tools, with a no-BS operating system keeping it all coordinated, was what really made it special.
- UIZealot 7y agoAgree on Snow Leopard. I don't even mind later versions not adding value. What's sad is, they added negative value. It got slower, buggier, and uglier with every update.
- yoz-y 7y ago> and nothing that has come after has really added value to the product For you. Personally to me things like cross device copy-paste, airdrop, notes and reminders integrations are indispensable now. Metal has brought a huge improvement to rendering speed and of course security between now and then is incomparable.
- agumonkey 7y agoFunny because Word 6 is often praised as perfect balance. Or maybe I read wrong
- Crinus 7y agoSince we're playing that game, i nominate Paint Shop Pro 7 :-) There are very few (and minor) things i'd change about that software and apparently its developers thought the same because the biggest change they did after that was to change the program's theme (in general i think when a commercial program has ran out of important stuff to add the next thing they do is to change the program's theme :-P). Also Delphi 2 and C++ Builder 1. I refer to the IDE there (they're essentially the same IDE except one uses Object Pascal and the other uses C++), not the language (as a language the ideal would be Delphi 7 with some functionality from Free Pascal like dynamic arrays and generics). The only thing i like from later versions is the inclusion of auto-completion, but beyond that (and especially after Delphi 7) there is way more bloat than good. And MS Paint up until the Vista version. The only thing it needed was a tool to draw arrows. I curse the Win7+ MS Paint every time i want to draw overlapping rectangles or a rectangle and then something else. Also WinHelp, whatever was the last version was fine. This didn't "fall from grace" as much as it was outright killed. CHM/HtmlHelp is nice (everything else that Microsoft has produced on the help front sucks) but the ability to add CSS and JavaScript on it means that many programs do add CSS and JavaScript (though TBF authoring WinHelp shows that it is a hacky hack of great hackiness, but i'm referring to the overall UX as a user, not author). And of course WinAmp 2.95, i do not think this needs explanation :-P Finally i think Visual C++ 6 (with the addon to add tabs) is the best VC++ version - again about the IDE, not the language. Though overall i prefer Borland's C++ (C++ Builder, Borland C++) mainly because the compilers are much faster (and i do not use C++ much to care about any missing features). On the Linux side the last version of Xpdf to use Motif was the best Xpdf, GNOME2 is the best GNOME and Gtk2 is the best Gtk. Though Gtk itself is lousy, the only reason to use it is for GNOME.
- DougN7 7y agoKeeping bean counters shouldn’t be the goal, but everyone does like to keep eating. What do you suggest for keeping the business healthy while not making things terrible?
- flohofwoe 7y agoI don't have a solution of course. We need a revolutionary idea like the "subscription model for software", but for user happiness, maybe there's a middle way which doesn't end in poverty for the software developer ;) UX designers leaving their ivory towers to get an idea how the real world works would be a good start. Somehow we managed to turn the positive idea of an "update" into something most users are hating.
- snegu 7y agoI assure you that UX designers (the real ones, at least) would love to get out of their ivory towers. In every job I have had, I have begged to get out and talk to users before doing anything else. However, that idea makes folks in charge nervous. It's expensive. It might reveal secrets(?). The users might get annoyed. One of the biggest issues is that time spent on research is time when the developers can't be developing. That seems to trump everything.
- reitanqild 7y agoI don't know. IIRC UX people here on HN has told me Ribbon was a perfect example of UX design done right: they tested it on users and chose the easiest one. Yet the first version of Ribbon released with the most important menus hidden behind the round logo in the upper left corner. You are probably a good ux designer, but in general, modern ux designers cannot be trusted ;-)
- tabtab 7y agoDon't forget that Pointy-Haired Bosses often stick their finger into the pie the last minute. You can't always blame the designers.
- mrunkel 7y agoThe problem with your theory is that "peak version" is different for every user of the software.
- diggan 7y agoThe solution is that every deployable version of the service should be usable on it's own and users should be able to chose exactly what version they are locked on to. Or they can choose to live on bleeding-edge and always get the latest updates. Wishful thinking maybe
- vbezhenar 7y agoIt's called long term support. And it's not cheap.
- flohofwoe 7y agoThere's a big difference between offering "end-of-life" versions for download, even if they are no longer supported, and forcing users on new versions even if they don't want to (which is fairly common for mobile/web apps and generally subscription-models like Adobe and Autodesk switched to).
- vbezhenar 7y agoThat's because the world decided to adopt software as a service model, where your device is just a thin client and real work is happening on a server. And that model is incompatible with letting customers to run old versions.
- TeMPOraL 7y agoI.e. exploitation pure and simple - delivering value to customers is incompatible with company exploiting those customers. This deserves as much pushback as possible, even though it seems like a quixotic effort.
- 7y ago
- collyw 7y agoThank god Linux gives you multiple desktop options. I am happily using "Windows 98 style" XFCE. To be fair there probably hundreds of subtle improvements over Windows 98, but no horrendous game changers like when Ubuntu went from Gnome to Unity.
- noir_lord 7y agoCinnamon feels like XFCE's conceptual descendant, it doesnt break the desktop metaphor at all from win98/XFCE while having enough of the newer stuff if you want it. It was what I used until recently and would go back to in a heartbeat.
- gurkendoktor 7y agoNot only Linux. Many people praise Apple for its radical "game changers", but I mostly use macOS because they haven't broken my workflows or muscle memory in the last thirteen years. It's a miracle in the world of commercial software, and it probably won't last as long as XFCE.
- yoz-y 7y agoSubscription model is actually way better if you don't want to end up with feature bloat. Because you actually get money from users even if you only ever fix bugs and improve performance. If you freeze your features you will soon arrive at a point where everybody who wanted your software bought it and then the revenue stops.
- Insanity 7y agoUnless you have competitors and they offer (niche) features that you suddenly want as well.
- yoz-y 7y agoDepending on how small the niche is you can sacrifice a small amount of users if they switch to keep the code simpler. Also it's not like the model prevents you from adding features. But it gives you more freedom to pick the ones that make the most sense to implement because you do not need to constantly chase new users.
- PeterisP 7y agoOnce you get to the point where pretty much every new feature serves just a niche, plugins are the solution. If need one of a hundred niche features, it's great to have software that has it, and it's also really great to have softare that doesn't have the other 99 features; it's better from usability perspective if they don't get automatically added for me.
- NowThenGoodBad 7y agoJust like Microsoft Excel. Unfortunately, Microsoft backpedalled between 2011 and 2016 versions (those are for Mac) and removed a significant amount of functionality. Files closed with the application no longer reopen, UI elements are gone, and, worse yet, you can't completely customize all of the possible keyboard shortcuts any more, you can't even find access to them. To my understanding, this was for 2 reasons (excuses): 1. Some OS changes Apple made* 2. To push people to subscribe to office 365 and "gain" that functionality * I paid full price for both 2011 and 2016 (and the corresponding windows office copies). 2011 still works on the most recent macOS with all of the functionality. So, claiming that Apple did something to make the feature of automatically reopening the documents you had open when you quit broken is bull. Their old version still does that on the new OS just fine (despite that little pop up claiming the software is incompatible...it still works, why not use it?) After buying MS Office with removed functionality, I will sadly not be buying office again. Nor will I be subscribing to office 365, nor will I be supporting it in any corporate ecosystem. The files from the old versions are perfectly fine and when they no longer are, Libre office and (almost embarrassingly) Google docs will have to do. I'm definitely not the only one bailing. My father has been off for many years and, as a principal engineer at a Silicon Valley medical device company he helps others see that we don't need to let Microsoft maintain a stranglehold on us. But, I was happy buying the new versions of office year after year until these most recent changes. Excel 2005 was one of their best versions. That was my subscription model: I pay full price every couple years you put out a new version and, in return, you give me a good, solid product that built off the prior one (or at least stayed damn near as useful) while providing support to that product through updates and bug fixes. Subscription services are already gaining groans from people and we don't need another subscription in our lives. But, to wrap up, back to the point: even though excel (and the other MS Office software) were incredibly versatile already, you still had the option to install the Analysis ToolPak if you needed to work with complex statistics or engineering analysis or even write your own plugins or macros for it, instead of those features overburdening the software and overwhelming the users by "covering all the use cases".
- justicezyx 7y agoThat's basically the ROI curve of software. Beginning: Slow and almost no return. Slow being a lot of intellectual effort to lay the foundation. No return being the foundation does not do anything useful, yet. Middle: Fast and linear return. Building on a sound foundation allow adding feature that is simple and with high quality; and the return is linear to the effort. End-of-life: Slow and almost no return. Bloated software eventually is dragged down by historical burden (tech debt, legacy features, etc.). Massive effort is needed to add feature, and the return is almost painful to stand. A lot of recent software took the approach of forced update to extend the middle life. Like the chrome today is considerably different thing than its beginning. Py3 tries to demolish its historical legacy, and embrace new foundations.
- whatever_dude 7y agoI completely agree and to me this is the "Flash Bones" problem. Despite one's opinion of Flash as a web alternative or its license, it was a great way to run interactive content on a browser, and they kept adding features to their native IDE ("Flash" itself) and capabilities to the player (including the SWF spec). It eventually reached a point where there was not much more to add to it: it could play video (novel at the time) and audio (including live synthesis), use sockets, etc etc, and do some pretty advanced stuff supported by the player/spec. But none of that sold Flash IDE licenses, so they _had_ to add more features to the IDE. One of these features was the ability to do Bones, a pretty common animation feature. To me that's what marked the IDE decline. I used to create a lot of Flash content, but stopped using it at that point too. Not because of bones, but it was symbolic of the moment. I still created Flash apps for years, but it was always by creating fresh, "stage-less" projects, compiled from source code (the right way to go anyway). Bones itself is a great feature, but at the time Flash the IDE was already way behind other animation tools that exported to Flash like ToonBoom. Adding that feature just made it clear that they didn't know what direction to go with the IDE: it wasn't the best animation tool (despite having kickstarted a market!), it wasn't the best dev tool, just a bit of both with very few people who needed both. No surprise it stopped selling even while the platform was thriving online, circa 2010.
- lkrubner 7y agoMicrosoft Word 5.1 on the Macintosh was published in 1992 and was generally seen as the best word processor ever invented. It's UI was perfect. It won a lot of praise in the press, all of it deserved. Sadly, after version 5.1, Microsoft began to focus on the integration of the Office Suite, which meant re-doing all the apps so that they'd be open to programming. And more features got added, and the UI became cluttered. For those of us who sometimes use Word, but don't need the rest of Office, Word 5.1 remains the high point. Also, as others often said, 5.0 seemed like a broken release, and the ".1" was a much bigger upgrade than is normally implied by a non-major-version number. So it is version 5.1, and not version 5.0, that is remembered fondly.
- noir_lord 7y agoOffice has gotten worse for me since 97, they added more and more crap that I didn't need and then put it front and center with a "look at the crap we added you don't need" design. These days I write in markdown and it it has to be pretty format it in libre office (mdpdf works fine for 99% of my uses though).
- Angostura 7y agov.X was pretty nice when OS X came along. Since the, not many improvements.
- Doctor_Fegg 7y agoMacWrite Pro was also released in 1992 and its UI was streets ahead of Word 5.1’s. Unfortunately its performance was laggy and, even by then, Word was so much the incumbent that it was hard to compete. But I loved MWP.
- avip 7y agoCounterpoint: Was generally seen as the best word processor unless you had to use it with an RTL language. In other words, it was perfect for (WORLD.population - 500mm) What's bloat for you may be an essential need for your fellow worder. #funfacts: https://www.zdnet.com/article/microsoft-boosts-languages-proofing-tools-in-office-2011-for-mac-unicode-right-to-left-support-missing/ https://www.zdnet.com/article/microsoft-boosts-languages-pro... https://caniuse.com/#search=dir https://caniuse.com/#search=dir
- habosa 7y agoLike OS X 10.6.8 ... everything was perfect in that version.
- SubiculumCode 7y agoA counterpoint: FL Studio is a long-standing, and much loved software package for audio production. Since its beginning FL Studio has had the following policy: Once you buy the software, all updates are free for life. The counterpoint is that each new version of the software has gotten better and better. Therefore, the purchase of FL Studio license both has fantastic current and future value, and has earned intense customer loyalty and online reputation, generating substantial word-of-mouth sales---like what I am doing right here, right now.
- 3xblah 7y agoThis commment and the OP seem to suggest that if users were in control, they would not change things. They would not add features. They would subscribe to the idea that software is "finished" (save for bug fixes). Can we agree that, realistically, generally users are not in control of the software development process, despite any organisational structures that appear to let users drive it.
- isalmon 7y agoI agree and I think Craigslist is a good example here.
- eeeeeeeeeeeee 7y agoThat definitely happens, but I think a lot of the blunders are due to good intentions with poor execution or not enough thought into the need and demand. Things like adding features to solve a problem, when those problems only affect a small percentage of users, is something I see a lot. Especially in the beginning of a product when you’re not 100% sure what you’re making or who you’re making it for and you want to appease all of your customers so you don’t lose them. Or the feature added is too complex to be useful for a user without training / tutorials, of which few users will undertake that time investment. I have yet to be on a team where features were not trying to directly address a customer issue / complaint, but maybe I’ve been lucky.
- deleted 7y ago[deleted]
- baybal2 7y ago> Instead of really improving the product, features become checkboxes on the roadmap. Which eventually results in degrading the quality of the product, it becomes bloated, the UX becomes confusing (especially to new users), and existing features start to suffer because the "maintenance surface" becomes bigger and bigger I side with you 100% on that The meme about software being an act of non-stop bicycle reinvention has never been more true to life than it is now
- m463 7y ago> new features ..."add value" My theory is MVP is what they ship, then it's about the monetizing.
- jv22222 7y agoOne might argue that some SaaS product teams hold back adding new features almost to a fault. Basecamp and Sifter come to mind. Edit: I know more about Sifter than Basecamp. I login to Basecamp every few years and it seems like not too much has changed to my untrained eye, but maybe they did stuff under the hood. For sure I know that Sifter got to what they considered peak features and stopped.
- duxup 7y agoI fear that peak often comes before many companies are profitable.
- KajMagnus 7y ago> the product's feature set is frozen at the "peak version" And then youa add a plugin and extensions API, so people can continue adding features, without annoying anyone — although the product is "frozen". Isn't browser like FF and Chrome an ok example of this b.t.w.?
- russdpale 7y agoI cannot help but chuckle at that last paragraph. Well said sir. Well said.
- johnchristopher 7y agoI was thinking something like that when changing some settings in Visual Studio Code this week-end. Before version x it was just a json file, now there's a GUI that wraps up that json file in a bunch of drop-down menus. I have like 5 settings in the file but the menus make it look like I am playing flight simulator or something. Thankfully I saw the curly brackets button and I can still edit the file manually :).