Featured Posts

Notes from An Event Apart Boston 2012 I had a great time at An Event Apart Boston, 2012. Ill post some photos soon. The conference avoided deep dives into code in favor of showing WHY you would do reactive design. As Eric Meyer said "My...

Read more

Judging the CT Student Innovation Exposition (E-Commerce)... Want to know what the next 10 years will look like? Ask a high school student. Their creativity isnt limited by their knowledge of what we currently call technological limitations. They have a vision of...

Read more

The Value of Feeling Appreciated as an Employee in... Whether you’re a new employee or the vice president of the company, everyone wants to feel valued, even appreciated, in the workplace. Not only does it improve morale and make the workplace a more pleasant...

Read more

The difference between classic and motion tweens in... Here it is: If you're used to doing things "the cs3 way" then you can continue to do so with the classic tween tool. It works the same way as you remember, using key frames as normal, but you cannot...

Read more

PHP: If (equal to AND not equal) - eliminate form spam... Just learned a great function of PHP thats already made my forms a lot better. A while back I wrote an article about eliminating form spam without captchas by using css to hide a text input box for bots...

Read more

twitter

Breaking News

  •  

Examples of Responsive Design and a plea for Device Agnostic Design

Category : Art & Design, Cool Websites, CSS, Slick Code, Technology, What I Read

Below are a few of my favorite examples of Responsive Web Design, the practice of setting media types allowing the design to scale to adapt to whatever the size of the screen that the user is using.

http://robot-or-not.com/
http://bostonglobe.com/
http://clearairchallenge.com/
http://www.smashingmagazine.com/

Device Agnostic Design
An article from Smashing Magazine talks about Device Agnostic Design which is a great future proofing advancement from responsive design. Being device agnostic means that you use your content to set break points, not the device you want the content to display on. This is important because if we spend time developing content for specific devices we are creating the next developer nightmare. There is no way to predict the size or aspect ratio of screens in the future. What happens if you design your site to perfectly fit your favorite tablet only to discover that the next generation of that same device has a slightly different sized screen.

For now, it seems as though developers are at the mercy of hardware makers. All we can do is hope they create some sort of a standard, and quick. In the meanwhile, we’ll have to make design decisions based on the content we want to show. After all, content is King.

Post a comment