3 ms·
Please only apply "conversational design" to the few places where it's appropriate. I recently tested an app that had a study section. But instead of presenting
by FabHK 6y ago
Please only apply "conversational design" to the few places where it's appropriate. I recently tested an app that had a study section. But instead of presenting the requisite knowledge the conventional way (text, maybe a video), they went all cute and "conversational" and put it in fake-messenger speech-bubbles...
App: "Would you like to learn about <...>?"
Me (exasperatedly typing): "yes"
App: "Bla bla 1"
Pause, "typing" animation...
App: "Bla bla 2"
Pause, "typing" animation...
App: "Would you like to learn more?"
...
Instead of just showing me the information so that I could quickly scan it, they forced me to type "yes" or "continue" every so often, and then, infuriatingly, fake "typed" the answers out slower than one reads, so that one had to wait for the stupid app.
I've deleted it.
- throwaway_pdp09 6y agoWhat's so peculiar about bad interfaces like that you've described is how it's so utterly obviously not up to the job. It's like looking at certain websites and saying "I can't read this". My energy supplier prints bills with some info in very light grey on white - I literally can't read the text, it's so obviously inadequate, but every day another thousand below-par websites/GUIs/whatever are churned out by people who not only don't understand UIs/websites, they can't detect the most fundamental, evident, basic flaws right in front of them.
- FabHK 6y agoAnd, in many cases, it's even extra work to make it worse than the simple default...
- throwaway_pdp09 6y agoHeck yes. Don't just display the information, let's instead un-fade into visibility so the users have to wait... Good point. NB. these stupidities are a lot harder to do without jscript, which is another reason I'm against js.