The Internet is changing, with responsive websites quickly adapting to any device and screen size to bring the user the most dynamic experience possible. From multinational corporations like Sony, Microsoft, and Nokia to global tech stars like Salesforce to online travel giants like Expedia, serious players are turning to responsive web design to march in step with the current trends in and reach an even wider audience of customers.

But making responsive websites has its downsides. The value the site provides to the user is more important than ever, and aesthetics often take a backseat while performance reigns supreme. The problem is that performance cannot be mocked up in Photoshop, and new methods to meet design challenges have to be adopted. So here are 10 problems with creating responsive design websites, along with 10 possible solutions.

1. A More Problematic Visual Stage

In the past, the client had to approve static images and screenshots before development could begin. Today, designing can be a more chaotic and fluid process of sketching and prototyping where the focus is on designing elements and how they will be rearranged, depending on different device dimensions and resolutions.

Fix: There are two approaches to responsive sketching. One approach is creating sketches for a desktop home page, as well as every other website page, and then adapting them for the most popular tablet and mobile screen sizes and dimensions. Another approach is using paper and communicating to the client to demonstrate design layouts and how they will reflow on different screen sizes. Designing in the browser and working with HTML and CSS prototypes starts early on; creating a system of components and seeing how they can be reassembled for different configurations replaces the creation of wireframes for every single page and state. The chosen method is usually dictated by the complexity of the website.

2. Navigation

Before responsive design, every user knew where navigation was. Even though today, the three bars at the top left corner of the page usually represent the de facto navigation "button," many users still find it difficult to navigate beyond the menu, especially when it comes to websites with complicated structure. Today, the whole concept of navigation has to be reconsidered.

Fix: Designers should spend more time trying to make navigation intuitive and self-explanatory. Studying the website’s content and information architecture, and understanding users—how and why they browse the site—is the only way to make a unique navigation decision. In addition, testing navigation on as many products as possible can help developers get it right.

3. The Appearance of Background Images and Icons

Images are crucial to a user’s experience on the web. In responsive design, images and icons have to be flexible to allow users to enjoy the graphics on high pixel density devices, which are becoming more widespread. Making sure the images don’t look blurry and poorly scaled up is the goal of every designer and developer.

Fix: Lazy loading images can help optimize browser rendering and reduce the number of HTTP round trips by deferring the loading of images that are not in the client's view. Making icons scalable (using the SVG format, which keeps icons light yet high-quality) and retina-ready can also help users enjoy the website without loss of quality on any device.

4. Showing Data on Small Screens

Showing data tables (airline flight timetables, for instance) on small screens is a real problem when the tables are complex and convoluted. It doesn’t help that they are also often large with a great number of rows and columns.

Fix: Responsive tables are the best bet right now. There are also other methods: abandoning the grid layout and creating a smaller table that doesn’t call for horizontal scrolling; building more compact pie charts out of tables; replacing tables with smaller versions while offering a link to the full version; hiding unimportant elements on small screens with a dropdown menu with access to the full table; rainbow tables where colors are used instead of columns; and even flipping the table on its side to make it fit.

5. Creating Rich Experiences that Load Fast

One of the biggest challenges is finding the balance between a rich user experience and the fast-paced nature of the Internet. Responsive websites sometimes weigh a lot, and because they attract traffic from both desktops and mobile devices, the experience can suffer from slow loading times. This means losing business, as the majority of mobile users leave after five seconds of not getting what they expect.

Responsive websites sometimes weigh a lot and the experience can suffer from slow loading times

Fix: The solution is conditional loading, which allows for loading of only what users need, when they need it. The rule of thumb is this: first load content, then enhancements, then leftovers. With users so used to lots of images, galleries, documents, downloads, etc. on awebsite, with the mobile-first approach, designers should take care to keep only the elements that are absolutely necessary to convey the message of the website. Because the proliferation of mobile devices is outpacing desktops, conditional loading is the way to go. And since in conditional loading many automation tools for scaling and caching images are used, it makes future changes to the site easier and faster. Also, assuming that the user connection is not perfect is a must to provide high performance.

6. Longer Designing, Developing, and Testing Periods

Because responsive websites have to work amazingly well on multiple (very different) devices—all while boasting rich functionality and complicated design elements—they often take longer to design, develop, and test. Usually it takes about twice as long to design a responsive site compared to a regular site.

Fix: The problem already contains a solution. Even though responsive sites may take longer to create, they are also better candidates for gradual change and natural evolution. Instead of having to implement major overhauls to a website, which are costly and lengthy, responsive sites can evolve step-by-step, saving owners a lot of time and effort in the long run.

7. Hiding and Removing Content

