Highlights of Week 32/2010
- Real Time Web Analytics Services – Best of (by hongkiat) - which web analytics service do you use?
- Guidelines for URI Design (by Jacob Gillespie) - URI structure is primarily important for user recognition and easy of use, search engine optimization is nice too.
- 8 Ways to Make Your Website Mobile Friendly (by Joel Reyes) - isn't it sweet that our mobiles will drive us towards better web development also? Something we should have been doing for a long time already?
- The ADA and the Web: Concerns and Misconceptions (by Jared Smith) - Is an accessibility law for e-commerce coming? Will this take the look of the web back to 1990? Jared has some nice Q&A there...
- Stop Designing Aesthetics, Start Designing Emotions (by John O’Nolan) - Design for emotions, definitely not a new concept but usually poorly covered. John takes a good stab on it.
- 5 Small Biz Web Design Trends to Watch (by Grace Smith) - Minimalism, Unique Photography, Bold Typography, Clear Calls to Action, A/B Testing - what more to say?
- iPad User Experience Guidelines (by UX Magazine) - with the source doc at Apple's Human Interface Guidelines for the iPad
Designing a Stop Sign [Video]
aka 'Welcome to my life'
Disclaimer: Any similarity to projects and designs living or dead is purely coincidental.
PS.: My absolute favorite is the dude swallowing his snack "...and a web address, in case people want more info".
Highlights of Week 27/2010
- Debunking the Myths of Remote Usability Studies (by Corrie Kwan, Jin Li, and May Wong) - some myths might seem obvious, but others - drawn from first-hand experience - are not. Anyway, lot's of good advise to be considered.
- How to Communicate With Your Clients (by Joel Reyes) - In short: Listen, Ask, Consult, Respect, Reason
- Beginner’s Guide to SEO: Best Practices – Part 3/3, Part 2/3, Part 1/3 (by hongkiat) - Search Engine Optimization is a must in all our toolboxes. Excellent three-part tutorial, thx!
- 250 Quick Web Design Tips (Part 2) (Part 1) (by Alexander Dawson) - about Browsers, Styles, Techniques, Marketing and all other good stuff.
- Agile UX and The One Change That Changes Everything (by Anders Ramsay) - Start Building Earlier through Rapid and Rich Communication and Just-in-Time Detail.
As always, send me your link or mention it in the comments. Anything related to this blog is much appreciated by all of us. Thanks!
Web Design: Sexy versus Conservative

In this post I try to keep true to my promise to add some spice to the world of web design and usability: I will try to investigate the cons of designing "sexy" versus "conservative".
So far clients still owe me a consistent definition of what they mean by asking for a "sexy" or "conservative" user interface. I guess I have a hunch and we all probably feel the difference but eventually it boils down to subjective interpretations.
Photo credits: AlphaX/X17, Adrian Varnedoe, A. Than/Pacific Coast News
Motivation
Just for a moment think of who you would rather want to have a long-lasting relationship with? The Paris Hilton on the left of the photo (sexy) or the Paris Hilton to the right (conservative)? Ok, probably neither, but for the sake of the argument?
In the words of one of our consultants: make the design 'sexy' for our marketing department and 'conservative' for our users. What now? Really?
Let's try to look at the cons of either side in an unbiased way by using a funny dating analogy:
The Bad of too Sexy
Designing too sexy gives everything away for free and leaves you with nothing to hold in reserve
Users know within seconds whether a site is right for them or not, they smell the scent of usefulness and determine that what is offered is worth further time investment. One might call initial attraction a success but it is human nature to want something more if we cannot have it.
So keep certain things a mystery. Don't give everything away upfront or for free. It's OK to tease though.
A 'slutty' design may lower your general value
Your users may feel that they have a higher intrinsic value than you do. Therefore you are not really worth further attention or a long-term relationship.
Design for emotions but keep in mind that trust is only built when your users can take you serious.
Sexy design may show your less than desirable aspects
Surely skillful designers know that it is important to emphasize the attractive aspects of your business and hide the less attractive characteristics. But, trying to pretend being somebody or something that you are not will come across as fake and unreal.
Stay true to your values and represent who you are. Don't pretend to be young or sexy if you aren't.
The Bad of too Conservative
Designing conservatively may indicate a low self-esteem
'Playing it safe' can be caused by many things: traditions, missing innovation, dusty policies, organizational structures, stubborn managers. Whatever it is, it will be felt by the users and could be interpreted as old-fashioned, slow (to deliver), outdated or simply lame.
Being bold is important (having a skilled designer helps too). Engage modern technology and trends like the social web.
Designing conservatively may indicate discomfort with your own business
You might have a hard time defining your business or telling an attractive story of who you are or what you do. This means you are not wholly comfortable or happy with what you represent and therefore choose to show as little of yourself as possible. Holding back is very risky because users (clients) might not understand who you are and don't know why they should get engaged or continue spending their time on your site.
Work hard to make your content/service attractive rather than the appearance. Don't hold back with something that helps engaging users.
Designing conservatively may not catch your users
Design must stand out because it will make YOU stand out. In times where everybody and everything is available on the web it's more important than ever to be unique in your offering, precise in how your business is different (or better) to others and clear in your message. Your front-end should clearly communicate all that! Designing too conservative may ultimately result in fewer visits and engagements.
Be unique and clear about your offerings and communicate it through your user interface.
Conclusion
The purpose of (most) web designs is to engage people and build relationships. That's why appearance is so important and that's why you should not design in stereotypes (aka 'sexy' or 'conservative').
Try to be clear about what you offer and honest in how you present it.
Like with anything in life, make sure to do your homework, learn about your target audience (think google). This will tell you how to dress appropriately and make the date between you and your users a pleasurable experience and hopefully a long-lasting one as well.
What's your opinion? How do you design? Why?
Website Analytics I: Browser Support
Which browser platform should we design for? To most web developers this question is a nightmare and dilemma at the same time, but yet again we face it almost on a daily basis. Just to show you how difficult an answer might be is the disparity between two projects I'm involved in, one for a federal government body that by definition only supports IE6 and another that is expected to be finished in 6 months and therefore was hoping to target IE8. Are these expectations realistic?
Analytics
Let's have a look at some website analytics that were collected over the past year (July 2008 - July 2009), taken from Fanposter.org, a social media website with over 5000 registered users from almost 100 countries and collected through Google Analytics.
Note: While I'm aware that the audience of this website might not be representative for all age groups or countries/regions, it still provides valuable hints about browser usage and trends.
Lesson 1: Internet Explorer on the fall
Internet Explorer is historically bundled with Microsoft Windows Operating Systems. IE6 was released August 27, 2001 just months before WinXP; IE7 was released October 18, 2006 and included with Windows Vista and Win Server 2008; IE8 final was released March 19, 2009 and will be included with Windows 7.
The combined total market share for Internet Explorer over the past year was 76.5% but the trend shows a clear decline over the past months from 74.0% in May to 68.8% in June and 53.9% in July.
Will this trend continue to hold true?
A lot will depend on the upcoming release of Windows 7 in October 2009 with Microsoft's power in reaching the people to upgrade their browsers. But almost certainly Microsoft will loose its dominant position of 95% in 2002 and 2003 (IE5 & IE6) or over 75% in the past year to its numerous very capable competitors.
Lesson 2: IE8 on the rise
When comparing the 3 current versions of Internet Explorer out there (IE6, IE7 and IE8 with IE5 and lesser not appearing in the analytics anymore and therefore being disregarded) it seems to be evident that IE8 is on the rise. Though the really surprising observation is that this increase cannot be accounted to users abandoning IE6 but rather to users upgrading their version of IE7. How come? The answer seems to lie in fact that many companies and their IT departments as well as governmental bodies still continue to hold on to and enforce the use of IE6. Can Microsoft overcome these - mostly security-related - concerns through IE8?
Lesson 3: IE6 might not die as soon as we all may wish

