As a front end developer who has been using CSS3 and web-kit wherever I can, I have been very intrigued with the activity here the last couple of days.
I just want to make a few points; I want to design my sites with CSS3 – it’s quicker, it feels like the right thing to do. I believe in progressive enhancement and I build my wireframes in CSS from the get-go.
However I can’t brush over the fundamental problem we face as practitioners today which prevent me in working exactly the way I wish to – IE has ~70% of the market.
Until the tipping point is reached when IE6 is < ~5% and IE7 is < ~20%, only then we can look at focusing on the CSS3 animations etc that so few people can enjoy. I don’t believe in designing for the lowest common denominator but I believe less in designing poorer interfaces for users with IE6 and IE7 when in 2010 that is generally 70% of my audience.
The truth is, (and what I believe to be the best approach at the moment) is to build with the future in mind, but take the time to build beautiful IE6 and IE7 only stylesheets to optimise their experience and give them the best – there is no reason why they cant enjoy rounded corners, it just takes longer to implement.
For all the fuss RGBa and rounded corners is generating in the community, the truth is clients do not care. – And why should they? After all, designers were producing these designs over ten years ago. Clients are not wowed by opacity, its nothing new. It may be new how we implement it, but to the end user, they’ve seen it all before.
I also don’t find this antagonistic evil-IE6 rhetoric helpful in the slightest. Many users are unable to change their browser and they shouldn’t be made to feel guilty about it. We should cater for these people and give them a rewarding experience.
Marvin
As a front end developer who has been using CSS3 and web-kit wherever I can, I have been very intrigued with the activity here the last couple of days.
I just want to make a few points; I want to design my sites with CSS3 – it’s quicker, it feels like the right thing to do. I believe in progressive enhancement and I build my wireframes in CSS from the get-go.
However I can’t brush over the fundamental problem we face as practitioners today which prevent me in working exactly the way I wish to – IE has ~70% of the market.
Until the tipping point is reached when IE6 is < ~5% and IE7 is < ~20%, only then we can look at focusing on the CSS3 animations etc that so few people can enjoy. I don’t believe in designing for the lowest common denominator but I believe less in designing poorer interfaces for users with IE6 and IE7 when in 2010 that is generally 70% of my audience.
The truth is, (and what I believe to be the best approach at the moment) is to build with the future in mind, but take the time to build beautiful IE6 and IE7 only stylesheets to optimise their experience and give them the best – there is no reason why they cant enjoy rounded corners, it just takes longer to implement.
For all the fuss RGBa and rounded corners is generating in the community, the truth is clients do not care. – And why should they? After all, designers were producing these designs over ten years ago. Clients are not wowed by opacity, its nothing new. It may be new how we implement it, but to the end user, they’ve seen it all before.
I also don’t find this antagonistic evil-IE6 rhetoric helpful in the slightest. Many users are unable to change their browser and they shouldn’t be made to feel guilty about it. We should cater for these people and give them a rewarding experience.