This website must look exactly the same in every browser The short answer.

The Longer Answer

The idea of making websites look exactly the same goes back to the Netscape vs Internet Explorer days of old. Today, the web is a vast landscape of devices, browsers, and usage types. I think that its safe to declare designing a website to look exactly the same on an iPhone as on IE6 is foolish. Not only does the iPhone posses a far superior rendering engine (WebKit) but it’s screen is much smaller, and has an entirely different interaction modality (touch) than a dinosaur windows XP machine running Internet Explorer 6. That is why we declare 2010 the end of the design once, deploy exactly the same, everywhere mantra. It’s time to design websites that are flexible, and adapt the the device viewing them. Take our site for instance, which has a iPhone and Android friendly mobile version that slims down the content, and uses interaction helpers devoted to touch users. The iPad version is a work in progress, mainly because we’re waiting on iPad 2.

Internet Explorer 6 – (Finally) Nearing Extinction

Yes, this 10 year old browser is still being talked about, even after Microsoft sent flowers to a public funeral. I think moving forward into 2011 we can finally call it dead. The graph below shows that IE6 for the US market has declined below 5% in the past year. At Circle Tree, we have not supported IE6 by default in our proposals since 2009. Please note – We still do market research for our clients to determine the percentage of their market share that is still using IE6, and if we find it is a sizeable market, then we will recommend IE6 compatibility in our proposal.

This is not an excuse not to do your research – an ounce of prevention is worth a pound of cure. This is especially in the design phase when making decisions such as alpha transparent PNGs. While there are IE6 specific hacks that use proprietary filters to render transparency, it slows down load times and blocks the browser while rendering. Our site is a perfect example, we didn’t think about IE6 from the start. As a result, we were free to layer multiple transparent PNGs to create depth and give the site fluidity.

Closing thoughts

Moving forward into 2011, feel free to design a site based on multiple looks, one for mobile, one for desktop, and even one for the iPad. Also, consider offering IE6 compatability as a value added service to your clients, as opposed to a default when creating a design. This way the client knows what to expect in terms of site performance in IE6. It also frees you from designing inside the burdensome box which is IE6 land. No more will you worry about box model hacks, z-index bugs or transparency support. It’s quite a relief, I suggest you try it, too.

This website must look exactly the same in every browser The short answer.

The Longer Answer

The idea of making websites look exactly the same goes back to the Netscape vs Internet Explorer days of old. Today, the web is a vast landscape of devices, browsers, and usage types. I think that its safe to declare designing a website to look exactly the same on an iPhone as on IE6 is foolish. Not only does the iPhone posses a far superior rendering engine (WebKit) but it’s screen is much smaller, and has an entirely different interaction modality (touch) than a dinosaur windows XP machine running Internet Explorer 6. That is why we declare 2010 the end of the design once, deploy exactly the same, everywhere mantra. It’s time to design websites that are flexible, and adapt the the device viewing them. Take our site for instance, which has a iPhone and Android friendly mobile version that slims down the content, and uses interaction helpers devoted to touch users. The iPad version is a work in progress, mainly because we’re waiting on iPad 2.

Internet Explorer 6 – (Finally) Nearing Extinction

Yes, this 10 year old browser is still being talked about, even after Microsoft sent flowers to a public funeral. I think moving forward into 2011 we can finally call it dead. The graph below shows that IE6 for the US market has declined below 5% in the past year. At Circle Tree, we have not supported IE6 by default in our proposals since 2009. Please note – We still do market research for our clients to determine the percentage of their market share that is still using IE6, and if we find it is a sizeable market, then we will recommend IE6 compatibility in our proposal.

This is not an excuse not to do your research – an ounce of prevention is worth a pound of cure. This is especially in the design phase when making decisions such as alpha transparent PNGs. While there are IE6 specific hacks that use proprietary filters to render transparency, it slows down load times and blocks the browser while rendering. Our site is a perfect example, we didn’t think about IE6 from the start. As a result, we were free to layer multiple transparent PNGs to create depth and give the site fluidity.

Closing thoughts

Moving forward into 2011, feel free to design a site based on multiple looks, one for mobile, one for desktop, and even one for the iPad. Also, consider offering IE6 compatability as a value added service to your clients, as opposed to a default when creating a design. This way the client knows what to expect in terms of site performance in IE6. It also frees you from designing inside the burdensome box which is IE6 land. No more will you worry about box model hacks, z-index bugs or transparency support. It’s quite a relief, I suggest you try it, too.

The new year has passed, and as the sounds of fireworks fade and the cacophony clears, I thought it was time to look back at some of things that need to die from 2010. This is a retrospective to our Web Design trends for 2011 article.

