Users hate your app's awful UX
-
A study sponsored and released by mobile enterprise app development platform Kony today indicates that if users hate your app, it's probably more about the look and feel than it is about functionality.
Sorry, thought you should know
-
A study sponsored and released by mobile enterprise app development platform Kony today indicates that if users hate your app, it's probably more about the look and feel than it is about functionality.
Sorry, thought you should know
-
Appearance is everything, content is nothing. Welcome to the 21st century, the age of Celebrity :rose:
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
Well, if an app provides just a few functionalities but works flawlessly it is a good app indeed. On the other hand it may have all the functions in the world but if it causes massive amounts of swearing, threats to the phone and so on then it is not. It is mainly the philosophy behind the standard microtools of Unix, like grep, sort, uniq... they do 1 thing and they do it well.
Geek code v 3.12 GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++* Weapons extension: ma- k++ F+2 X
-
A study sponsored and released by mobile enterprise app development platform Kony today indicates that if users hate your app, it's probably more about the look and feel than it is about functionality.
Sorry, thought you should know
It is very easy to fix... On the first presentation remind the audience that the UX design by the best designer studio (name one distant)...In my experience that improves the feedback a hundred times...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
Appearance is everything, content is nothing. Welcome to the 21st century, the age of Celebrity :rose:
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
It's all great if your app can do everything the user needs to do, but if a user can't find which buttons to press to make it work the app is as useful as a bucket full of lemurs on the Eiffel tower (yes, that's not very useful indeed).
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
} -
It is very easy to fix... On the first presentation remind the audience that the UX design by the best designer studio (name one distant)...In my experience that improves the feedback a hundred times...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
All too sadly true. The 'expert' from another city is always much more clever than your own developers. :sigh:
TTFN - Kent
-
It's all great if your app can do everything the user needs to do, but if a user can't find which buttons to press to make it work the app is as useful as a bucket full of lemurs on the Eiffel tower (yes, that's not very useful indeed).
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
} -
Appearance is everything, content is nothing. Welcome to the 21st century, the age of Celebrity :rose:
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
Nah. Not the same issue. Usability seems to be the last concern of a great many developers, and it's apparent in the absolute crap they produce.
-
A study sponsored and released by mobile enterprise app development platform Kony today indicates that if users hate your app, it's probably more about the look and feel than it is about functionality.
Sorry, thought you should know
I did a demo on a new application I developed a while back. The customer needed to use it in an environment where mouse and keyboard are available, but not very practical (due to dirty work/dirty hands) and so the entire application was build for a touch screen, big buttons, big textboxes, everything big to support a dirty- and fat-fingered, touch, factory environment. I gave the demo in a room where I didn't have a touch screen. The user hated it, said the application looked as if we went 10 years back in time! Of course I wasn't thrilled to hear that! So this is kind of how the conversation went. Customer: "I don't like how this application looks. Everything works with touch nowadays, phones and tables, and you're still using a mouse, its as if we go back 10 years in time!" Me: "But you'll have a touch screen in production environment..." Customer: "And will that work?" Me: "Yes." Customer: "In that case it looks very nice, I was just afraid I had to use a mouse!" Apparently the big UI (which looked like other applications they were already using) didn't ring a bell. Also, using a mouse is so 2004... Users... :sigh:
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
} -
I did a demo on a new application I developed a while back. The customer needed to use it in an environment where mouse and keyboard are available, but not very practical (due to dirty work/dirty hands) and so the entire application was build for a touch screen, big buttons, big textboxes, everything big to support a dirty- and fat-fingered, touch, factory environment. I gave the demo in a room where I didn't have a touch screen. The user hated it, said the application looked as if we went 10 years back in time! Of course I wasn't thrilled to hear that! So this is kind of how the conversation went. Customer: "I don't like how this application looks. Everything works with touch nowadays, phones and tables, and you're still using a mouse, its as if we go back 10 years in time!" Me: "But you'll have a touch screen in production environment..." Customer: "And will that work?" Me: "Yes." Customer: "In that case it looks very nice, I was just afraid I had to use a mouse!" Apparently the big UI (which looked like other applications they were already using) didn't ring a bell. Also, using a mouse is so 2004... Users... :sigh:
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}My situation exactly - in food manifacturing plants you must have resistive touchscreen to cope with gloves, and BIG buttons to accept gloves designed for industrial freezers. Also we must account for daltonism so the choice of colours is reduced. Furthermore, due to the first designs dating 1996 we are stuck, for stock compatibility, to 1024x768 pixel. Hellish, but every customer praise us for the ease of use - much less for the setup which is almost arcane :D
Geek code v 3.12 GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++* Weapons extension: ma- k++ F+2 X
-
It's all great if your app can do everything the user needs to do, but if a user can't find which buttons to press to make it work the app is as useful as a bucket full of lemurs on the Eiffel tower (yes, that's not very useful indeed).
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}:thumbsup: /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
