This is a Chrome extension that will resize your browser window to the break points in the code of the current site you are viewing. Those sites without breakpoints show a blank window in the extension.
Responsive Inspector is helpful to see all of the breakpoints a particular site uses. Some have several breakpoints, other sites have just a few. It's a good learning tool.
It's a wee bit buggy sometimes, but it's being updated regularly.
If this link does not work, just search for "Responsive Inspector" in the Chrome browser Extensions.
A Beautiful Boilerplate for Responsive, Mobile-Friendly Development
There are other tools like this. We may be interested in learning more about them when the time comes.
Some interesting tips such as:
1) start design with mobile and expand out for larger screens
2) even numbers of columns provide easier wrapping options than odd numbers
Zurb story here: http://zurb.com/responsive/reading
Kia's site is: http://www.kia.com
Number 6 is Kia's new RWD. I went to the kia.com site and the RWD was pretty awful.
* MIN WIDTH:
-- images and text are blurry.
-- horizontal nav completly disappears.
-- the 3 stacked horizontal bars that should pull up a menu.....don't. They drop the main page and you're stuck facing a carousel and some monumental horizontal and vertical scrolling to see only models of vehicles.
* MAX WIDTH:
-- they don't have a max width and try to stretch into infinity. Stretched across 2 or 3 of my displays and I have the full site.....blurry.
* MOBILE SITE:
-- it's a mini-version of the main desktop site.
-- this works well on the iPad in both vertical and horizontal orientation.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I've seen great RWD when the min- and max-width are defined and the three horizontal bars become what used to be the horizontal navigation.
But Kia's desktop RWD fall short in my opinion. If anyone ever reads this, I wonder what their impressions would be.
Wow, very interesting. The numbers tell the story of the browser use declining.
The great increase was social media; people still use the browser on a computer to access the social media site. They don't download a Facebook application to install on their computer-they use the browser.
But mobile-wise, that's a different beast. I still think we should create a site that is accessible to mobile devices rather than create an app. I think in the coming years, though, iOS/Android developers will probably be job positions here at UT.
Great post, thanks for sharing.
I take issue with focusing on the amount of time spent in apps vs. mobile web. If you look at the breakdown, 68% of app time is on pure entertainment activities like gaming, social media and YouTube. Which makes total sense that people spend a disproportionate amount of time on those things.
Plus that guy looks really annoying!
RE: Mason-Good points, Señor Mason. But using inflammatory titles gets people reading.
My next post will be "LIBRARIES ARE DEAD-EVERYTHING IS ON GOOGLE, ANYWAY".