This website must look exactly the same in every browser The short answer.

The Longer Answer

The idea of making websites look exactly the same goes back to the Netscape vs Internet Explorer days of old. Today, the web is a vast landscape of devices, browsers, and usage types. I think that its safe to declare designing a website to look exactly the same on an iPhone as on IE6 is foolish. Not only does the iPhone posses a far superior rendering engine (WebKit) but it’s screen is much smaller, and has an entirely different interaction modality (touch) than a dinosaur windows XP machine running Internet Explorer 6. That is why we declare 2010 the end of the design once, deploy exactly the same, everywhere mantra. It’s time to design websites that are flexible, and adapt the the device viewing them. Take our site for instance, which has a iPhone and Android friendly mobile version that slims down the content, and uses interaction helpers devoted to touch users. The iPad version is a work in progress, mainly because we’re waiting on iPad 2.

Internet Explorer 6 – (Finally) Nearing Extinction

Yes, this 10 year old browser is still being talked about, even after Microsoft sent flowers to a public funeral. I think moving forward into 2011 we can finally call it dead. The graph below shows that IE6 for the US market has declined below 5% in the past year. At Circle Tree, we have not supported IE6 by default in our proposals since 2009. Please note – We still do market research for our clients to determine the percentage of their market share that is still using IE6, and if we find it is a sizeable market, then we will recommend IE6 compatibility in our proposal.

This is not an excuse not to do your research – an ounce of prevention is worth a pound of cure. This is especially in the design phase when making decisions such as alpha transparent PNGs. While there are IE6 specific hacks that use proprietary filters to render transparency, it slows down load times and blocks the browser while rendering. Our site is a perfect example, we didn’t think about IE6 from the start. As a result, we were free to layer multiple transparent PNGs to create depth and give the site fluidity.

Closing thoughts

Moving forward into 2011, feel free to design a site based on multiple looks, one for mobile, one for desktop, and even one for the iPad. Also, consider offering IE6 compatability as a value added service to your clients, as opposed to a default when creating a design. This way the client knows what to expect in terms of site performance in IE6. It also frees you from designing inside the burdensome box which is IE6 land. No more will you worry about box model hacks, z-index bugs or transparency support. It’s quite a relief, I suggest you try it, too.

This website must look exactly the same in every browser The short answer.

The Longer Answer

The idea of making websites look exactly the same goes back to the Netscape vs Internet Explorer days of old. Today, the web is a vast landscape of devices, browsers, and usage types. I think that its safe to declare designing a website to look exactly the same on an iPhone as on IE6 is foolish. Not only does the iPhone posses a far superior rendering engine (WebKit) but it’s screen is much smaller, and has an entirely different interaction modality (touch) than a dinosaur windows XP machine running Internet Explorer 6. That is why we declare 2010 the end of the design once, deploy exactly the same, everywhere mantra. It’s time to design websites that are flexible, and adapt the the device viewing them. Take our site for instance, which has a iPhone and Android friendly mobile version that slims down the content, and uses interaction helpers devoted to touch users. The iPad version is a work in progress, mainly because we’re waiting on iPad 2.

Internet Explorer 6 – (Finally) Nearing Extinction

Yes, this 10 year old browser is still being talked about, even after Microsoft sent flowers to a public funeral. I think moving forward into 2011 we can finally call it dead. The graph below shows that IE6 for the US market has declined below 5% in the past year. At Circle Tree, we have not supported IE6 by default in our proposals since 2009. Please note – We still do market research for our clients to determine the percentage of their market share that is still using IE6, and if we find it is a sizeable market, then we will recommend IE6 compatibility in our proposal.

This is not an excuse not to do your research – an ounce of prevention is worth a pound of cure. This is especially in the design phase when making decisions such as alpha transparent PNGs. While there are IE6 specific hacks that use proprietary filters to render transparency, it slows down load times and blocks the browser while rendering. Our site is a perfect example, we didn’t think about IE6 from the start. As a result, we were free to layer multiple transparent PNGs to create depth and give the site fluidity.

Closing thoughts

Moving forward into 2011, feel free to design a site based on multiple looks, one for mobile, one for desktop, and even one for the iPad. Also, consider offering IE6 compatability as a value added service to your clients, as opposed to a default when creating a design. This way the client knows what to expect in terms of site performance in IE6. It also frees you from designing inside the burdensome box which is IE6 land. No more will you worry about box model hacks, z-index bugs or transparency support. It’s quite a relief, I suggest you try it, too.

