Visually Designed Software

As I continue to look around, work and consult for various companies, I have begun to realize that the visual
element of software design in perhaps more important than functionality. Humans are visual beings, we like
nice furniture, nice buildings and beautiful people. The same is true of software.

The recent success of the iPhone is an example, Apple makes attractive devices that have attractive user
interfaces. This I believe is the key to their success. Years ago, we all put up with Microsoft, not because their
software was robust, efficient or reliable but because they had the best user interface by far. As mentioned
in a previous article, Linux is now maturing into a desktop operating system that can finally compete with Microsoft, this is mainly because the user interface is attractive. The new Gnome and KDE windowing user interfaces are easy to use and attractive.

The same can also be said for web development. I believe it is more important to have the user interface
looking excellent, before working on the functionality. Some may argue, that simple command line tools are not
attractive yet are used extensively, this is true. the users of such tools, like the interface and are accustomed
to it. It is textual, too the point and uncluttered. Again, it is a particular type of interface, non-graphical however
with its own attraction and design.

I believe that many companies delivering business solutions (via bespoke software or web services), often
ignore this fundamental design principle. People simply get bored and annoyed by ugly interfaces !
Getting the design (visual) right is fundamental, of course then comes the functionality ....

For those interested in some cool visualization ideas, check out IBM's Many Eyes http://manyeyes.alphaworks.ibm.com/manyeyes/

Comments

Post a Comment

Please post your comments, I am interested in your views

Popular posts from this blog

The pitfalls of share options in the technology startup

Draft 1 PLEASE NOTE: I  am a simple engineer and this document should not be taken as legal advice in any way whatsoever.  Please feel free to comment or relate your stories here. All feedback is more than welcome Over the last few weeks I have been involved in trying to get a fair outcome for some options that I have in one of the many startups I have worked with over the years. As I continue to push my case forward I thought I would write some thoughts whilst fresh in my mind.  Many of us are attracted to startups due to the promise of shares or share options in the company we are joining. Many people work at reduced rates or no pay in exchange for these contracts, with the hope that one day they will materialise into some value for us. For startup companies, options are a vital currency. Initially cash is tight and using options is a means to attract the right people to help launch the company or take it to the next stage in it's evolution.  In recent weeks, I hav...
Read more

Hire for Engineers not for Frameworks

I have been faced with hiring great engineering teams on a number of occasions, I am constantly amazed at home many hiring managers and recruiters seem to focus on particular technologies and experience in those technologies. My experience has taught me to hire engineers and I have always viewed the technology as a secondary consideration. I always focuses on a grasp of engineering fundamentals and not on information about some current or past technology. In our current world these technologies are out of date by the time the ink on the contract is dry. Recently, I was approached by a leading company for a very senior role. The in-house recruiter laid on his wonderful resume with world leading software companies before affording me the chance to explain my career-to-date. He then proceeded to ask me a number of questions on specific Java libraries and how they were used. This is all information that is readily available on reference sites and in API documentation and does not ...
Read more

Insights & Suggestions For Effective Software development

I decided to note a few observations on software development based on my experiences with a number of clients over a long career, this is work in progress and would appreciate any further input or comments. Topics Data science needs systematic approach Without Specification you are in trouble Interview for excellence Agile does not mean "do nothing" Devops first is not always productive Too many resources is as bad, or worse than too little Design before Develop, before Deploy 1. Data Science needs a `Systematic Approach` We live in a `Data Science` age, it's a buzz word. We have always had data science in some form or another, it's just that the availability, techniques, compute power and volume has exploded over the last few years. Principles are not new, they are standard engineering practises, however, in the new generation of `Data Science` these standard practises are often overlooked. Here are some general rules-of-thumb I have noted down : It makes no sense to...
Read more