Comments on: UIEtips: Where Are Mobile First Responsive Web Designs? http://www.uie.com/brainsparks/2012/09/11/uietips-mobile_first_rwd/ UIE\'s latest insights on the world of design Sat, 25 May 2013 00:51:34 +0000 hourly 1 http://wordpress.org/?v=3.4.1 By: Brad Greenwald http://www.uie.com/brainsparks/2012/09/11/uietips-mobile_first_rwd/comment-page-1/#comment-240687 Brad Greenwald Mon, 26 Nov 2012 21:51:15 +0000 http://www.uie.com/brainsparks/?p=8083#comment-240687 I currently work at space150 where we built http://www.buffalowildwings.com as a mobile first experience. We used techniques such as CSS inline SVG, server-side detection for mobile assets, and Javascript which builds & destroys various interactive page features. We built the mobile experience at 768 pixels and lower to accommodate a wide range of Android devices. The average page size is around 1mb, while a couple pages are 2mb or greater. We have content entered through a CMS, it's not easy to get optimized images uploaded through the CMS after the content entry process leaves are hands. In areas such as slideshows, the time investment to create mobile-first versions of images become too taxing on the project, resulting in an under-utilization of our server-side mobile detection program. Building sites in this fashion has resulted in the creation of scripts which our developers are occasionally making public on github. I do agree mobile-first frameworks seem to be in their infancy at this time. Thought I'd share, Cheers, Brad Greenwald I currently work at space150 where we built http://www.buffalowildwings.com as a mobile first experience.

We used techniques such as CSS inline SVG, server-side detection for mobile assets, and Javascript which builds & destroys various interactive page features. We built the mobile experience at 768 pixels and lower to accommodate a wide range of Android devices. The average page size is around 1mb, while a couple pages are 2mb or greater. We have content entered through a CMS, it’s not easy to get optimized images uploaded through the CMS after the content entry process leaves are hands.

In areas such as slideshows, the time investment to create mobile-first versions of images become too taxing on the project, resulting in an under-utilization of our server-side mobile detection program.

Building sites in this fashion has resulted in the creation of scripts which our developers are occasionally making public on github. I do agree mobile-first frameworks seem to be in their infancy at this time.

Thought I’d share,
Cheers,
Brad Greenwald

]]> By: Bark Golgafrincham http://www.uie.com/brainsparks/2012/09/11/uietips-mobile_first_rwd/comment-page-1/#comment-235068 Bark Golgafrincham Thu, 04 Oct 2012 19:40:28 +0000 http://www.uie.com/brainsparks/?p=8083#comment-235068 People continue to misunderstand RWD as it relates to web applications as opposed to brochure and newspaper sites. RWD is not just about content sizing -- RWD is going to be about abstraction, code management, and using the right methodologies. See here for more -- http://wp.me/p2brND-8C People continue to misunderstand RWD as it relates to web applications as opposed to brochure and newspaper sites. RWD is not just about content sizing — RWD is going to be about abstraction, code management, and using the right methodologies.

See here for more —
http://wp.me/p2brND-8C

]]>