Websites with complicated UI elements, advanced search features, multi-step forms, data tables, calculators, dashboards with third-party scripts, and so on often pose a problem because they simply contain too much information. The approach so far has been to hide or remove content from users, but many people feel they deserve access to all information, even if they are browsing on a small device. In some cases, there is no way for a user to get the full version of the website they are browsing.

Fix: Thorough planning from the onset that determines where content is arranged in a way that doesn’t force developers to hide anything is the solution. The goal should be to optimize as much as possible, remove unnecessary elements from early drafts and focus on the core structure of the website, without adding any bells and whistles. Now is not the time to embellish, but to prioritize and cut. It is always best to give the user the possibility to have access to the full version of the website, if they choose to do so.

8. Converting Fixed Sites Into Responsive Ones

This is a huge dilemma: is it necessary to change the less flexible code of fixed-layout websites or can they be left as they are and still provide acceptable performance?

Fix: The conversion process is a challenging, but for light and simple websites, it’s feasible and has been done successfully in the past. The choice is often to reverse style sheets and templates or start a greenfield rebuild, which is a process of rebuilding the site without the need to consider any prior work. When you have a bigger, complicated website, a greenfield rebuild is a better option than not doing a conversion at all.

9. Older Versions of Internet Explorer Don’t Support CSS3 Media Queries

When working with mobile-first techniques, your website might not display properly on older versions of IE. In these cases, developers should find a way to support an older website on mobile devices.

Fix: It is best to take care of Internet Explorer users and to offer them a handy solution. An experienced designer can easily change page layouts, depending on the size of the browser window, using JavaScript. With a goal of maintaining the original layout, the solution is to use polyfill, which is a portion of code that provides the technology that developers expect the browser to provide natively. Another fix may be to use a conditional IE style sheet with elementary styling or do nothing at all if it looks passable. It all depends on the needs of the end user.

10. Not Everyone Understands Why They Should Go Responsive

The process of working with clients is not always structured and orderly, and the methodologies for responsive design are still being refined and tested. Solutions to challenges are rarely set in stone, which sometimes creates uncertainty and confusion for clients.

Fix: Showing the benefits of responsive design in action is the best way to get positive feedback and approval. Responsive design can prove itself a significant advantage in the market in terms of multi-device functionality, making future fixes easy, and appealing to a much widest audience of users.

Conclusion

Even though responsive design is becoming more popular, there are still many questions left unanswered and no official solutions to the challenges that this trend poses. The most important thing to remember is that responsive design should improve experiences, not reduce opportunities for users, and all designer and developer efforts should be aimed at making that goal a reality.

 

Image of man using mobile device courtesy Shutterstock.

Article No. 879 | October 2, 2012
Article No. 1 301 | September 4, 2014
Article No. 837 | June 12, 2012

Add new comment

Comments

Good work kirill, for highlighting the problems and the solutions.

More than 80% of the internet users are using their smartphones & handheld devices to use the internet. So it's better to avoide such issues and design a responsive websites that quickly adapt to any device and screen size. 

Thanks for Sharing the information.I learnt the importance of Responsive site.I would like to Share my ideas and articles with you

 

Great post on the responsive design. Great work.

Nice Article.Thanks for posting this. We are same fields . For more information do visit our website http://bit.ly/1w2VfBZ

Hi Kirill, 

Excellent article! The importance of mobile responsiveness is something we've been trying to emphasize for a long time. As a company who mass-publishes thousands of content-rich RESPONSIVE websites, our web to mobile converter has been in the final stages of development for a little while now. Soon, we will be able to turn any website into a mobile-optimized and responsive website, and FAST. For now though, all of our websites come with mobile-optimization baked into them from the start. 

Thanks again for the insights, 

Taylor Graham

 

Besides those responsive design problems and fixes we need to maintain an adjustive web design. As the technology is evolving continually, we need to optimize the way we display content. A new concept that helps you achieve it is the "Adjustive" web design. Read more http://goo.gl/Dw94FJ

For images, services like this http://web.wurfl.io/#wit are very useful (free of charge, btw). This will scale and optimize the image to fit the device the user has. Works well with the new and shiny srcset too.

missed one more important thing ! Fonts 

big question, whether to go with px or with em. And if any, then how ?\

Would love to read, if you could say over this also.

Well, to my mind the px or em do not make any difference to responsive design whatsoever, rather than they contribute to the simplicity of your CSS.

Say you have ten classes .class1, .class2, etc. If you stick with px you would have to declare 'font-size: .. ' for each class in every '@media()' that you use. With 'em' you would just declare a single 'font-size: ..' for your 'body'. Which ultimately would eliminate 9 lines of code for every '@media()' that you use.

It's not a 'responsive design problem' rather than plain common sense.

P.S. Great article, Kirill!