Don Norman has an interesting article saying simplicity is not the answer. Quite true, especially because nowadays simplicity is getting dangerously trendy. I believe the right balance of functionality and simplicity also depends on the user’s profile and needs. [Continue]
I find a lot of confusion around the two phrases - simplicity and quick to use. I find people replacing one by the other and trying to judge a tool’s design. Is every simple product quick to use? [Continue]
In what aspect is Linux is better than others? It is flexibility, according to Linus Torvalds. I think the real strength of Linux is not in any particular area, but in the flexibility. [Continue]
As I am reading more and more about Vendor Relationship Management, I am convinced that our future is going to go in the direction of more control and personalization for you and me, the user. But this also means that we will have to learn more, to be able to really convert the control and personalization into higher productivity. Simplicity is dependent on our perception, which is a function of our knowledge, experience and skills. [Continue]
Luke Wroblewski notes down points from Jared Spool’s talk about what makes design intuitive. There is a lot of overlap between simple and intuitive designs. An identity trait of an intuitive design is to directly talk with the user about what to do with it. [Continue]
How many solutions can be there for designing a simple data table? Luke Wroblewski illustrated the process of redesigning a simple data table. The design should facilitate communication, not overshadow the actual data with visual and data design. [Continue]
Jeff Atwood cites various instances of user interface friction. Any aspect of the UI design that makes its usage inconvenient and complex causes friction. Most of the times I have seen that it arises not because of lack of thinking, it is wrong automation. [Continue]
I have written a lot about abstraction. I also think that it is something at the root of design, at the root of understanding something. There are various benefits of abstraction. [Continue]
Adam Bosworth explains why some software works and some does not. He brings it down to two basic factors - Physics and Human Psychology. It does sound pretty abstract, but he elaborates it further by specifying that success of software has always required a faster hardware technology. [Continue]
Mike at Techdirt writes if the programmer takes the blame for not being a user, make the user a programmer. It is quite true that software gets hurt if it is not developed for usage by the user. It is natural that the creator and the consumer always think about different things. [Continue]