The new year has passed, and as the sounds of fireworks fade and the cacophony clears, I thought it was time to look back at some of things that need to die from 2010. This is a retrospective to our Web Design trends for 2011 article.

This website must look exactly the same in every browser The short answer.

The Longer Answer

The idea of making websites look exactly the same goes back to the Netscape vs Internet Explorer days of old. Today, the web is a vast landscape of devices, browsers, and usage types. I think that its safe to declare designing a website to look exactly the same on an iPhone as on IE6 is foolish. Not only does the iPhone posses a far superior rendering engine (WebKit) but it’s screen is much smaller, and has an entirely different interaction modality (touch) than a dinosaur windows XP machine running Internet Explorer 6. That is why we declare 2010 the end of the design once, deploy exactly the same, everywhere mantra. It’s time to design websites that are flexible, and adapt the the device viewing them. Take our site for instance, which has a iPhone and Android friendly mobile version that slims down the content, and uses interaction helpers devoted to touch users. The iPad version is a work in progress, mainly because we’re waiting on iPad 2.

Internet Explorer 6 – (Finally) Nearing Extinction

Yes, this 10 year old browser is still being talked about, even after Microsoft sent flowers to a public funeral. I think moving forward into 2011 we can finally call it dead. The graph below shows that IE6 for the US market has declined below 5% in the past year. At Circle Tree, we have not supported IE6 by default in our proposals since 2009. Please note – We still do market research for our clients to determine the percentage of their market share that is still using IE6, and if we find it is a sizeable market, then we will recommend IE6 compatibility in our proposal.

This is not an excuse not to do your research – an ounce of prevention is worth a pound of cure. This is especially in the design phase when making decisions such as alpha transparent PNGs. While there are IE6 specific hacks that use proprietary filters to render transparency, it slows down load times and blocks the browser while rendering. Our site is a perfect example, we didn’t think about IE6 from the start. As a result, we were free to layer multiple transparent PNGs to create depth and give the site fluidity.

Closing thoughts

Moving forward into 2011, feel free to design a site based on multiple looks, one for mobile, one for desktop, and even one for the iPad. Also, consider offering IE6 compatability as a value added service to your clients, as opposed to a default when creating a design. This way the client knows what to expect in terms of site performance in IE6. It also frees you from designing inside the burdensome box which is IE6 land. No more will you worry about box model hacks, z-index bugs or transparency support. It’s quite a relief, I suggest you try it, too.

This website must look exactly the same in every browser The short answer.

The Longer Answer

The idea of making websites look exactly the same goes back to the Netscape vs Internet Explorer days of old. Today, the web is a vast landscape of devices, browsers, and usage types. I think that its safe to declare designing a website to look exactly the same on an iPhone as on IE6 is foolish. Not only does the iPhone posses a far superior rendering engine (WebKit) but it’s screen is much smaller, and has an entirely different interaction modality (touch) than a dinosaur windows XP machine running Internet Explorer 6. That is why we declare 2010 the end of the design once, deploy exactly the same, everywhere mantra. It’s time to design websites that are flexible, and adapt the the device viewing them. Take our site for instance, which has a iPhone and Android friendly mobile version that slims down the content, and uses interaction helpers devoted to touch users. The iPad version is a work in progress, mainly because we’re waiting on iPad 2.

Internet Explorer 6 – (Finally) Nearing Extinction

Yes, this 10 year old browser is still being talked about, even after Microsoft sent flowers to a public funeral. I think moving forward into 2011 we can finally call it dead. The graph below shows that IE6 for the US market has declined below 5% in the past year. At Circle Tree, we have not supported IE6 by default in our proposals since 2009. Please note – We still do market research for our clients to determine the percentage of their market share that is still using IE6, and if we find it is a sizeable market, then we will recommend IE6 compatibility in our proposal.

This is not an excuse not to do your research – an ounce of prevention is worth a pound of cure. This is especially in the design phase when making decisions such as alpha transparent PNGs. While there are IE6 specific hacks that use proprietary filters to render transparency, it slows down load times and blocks the browser while rendering. Our site is a perfect example, we didn’t think about IE6 from the start. As a result, we were free to layer multiple transparent PNGs to create depth and give the site fluidity.

Closing thoughts

Moving forward into 2011, feel free to design a site based on multiple looks, one for mobile, one for desktop, and even one for the iPad. Also, consider offering IE6 compatability as a value added service to your clients, as opposed to a default when creating a design. This way the client knows what to expect in terms of site performance in IE6. It also frees you from designing inside the burdensome box which is IE6 land. No more will you worry about box model hacks, z-index bugs or transparency support. It’s quite a relief, I suggest you try it, too.