I would like to share in this post one of my conclusions based on the projects experience.
It is very common situation when something can be done in more then one way. For example, you can have List screens where some lists of items are shown. And you can have a small feature there: search by the item name. There are at least 2 distinct ways how you can design the interaction:
- User types in a part of name and then clicks some button or icon. Search is applied then.
- User types in characters and as he types the list is continuously being filtered
The question that will definetely appear at some moment is which alternative to follow.
Some people can just not notice this fork and will implement some default solution. This way is not good since there is 50% probability that your users will ask you one day “Hey Jack, why didn’t you choose the other way?” and you’ll need to redo.
If you are more smart you will smell the fork and will ask your customer beforehand: Hey John, how would you like this to work?
That will work but still this is not the best solution.
The best one is to have in your application 2 similar List Screens and implement one way on the first screen and the second one on the second. Then leave it as it is. Let the John-the-Customer touch it, play with it and he will come to you one day and select the solution fitting his needs the most.
You may think there is something wrong with such approach, a need to do double-work, but it is easy to smooth out everything when you have different versions. It actually degrades the probability of those 50% when John ask you reimplement the stuff in absolutely different way.
To sum up the bullshit above: consistency always wins the battle through the powers of choice
Recent Comments