4 ms·
I like the main idea here, but the points listed are a bit extreme. Specifically this one: > should never update a user interface without allowing the previous
by viraptor 6y ago
I like the main idea here, but the points listed are a bit extreme. Specifically this one:
> should never update a user interface without allowing the previous one to be used as the default
Are you ready to pay for the ongoing support of all legacy interfaces, including the ones you're not using and which are possibly not used by anyone in the world (no telemetry)? Are you ready for all the bugs and security issues this will cause?
Same goes for support of old file formats.
- cgrealy 6y agoCompletely agree about interfaces. File formats should be supported though. At the very least, I should be able to import a file from the old version and have it converted.
- dt3ft 6y agoIf you pay for your software through a subscription, of course, no problem. You paid for software once? Well, tough luck. Your older versions will no longer be supported because we can't afford developers because you stopped giving us money. There is no way anyone is going to be supporting old formats while providing free updates. This makes no business sense.
- cgrealy 6y agoThat very much depends on the license. Many licenses include future updates. I am far more likely to pay for software that supports file formats in the future.
- dt3ft 6y ago> Many licenses include future updates. May be so, but likely not in the long run. Developers don't quite want to work for free, and providing free updates is a bad business model if licensing model is "one time fee". They may say "free updates" to lure you in, but updates are only provided for your version. As soon as a new major version comes out, your current version will stop receiving updates. You will have to upgrade to the latest version at some point, and this upgrade is definitely not going to be free. You get what you pay for.
- tpxl 6y agoWhen updating from one format to another, you should generally write code to convert it. Once you have that code, it should be trivial to update old -> new format by using all the intermediate software versions, or not as trivially, you can have a transformer from all previous versions to the current in your latest releases.
- anchpop 6y agoI think they mean that you only have to support the most interface besides the new one, not every single version
- viraptor 6y agoThen if you get 4 updates in a row that are: UI, security, UI, security, you have to choose which one you care about more.
- bobbylarrybobby 6y agoWell then for people using the previous version of the interface, updates still force them onto a different interface.
- qu4z-2 6y agoI took that restriction to be specifically for automatic updates, and I agree. Don't break my workflow without my consent.
- wwweston 6y ago> Are you ready to pay for the ongoing support of all legacy interfaces Part of the problem here is that software companies don't seem to ever ask this question in good faith (and of course, don't even realize that at an institutional level they don't actually care because common incentives for product and UX people are towards changes they can take credit for). Try setting up a system where people can in fact pay for earlier UIs. See what happens. (Term "earlier" used deliberately over "legacy", because it's only "legacy" if it's abandoned by either users or owners.)
- dt3ft 6y agoIt took a while to find a comment that points out the cost of maintaining legacy UI. It is highly likely that no customer is willing to pay for support of legacy anything, let alone UI. "Jonny" sounds like the kind of person that wants to purchase software at a one-time cost, and then expect free lifetime upgrades (which include all the outrageous demands such as supporting legacy UI). Make your own software Jonny, see how that works out for ya.
- blub 6y agoThe legacy UI often works fine and the new UI's sole purpose is to justify the salaries of the design department. Ask any customer if they're willing to pay for a new UI and you'll likely find that they don't.
- viraptor 6y agoIt depends on a question though. "Do you want a UI redesign?" will likely be a no. "Do you want to access the thing you're using 100 times a day in 1 click rather than 5 menus?" will always be a yes. Unless the company is completely failing at its strategy (and that's not the same thing as many vocal people saying that on the internet forum), the redesign has goals and some reason behind it. Your "worse" may be solution to someone's ongoing problems.
- dt3ft 6y agoWe tend to underestimate the value that a decent UI/UX professional can bring to a software product. Users typically hate changes (change aversion is in the human nature) and will hardly notice any improvements. But try to install an older piece of software, say, Microsoft Word 97 and compare usability to the current version. Don't pick one feature, look at it from a daily usage perspective. I bet you'll find a ton of improvements and think "huh, I had no idea it was so painful to work with Word 97"...
- out_of_protocol 6y agoActually launched Word97 recently. Surprisingly good UX, at least for simple documents
- Legogris 6y agoMaybe if the "move fast and break things" attitude coupled with CD wasn't as widespread, breaking UI flows wouldn't be seen as part of the weekly routine. There are absolutely situations when changes are warranted but I really think it's a mistake to see Google Cloud and FB as sources for inspiration wrt this.
- txutxu 6y agoIf the UI is changed to fix "bugs and security issues", I'm perfectly fine. If the UI is changed: * for no reason (other than justify the salary of the designers team) * just for the sake of "give the impression of evolution", but really it's just hiding or moving buttons and menus and changing font sizes, colors, layouts... * or to intrusively insert new and unrelated products, in the middle of the original workflow * or to remove (or change) basic and intrinsic product functionality * or to prevent to continue the (intended) workflows acquired with previous usage then I'm not so fine... anyway, what is mentioned is just that automated updates (and this does not apply to web applications I think), shouldn't do that change, without an "option to stick to the previous" UI. At least in minor version updates, I totally agree. Edit: format and verb tenses
- dbsmith83 6y agoBetter solution: make the UI modular and configurable so the user can choose the layout For file formats, updates changing file scheme need to be backwards compatible