Drew Thomas is the chief creative officer and a co-founder of Brolik, a Philadelphia digital agency. While Brolik is his focus, he also considers himself a “maker” and tinkers with all kinds of side projects, both digital and physical.
Digital experiences are emulating real life more and more every day. This may seem counterintuitive, considering the hate that rains down on skeuomorphic visual design, but there's a lot more to emulating real life than aesthetics.
Interface designers can emulate real-life physics and movement on a digital screen. This type of motion is becoming more common, which is why it's becoming easier for people to understand computers. We're not getting better, the interfaces are!
Information about customers has never been available on the scale it is today. Businesses are learning new ways to leverage data to improve themselves on a daily basis. They’re realizing that data collection and data analysis have a measurable return on investment, and decision-makers are asking to see them.
As a developer, business owner or marketer, you need to know how to gather data and how to do it efficiently and in a scalable way. Furthermore, you need to understand what that data means and how to present it.
When considering a mobile Web strategy and weighing responsive Web design against a separate mobile website, the most important metric is how functional the website is for the user. This goes beyond better content organization for smaller screens.
Mobile (and desktop) websites should be easily found, easily shared, fast loading, easy to maintain and easy to build on. If we keep that in mind, considering where the Web is today and where it looks to be going, there are many compelling arguments for responsive Web design.
With all the talk about responsive Web design, designers and coders are moving even further from the fixed pixel layouts of design’s print-based history. We’re finally thinking in terms of fluid layouts and expandable, interactive content. But when you get down to it, we’re still thinking of the fluidity in terms of desktop, tablet and mobile sizes.
Chances are that your responsive websites have media query breakpoints at precisely the tablet and mobile widths, essentially creating three different versions of a website with the same code. While this is much more ideal than what we’ve all done until now, it’s not always the best way to approach things. Often, our content breakpoints (the viewport widths where content should be reformatted) are different from common device breakpoints (the viewport widths that reflect physical devices).