If you are reading this, please get modern browser.
skip to main content | skip to main navigation | skip to secondary content

FOWA Expo random bits

~ 13th October 2007. · 13:56 CET · permanent link · printer friendly ~

Earlier this week, I already wrote about FOWA Expo, but here are more informal bits — moments and quotes written down, remembered or experienced.

Networking

Prior the conference every attendee was asked to sign-up to FOWA Crowdwine and choose her interests, so the organizers can help us meet more people. Those who did, received unique badges at reception with their tags, matches and opposites.

My tags were naturally: user experience, web standards, typography… and my matches were Robin Christoperson, Andrew Pendrick, Sarah Ward and George Zafirovski. I actually met George, who moved from Macedonia to London some 10 years ago, so we easily switched to Croatian (Macedonia and Croatia are both former Yugoslaw republics).

There was a couple of considerable job offers on the conference and if one was available, she could walk away with a brand new position.

Randoms bits

  • Erika Hall said Users don’t complain about wording as long as you don’t change colors. (Copy is Interface)
  • Matt Biddulph said Internet is small pieces loosely joined. (Coding on the Shoulders of Giants)
  • If you need reliable standalone “DOMContentLoaded” JavaScript function, take a look at the shortloaded by famous Stuart Langridge.
  • Identity Matcher, extracted from dopplr.com codebase, enables you to pull in social network information from sites such as GMail, Twitter, Flickr or Facebook.
  • This one’s my favorite; Daniel Burka said You simply have to say ‘No’ to more features. Look at the Firefox and Mozilla Suite. Firefox would never be so popular if they didn’t decide to keep it simple.

Introduce advanced options wisely

~ 10th October 2007. · 08:40 CET · permanent link · printer friendly ~

The default options are the ones, that the majority of users understand well. With defaults designed to facilitate the basic tasks, all users will be able to start using web app right away.

Advanced features only make sense if they increase the accuracy and reduce time spent on a task. Advanced options made up-front, without real demand from the user-base are often only something glossy and shiny. Inviting users to learn a feature which main purpose is to be a cool widget that differentiate the application from the others — will fail for one very simple reason.

The kind of users who would appreciate such a feature are often anxiously seeking for the next gadget once the master the current one. In most cases, those visitors are not here for the content, but for the context, most notably the coolness factor. Unless the coolness itself is your product, you are probably not targeting those users.

Add advanced feature when you are absolutely sure you need it and after you have real user’s feedback.

Advanced feature should be gently introduced once the user is familiar with the basic functionality. In desktop applications such advanced options are often hidden in the ‘settings’ or ‘preferences’ panel. In web application those could be placed somewhere in ‘my profile’ area. However you decide to do it technically, don’t create the interface noise by polluting the content.

With well known web services, like Amazon, the extensive loyal user base is a good excuse to place an advanced feature right up-front. With a new project which need yet to prove its’ credibility, one has to be careful not to reject valuable first comers by unnecessary complicated interface.

Related reading

FOWA Expo 07 report

~ 8th October 2007. · 22:16 CET · permanent link · printer friendly ~

The FOWA Expo was more business oriented then the previous one (Expo extension is for sponsor’s stands on the entrance to the hall, where some interesting product/service demos were held). A vast majority of talks were about lessons learned and dos and don’ts when it comes to startups.

On to presentations… or better yet, speakers

Super-optimistic Chief Performance Yahoo! Steve Sounders, the author of YSlow for Firebug, confirmed what Nate Koechley first introduced at @media this Spring about speeding-up web pages.

You can’t fight the numbers and High Performance Web Sites surely whipped some shocking ones out. I already saw some of the graphs at YUI Blog earlier, but many attendees were left surprised.

Following the High Performance directions, any site can be 50% leaner within a few hours. Given the fact that the companies/organizations invest considerable amounts of money into hardware infrastructure and/or back-end development (for instance, a development of an advanced caching system), it is just silly to skip this first and the easiest step in optimizing site’s performance.

If you’re ready to start making faster web pages, but don’t know where to start, I encourage you to buy a book.

Robin Christopherson, a Web Consultant at AbilityNet, held pretty impressive demonstration about how visually challenged people use the internet. Listening to screen reader playing the endless strings of meaningful text was scary, but at the same time enlightening experience.

The curiosity of the session was — it takes approx. 20 minutes for screen reader to start reading the main content on Amazon.co.uk, because they simply didn’t provide skip to main content link.

Daniel Burka, a lead creative behind Digg and Pownce was a true refreshment. His presentation about community feedback was honest and authentic. He was surprisingly patient to rivers of attendees, without a blink of celebrity pretending. Thanks to his feet standing firmly on the ground, we’ve collected some pretty valuable tips & tricks during the informal discussions afterwards.

Erika Hall from Mule Design in her Copy is Interface gave a bunch of great examples of how careless choice of copy used on the site’s interface can make a site either miss-interpreted or completely blunt. She also pointed out that without knowing your users/audience, it’s difficult to come with the right choice.

The sweet desert of the second day was a survival/essential startup session by Feedburner co-founder Dick Costolo. He extended the presentation well over his minutes, but with a good reason and greatly approved by the crowd.

Launch Late to Iterate Often provided a great insight in common pitfalls in the first year or so of a projects life-span. Pointers like Ask for money when you have it, There’s no such thing as a Standard Deal and Flat Organization are just a few of 14 selected bullets I wrote down; and there was even more… What’s more important — he covered every thesis with a valid example.

All in all, many bits collected and a few randoms I will hopefully post in the next couple of days. In a mean-time, check out the available presentations at SlideShare.

* Please keep in mind that this is a personal web site and it does not reflect the position or opinion of my respective employers, organizations or partners.

Typetester – compare screen type Supported by Veer.

What is this?

A web log of Marko Dugonjić, web professional from Croatia. Topics covered:

Translate this site

German, Spanish, Italian, French or Japanese (via).

See you there!

Feel like buying a book?

Try with maratz.com aStore

Worth visiting

top of the page | skip to main content | skip to main navigation | skip to secondary content