Figure 3: Google Trends; The spikes D, E & F indicate the introductions of Beta 1 (March 5, 2008), Beta 2 (August 27, 2008) and Final respectively.
As discussed above IE6 is still a requirement for many users. A quick look at Google Trends reveals that searches for IE6 (Figure 3: blue line) have been pretty stable over the past 4-5 years while searches for IE7 (Figure 3: red line) are declining and searches for IE8 (Figure 3: yellow line) are in the lead. This goes hand in hand with the observations in Lesson 2 above.
In the meantime let's join the numerous battles to kill IE6 like Norwegian Websites Declare War on IE 6 and IE Death March or more seriously at Bring down IE6. Joke or not, IE6 will be around for some more time and therefore needs to be considered if we want it or not.
It won't even help that Digg is discussing to drop support for IE6 or YouTube Will Be Next To Kiss IE6 Support Goodbye. Both sites don't need users that cannot upgrade IE6 e.g. due to limitations at work because exactly these users have limited access restricted by their companies anyway.
Lesson 4: Firefox stays on top
A very interesting observation is the fact that Firefox does a really great job in staying on top of things and keeping their user base up to date. In the last month of the observation period less than 5% of all Firefox users had a version lesser than 3, or in other words, the great majority of Firefox users was using version 3 and higher. And with versions 3.7 and Firefox 4 in the making, a huge base of motivated developers and fascinating plug-ins the future looks bright. Firefox's marketshare seems to climb steadily also, as of July 2009 it showed 32.1% (20.5% average over the past year) with the majority Windows versions and only 0.6% on Mac and 0.2% on Linux. Obviously we all love the high commitment to standards compliancy that makes developing web apps a blast, right?
Lesson 5: Chrome & Safari
Google Chrome was released December 11, 2008 and first received as Google's never-ending battle against Microsoft (see graphic by Federico Fieni) but more likely just another smart move to keep users on the web - the faster, the better - or like Ben Parr explains "Revenue = Amount of Time on the Web".
As far as marketshare is concerned, Chrome rose to 2.3% in July according to my analytics. This is still fairly small but not to be underestimated. In terms of testing Google's developer page for Chrome suggests that "if you’ve tested your website with Safari 3.1 then your site should already work well on Google Chrome". But what about Safari?
Safari accounts for 1.3% in the yearly average (with 1.2% on Mac and the rest on Windows). Should we test Safari with a marginal share like this? It really depends on your budget and company structure which might require unjustified additional resources for your QA team. Do the math for yourself: 1% of 10k visitors are 100 potential customers - is it worth the effort?
Lesson 6: Opera is the misunderstood genius
Opera shows an average of 1.1% with an unexpected peak in July 2009 - I need to continue observing where and why that came from. Needless to say, Opera is strong in European countries like Russia and on mobile devices such as mobile phones, smartphones and PDA's (personal digital assistants). It's a shame that Opera is not further ahead, it has been and still is innovator and spearhead in terms of new useful features as well as standards compliancy and implementation.
What are your experiences?
Without giving any decisive conclusions I'd like to hear your experiences or analytics to this subject. For which browser platform do you design for? What do you tell your clients when they ask you this question?









