Where I work, we have 11 Designers/Front End Developers who work together in the User Experience arm of the company. We’ve been aware that Responsive Web Design is an important concept to grasp in order to meet the needs of our customers. In fact, we discussed it during my interview before they hired me last summer! Responsive Web Design is not the sole means by which our company is addressing the needs of users outside of the desktop environment, but we have decided to make it a part of our baseline structure. We think it is that important.
My pal, Brad Dielman, alerted me that a bruhaha regarding responsive images existed. He had to focus my attention on it because I missed all the Twitter traffic highlighting the web community’s ire was raised over something other than vendor prefixes. As a result, I’ve read a lot about the proposals for addressing content images (stuff inside the
<img /> tag in HTML) in an increasingly “Responsive Web Design” colored world. (more…)
Those of us who came into the Front End Development profession approximately 5 years ago had the ability to learn it in a much more stable environment, if you will. Mobile wasn’t a “thing” like it is now. CSS3 wasn’t a thing yet, it was just a dream we drooled over. Preprocessors weren’t a thing. Responsive Web Design wasn’t a thing. This field of study is so much broader with so many more considerations.
I know it can be argued that there was always a lot to learn or that the topics we consider “things” today were always important. We’re just more vividly aware of it now, thanks to device proliferation. Regardless, people coming into the Front End Development specialty today have so much more to grasp at the onset than we did 5 short years ago. I dare say we had it a little easier, even if IE6 made us cry bloody tears all the time.
And it isn’t going to get easier, imo.