2 ms·
My rule of thumb for adoption UX is: every step roughly halves the number of people who will complete the process. So a 10-step install means that if a million
by api 9y ago
My rule of thumb for adoption UX is: every step roughly halves the number of people who will complete the process.
So a 10-step install means that if a million people discover the app only about 900 will get it running.
As complexity and general noise increases this effect will become more pronounced. People just do not have time for time-consuming installs. The information age is the age of distraction and so if something takes a lot of time "plonk" into the trash it goes.
There are ways to secure things with decent UX. At the very least the defaults could allow direct access only from private IP ranges and require explicit configuration to set otherwise. This would prevent people from shooting themselves in the foot this way.
- jlgaddis 9y ago> People just do not have time for time-consuming installs. I have two quotes printed on the back of my business cards. One of those is: "If you don't the time to do it right, when will you have the time to do it over?" I remember hearing something to the effect of "temporary setups never are" and, in all but the most disciplined environments, I've generally found that to hold true.
- mavhc 9y agoPeople dealing with masses of data should find it hard to make it accessible, security isn't easy, you should have to learn what you're doing. But also there should be no way to get it working insecurely. Should just refuse to run until everything is secure, data limits, timeout limits, retry limits, ip limits, account limits, password complexity, etc.