Trent Walton has written (and designed) a great (and beautiful) article on dealing with content in responsive web designs that adapt to the width of visitors’ browsers. Content Choreography is a good discussion of content organization, changing designs too much between various widths, and the workflow needed when creating responsive web sites. Definitely a must read for any designer or developer.

http://mediaelementjs.com/

Great JavaScript script for HTML5 video and audio players with a Flash fallback. Includes plugins support and skins. Visitors get a good and consistent media experience regardless of what browser they’re using.

http://css-tricks.com/9778-screen-resolution-notequalto-browser-window/

Something I’ve been preaching for years, but just because your web analytics say everyone visiting your site has as screen resolution of 4,000 pixels by 4,000 pixels doesn’t actually mean their browser is that size. Screen resolution size is not the same as browser window size. Most users, including myself, surf the web with their browser window at only a fraction of their screen resolution.

This is a realization of the One Web (see 3.1 One Web) principle, whereby content should be accessible on a range of devices irrespective of differences in presentation capabilities and access mechanism. Web sites may paginate their content in various ways corresponding to differences in device characteristics; therefore the navigation structure of the site, and possibly its technical realization, may vary according to the device class that is being served. (See also [WebArch] Section 3.5.1).

A bookmark captured on one device should be usable on another, different type of device even if it does not yield exactly the same experience. If the page that was bookmarked is not appropriate for the device that is now using it, an alternative that is suitable should be provided.

Thematic consistency means no matter what device you’re using, the same content should pull up when you hit a URL.

Jason Grigsby of CloudFour has posted an interesting (as always) article on the latest trends in mobile first responsive web design and the numbers show the majority of responsive designs provide very little, if any, file size savings for their mobile versions.

http://elliotjaystocks.com/blog/css-transitions-media-queries/

Seen it happen accidentally since nearly the beginning of the responsive web design movement, but great writeup on how CSS3 transitions can add some fun to your responsive designs.

http://www.technologyreview.com/blog/mimssbits/26778/

A great article talking about the many advantages of the mobile web. A couple of great notes from the article. First, on the reach of the World Wide Web compared to the app stores:

One word: distribution. There are 2 billion web users versus 50 million iOS users.

And what’s in it for developers…

With web apps, developers could code once and be reasonably confident their app will work on any object — phone, tablet, laptop, etc. — with a standards-compliant browser. The implications for developer time and resources are profound.

http://blog.marketnet.com/index.php/2011/05/18/think-apps-are-all-that-matters-for-mobile-think-again/

Great stats on the mobile websites for Facebook and Twitter outpacing their respective mobile apps.

http://pinchzoom.com/posts/classes-of-mobile-web-apps

Great overview of the different options when creating mobile web apps from Brian Fling. Spans from iPhone only to universal apps.

http://designthencode.com/

I worked through the “from scratch” article and learned the basics of C and Cocoa programming and then immediately purchased the rest of Mike Rundle’s iPhone/iOS design & development resources.