|
|
|
|
|
|
by michaelt
822 days ago
|
|
|
Honestly I've never understood any sort of software update or new user guide or changelog appearing when the user starts the software. You know why I've just launched this game in Steam? Why I've just opened this shared meeting whiteboard software? Why I've opened my bank's banking app? Because this is the moment I want to use it. If I open Skype it's because I need to be on a video call within the next 15 seconds. It doesn't matter what the popup says or does or how valuable it might be - I'm dismissing it, because I need to be on a video call within the next 15 seconds and it's between me and that. How could a UX team possibly conclude that the precise moment a user shows unambiguous intent to use your product, is the best time to get in their way? |
|
|
Well, the most natural answer is that it's not a UX team. It's the software engineers observing that since our program isn't running all the time, this is the moment we have to check for things.
And roll around that design issue a few more times and that's why your computer is running upwards of dozens bespoke programs that do nothing but scan for updates periodically and consume surprisingly large amounts of resources to do it since apparently most programmers can't write a program to try a network request every couple of days to consume anything less than a gig of RAM and 25%+ continuous CPU.