The proliferation of mobile devices has made it necessary to rethink your web experiences. The mobile phone and tablet, along with retina displays, have substantially changed how a user experiences your design. Responsive web design has emerged as a solution in some cases, but even though connection speeds on mobile networks are increasing, performance remains an issue.
Luke Wroblewski has a wealth of experience with the mobile web. He suggests that the definition of “mobile” itself is blurring as devices continue to evolve. Rather than designing for device specifications, Luke says it’s more important to think about the context in which these devices are being used.
During his virtual seminar, Organizing Mobile Web Experiences, the audience asked some great questions. Luke joins Adam Churchill to cover some of those questions in this podcast.
When you talk about “mobile”, does that include both phone and tablet? Is it better to use responsive web design than a separate mobile site? What are the benefits of native mobile applications vs. responsive UIs? How do account for different use cases when employing responsive web design? Does quality become an issue with the code base increasing to make sites adaptive? Should you make decisions on breakpoints based on content or device? Should you design differently for small screens and small windows?