6 ms·
Getting even more to the point: why does an installer even need to use Silverlight to render a progress bar!?!? As far as I know, these things have been there s
by userbinator 8y ago
Getting even more to the point: why does an installer even need to use Silverlight to render a progress bar!?!? As far as I know, these things have been there since 16-bit Windows and continue to work fine in Win10:
https://docs.microsoft.com/en-us/windows/desktop/controls/progress-bar-control https://docs.microsoft.com/en-us/windows/desktop/controls/pr...
- jcelerier 8y ago> continue to work fine in Win10: putting the head in the sand like this won't make the problem go away. UX designers demand stuff that is smoother than win32 progress bars, that has spline-interpolation-like behaviour with some nice little tween at the end when going to the next page, with varying smooth color gradients all over the place. go make this UI with pure Win32 primitives : https://youtu.be/v0GG8uh80V4?t=158 https://youtu.be/v0GG8uh80V4?t=158
- rkagerer 8y agoI hate animations like that. All they do is distract me, waste my time while I'm waiting to see and interact with the next thing, and move my target out from under me while I'm trying to go click it. I always turn off all the animation settings right out of the box. I wouldn't be surprised if one day soon this fad gives way back to a renaissance of clean, simple, instant UI's and everyone will feel like their devices got a lot snappier.
- phailhaus 8y ago> I wouldn't be surprised if one day soon this fad gives way back to a renaissance of clean, simple, instant UI's and everyone will feel like their devices got a lot snappier. No, don't think so. Instant UI's are disorienting because there's no visual cue for what is about to happen, and they don't give your brain an intuition as to how the interface behaves (e.g. a sidebar slides in from the side rather than the top). We're used to instant UI's because we've learned the patterns over time, but they're very unnatural to new/ocassional users. Some interfaces overdo the animation timing though, they can be very fast and still give users enough of a cue to understand what happened.
- Retric 8y agoAnimations that change colors within a narrow range are fine, moving UI elements around is a huge anti pattern that annoys users without any benifits. It’s the same issue as flat buttons, users need to know what’s clickable, and what has been clicked. They don’t need shading etc, but feedback has masssive utility. Sadly, our field generally lacks the kind of real feedback that corrects such incompetence.
- phailhaus 8y ago> moving UI elements around is a huge anti pattern that annoys users without any benifits. Still disagree, and I think you're thinking of really obnoxious examples. I'm imagining about a ~150ms animation for the following: 1. A sidebar sliding out from the side 2. Dialogs swooping in and out from the top of the screen 3. Form panes sliding out when replaced These quick, almost-no-time visual cues are incredibly important at giving your interface a sense of presence and physicality. Without them, your UI elements are flickering in and out of existence without any perceivable reason, and can often leave the user wondering what changed.
- Retric 8y agoThat still just adds perceived lag to the system slowing people down as you can’t read something that’s not yet rendered or sliding around that quickly. 150ms adds up. “Why did this get so slow?” Is a real and common complaint with such changes and why OS’s allow people do disable so many animations.
- phailhaus 8y agoThe "why did it get slow" complaints happen when the animations aren't fast enough. The brain doesn't need a lot of time to register motion, but many times designers will use a slow and laborious animation to really emphasize something appearing. See Google's material design: it is based on the philosophy that interfaces should behave physically, and you'll see that it feels incredibly snappy. Check out these demos: https://material.io/design/motion/speed.html https://material.io/design/motion/speed.html Example: you can't effectively convey a menu becoming a button without an animation. Without an animation, the menu disappears and a button appears, but there's no reason to believe that they're related. A 100ms tween from one to the other is all you need. Our brains are very good at relating motion, not objects blinking in and out of existence.
- jcelerier 8y ago> I wouldn't be surprised if one day soon this fad gives way back to a renaissance of clean, simple, instant UI's and everyone will feel like their devices got a lot snappier. facebook introduces artificial delays in the loading of their stuff because people wouldn't believe that it actually works when it is too fast
- GoodDreams 8y agoSimilarly travel booking sites add an artificial delay otherwise travelers don’t believe the site tried hard enough to find the best deals.
- corysama 8y agoTurboTax Online is just an hour long series of delays to give the impression that server farms are struggling to do work that could be handled instantly by a Commodore 64.
- bradstewart 8y agoWow. Do airlines do this as well? I literally will not fly American Airlines anymore because their website is so unbearably slow when looking for flights (not that United or others are much better).
- calcifer 8y ago> UX designers demand stuff Really? Demand? This is an installer that you will see maybe once a year, probably not even that. You will forget everything about it the moment it terminates, so why not use the default progress bar the OS provides and call it a day?
- phailhaus 8y agoThe installer is the first impression your user will have of your application.
- sid- 8y agoAnd that hanging leaves a great impression :)
- fredsanford 8y agoThen most companies have impressed on me that they hire chimpanzees to design/code Windows installers and the like.
- userbinator 8y agogo make this UI with pure Win32 primitives I happen to be both a demoscener and Win32 programmer, so I know exactly how to do those sorts of effects without bloat. That doesn't mean I necessarily advocate doing it, however. It's ironic that you mention fancy progress bars, when the ones in the VS installer are even less fancy than the built-in OS ones. 2 colours, no 3D border, not even a gradient. One of my annoyances is applications which reinvent standard OS controls and UI. The OS has (or unfortunately, more like had these days... but that's a different rant) theming and customisation capabilities for a reason. Don't try to be different just for the sake of being different, you'll stand out and not in a good way. It's an accessibility issue too: what happens when your custom-rendered UI is run on a system where the user has configured a custom colour palette (because he/she is colourblind, or just finds some colour combinations easier to use)? The OS UI widgets all have a consistent style and change all together, more than can be said of custom UIs. (In applications like games, it often makes perfect sense to build a custom UI because it's part of the gameplay experience; but for a productivity application, a custom UI just gets in the way.)