Mind-blowing User Interface

The future of online magazines is here...Check out Time magazine's new iPad App




And btw HTML 5 can do all this...(so says Steve!)

Sam Kurien

Wondering If Intuitive Designs should be the norm?

This post will start off with a posing question that is different from the title of the post- Should Intuitive Designs be built into systems or is the adaptability to such systems/interfaces already built into us?

I often wonder about the above question and  problems  like this do stay to bother. A architect/system designer/UI designer or a product designer always (well…not always) wrestle with these kinds of questions. On the left here is the pic of my daughter playing with my mac, when this was taken she was not even three, she is now four and knows how to use cell phones, and almost all the digital devices that her dad uses at home ranging from (ipods, iphones, wii, blu-ray player, hdtv’s etc.)….sounds scary isn’t it but again I begin to wonder if this is the world we live in now, as a parent I am confused whether to be proud of it or not? However these question still loom up in the air…

As I dissect these ponderings let me come at it from the angle of first answering the title to this post: I think as systems are designed and inventions (hardware) or software’s come to life a certain amount of intuitive behavior is always built into them no matter what and they either result into friendly or not so friendly systems. From the pictures above some of the mac fans may argue it is the ease of the system that allows this four year old to watch YouTube videos on my laptop but hold that thought that’s why I merged the two images into one, the laptops on one half is a PC laptop and on the other half is the mac and the web page Hannah is watching is YouTube on both machines. She has somehow figured out watching me for a good amount of time how to click on the favorite links in Safari as well as Firefox. So the argument that the MAC interface is easier for the child or easier to use in Hannah’s case fails. Again this may not  be a very good example but there is this truth that in the systems or interfaces designed some are easier to use and some are harder or just plainly inconvenient.

The second aspect again…”I wonder” and question is if the cognitive adaptability of the mind is strong in some (and not so strong in others) that enables the end user to just figure out the system and make use of it to satisfy a given need. In Hannah’s case her need to watch cartoons made her aware of the system (ot the tool to be used), she adapted the system and the need was satisfied. Though she hasn’t figured out that the favorites “Tom & Jerry” is bookmarked on the sites whenever she pulls up that site, her adaptive mind doesn’t care whether it’s a PC or MAC, she doesn’t care if the interfaces are convenient or not but the need to watch those cartoons is satisfied by her congnitive adaptability of the system irrespective of the intuitive design. This is true in the case of systems like SAP, the manufacturing industry really needed software products that solved problems on supply chain, managing production cycles etc and SAP systems solved that very need but the user interfaces on those systems “sucked” (pardon my expression here) big time but that is the truth. The engineers solved the problem but the interfaces were clumsy to use and soon productivity over a period of time turned into time consuming nightmares with SAP specialists rising in the market (sorry SAP guys...you are special) . So the next question that arises would be ...should designers/architects of a system even bother what the end user thinks, if the need is there, the end user will adapt and learn. Unfortunately many systems both devices and softwares are designed by technical people who believe that they know best and the end users know less or for that matter the end users don't really know what they want. The evolution of systems and the design process has come a long way and the truth of the age is far from it, we live in a age where interface designing has matured not only in the everyday machines we use but in software interfaces we design. The very competitiveness of firms to survive depends on it. An interesting point to note here would be to ask what then is the balanced approach to known as to how much intuitiveness needs to be built in so that it is easy to use, learning cycles are cut short, and finally it is easy to adapt.

Another interesting question that I will pose here is how do we measure those balances while designing such systems? We know maturity models optimize processes, procedures and product development but adaptability will be a hard one to measure as humans are capable of adapting at different levels of cognition, but at the end of the day I will settle for a system that has high form factor, high functionality and high adaptability in every area of design engineering. A design approach like the one graphically represented here from Anothony Robinson's six stage UI design work flow makes perfect sense to me if the approach is user centric, iterative. This approach though may have longer gestation periods and may be expensive in the beginning the plus's are the longer life cycle of the product and a support engineer's boon  - less maintenance and bug fixes. Now this may vary from industry to industry but this is a good start.

So in short...systems should have built in them the ease of use graphical or logical intuitiveness. System designers and Product designers should start by defining usability and utility (mind you they are different) from a the perspective of the all types of users in the mass, know the limitations that you cannot please everybody (a certain level of adaptability will be assumed from certain segments) and the result is we have a process defined for intuitive design to be the norm.

Sorry this post must have posed more questions than having answered them but these spaces are placeholders for my thoughts and I am sure I will revisit it soon.

Sam Kurien

Introducing the Blend Art-board

The one thing I like about the Blend is the idea of moving towards a system where the designer, architect and programmer can visualize and talk to each other with ease. Not only intuitive user interfaces is the order of the day but building them fast and with ease is also on the high priority with software manufacturers. This post is to introduce you to the different parts of the Blend Software's UI.

The work surface is referred to as the artborad where you will design your Silverlight or WPF applications. 

The artboard is your work surface, where you can visually design a document in your application by drawing objects and modifying them.

1. The artboard background color can be changed to suit anything you want, it is like the canvas where the majority of your work will be done.  To change the color you can use the Tools >> Options menu to do so. 

2. XAML Editor : The code that is generated is called XAML and can be edited in this window. If you look at indicator 5 it will give you options to be in Split view which means (design+code), XAML View which means you can directly edit the code. 

3. The Artboard controls have five key controls which are snapping on and off the gridlines, snaplines, showing annotations and turning on and off rendering effects. This area also shows the zoom percentages that can be controlled by clicking on the list down. 

4. This is the area where the filenames of your project appear. 

5. See point number 2. 

When you are working on a project you will also see certain tabs on the left and the right which can be turned on and off based upon the objects and actions you are performing on them. I have included these screen shots for your reference, in case you are following for the first time after you have installed Expression Blend. 

Enjoy..Next Time we will go ahead and create a roll over application.

HTML 5 Sketchpad

HTML5 being touted as the wave of the future in markup languages. Just do a google search if you’re curious about html5 and you’ll find a ton of info on what it is. HTML5 is being developed as the next major revision of HTML (Hypertext Markup Language), the core markup language of the World Wide Web. The Web Hypertext Application Technology Working Group (WHATWG) started work on the specification around June 2004 under the name Web Applications 1.0.[1] As of February 2010, the specification is in the "Last Call" state at the WHATWG - which as mentioned earlier stands for WEB HYPERTEXT APPLICATION TECHNOLOGY WORKING GROUP. The main purpose of HTML 5.0 is to reduce the need of plug ins for RIA applications like Adobe Flash, Silverligh, Apache Pivot, JavaFX etc.

I won’t bore you with all the details about coding, but I found this cool online sketchbook while browsing completely flash free sketching application. It will be interesting to see if this will be cross system embeddable (Is that even a word? Good thing about the English language is use it and popularize it and somebody will add it in the dictionary) and portable with blogs/social networking sites.