As a web developer there comes a time when you need to consign a browser to the dustbin of history, and remove it from your testing suite. It’s a decision I find difficult to make – I am a visual designer and hate the idea that a website I built might look less than perfect for anyone at all. But to offer our audience an experience that takes advantage of the best the web has to offer, it is necessary to weigh the needs of the many against the needs of the few. In this article I will look at some best practices for dropping support for a browser, and suggest a list of browsers that make the cut (and ones that don’t).
Over the years I have had the opportunity to collaborate with a number of print designers on website designs. The way these collaborations usually work is that the print designer will mock-up initial static layouts for the website, and it will fall to me to bring their mock-up to life in either Flash or HTML. These collaborative efforts can be very rewarding, but there are a few common “gotchas” that tend to catch print designers unawares when they first try their hand at designing for the web. Most of the problems stem from design challenges that are particular to the web, and wouldn’t typically be encountered by a print designer.
Now that Internet Explorer 7 has been released, I imagine many web designers will be running it as their default installation of IE, and using standalone versions to test sites in IE 6 or older. One longstanding drawback of these standalone versions is the inability to use the AlphaImageLoader filter, which enables the display of transparency in PNG images. Thankfully there is now a simple solution at hand.
In my experience, most web design clients don’t know much about design, and even less about the web. This isn’t a fault, and it doesn’t make them a bad client. It makes them a regular web user. But sometimes the knowledge gap between a designer and their client can lead to communication problems. I have found that with a little education my clients are better equipped to understand my decision making processes, and we are able to start talking to each other, rather than past each other.
If you didn’t blink, you may have noticed that for a few days recently Wikipedia’s entry for Web 2.0 included a subsection describing the visual elements of Web 2.0. Gradients, colorful icons, reflections, dropshadows, and large text all got a mention.
A few days later the “visual elements” addition had been removed after a vote by wikipedians. The objection, I suppose, is that no set of visual criteria can accurately define something as being characteristic of Web 2.0 – if Web 2.0 can be understood as an approach to generating and distributing content, then it needn’t be tied to a particular visual style.
Nevertheless, it’s true that many Web 2.0 sites do share a distinctive aesthetic. Wikipedia’s editors may not think it’s a worthy part of the Web 2.0 discussion, but I say bring it on! Let’s take a look at the some of the communication issues facing a Web 2.0 site, and see how the “Web 2.0 look” can help to solve them.
For a long time I was wary of designing email newsletters. I had read how difficult it was to construct an HTML newsletter that displayed as intended in all the popular email clients. I had heard about the horrors of creating layouts using tables. I had been warned about the perils of using CSS. But this year I have had several clients request that I design email newsletters for them, and had no choice but to school myself in the arcane art of HTML email design.
If you plan on designing a kick ass AJAX application then you better make sure you’ve got a kick ass load indicator. That way your visitors will know that stuff is happening while you weave your AJAX magic behind the scenes.
I’ve read a few articles recently where the author gives a run down of their top development or office productivity software – the “must have” tools that make you and your computer happy campers. Never one to miss a bandwagon, I’ve decided to create my own list of the web development and productivity tools that I use on a daily basis.
Swift is a new PC web browser based on Webkit, the open-source HTML rendering engine under the hood of Apple’s Safari browser. For web developers this opens up the possibility of testing websites in a decent approximation of Safari, without requiring a Mac on hand.
