Focus on the limitations and pitfalls of Web response design

Multi-device Test response web site

We've covered a lot of ideas about how to create response sites-using flexible layouts, media queries, image scaling, and other techniques, so that the site works well on a variety of screens and looks good. The current response design has received a lot of attention, well-known web sites. NET on the first page there are 60% articles in the discussion on this topic.

However, sometimes it is helpful to focus on taboos in web response design. Recently, the response Design Master, Brad Frost, has published in the. NET Magazine the five most common mistakes that designers have made (Webapptrend are translating). It refers to the error of using a specific size screen to trigger layout changes and to avoid applying a single dimension to all screens.

With regard to the latter, Frost wrote:

"A variety of mobile devices are not just different screen sizes ... Nor should we satisfy ourselves simply by creating a response layout. For example, we sometimes forget that mobile phones can be positioned, talked, and so on. Browsers on these devices are expected to provide more access to the device's APIs in the near future, which will further expand the functionality of the Web.

We should give full play to the hardware function of the equipment. Processing constraints laid a good foundation for us, and then we can use incremental enhancement, feature detection and other technologies to further improve the user experience. ”

This post is worth reading. But we want to add the sixth rule: don't think what you developed yesterday is still the best thing to run tomorrow.

This is not to say that what you are developing today will not work tomorrow. It's just that there may be a simpler way to achieve the same functionality.

Web Response design is an emerging challenge, and the best solution for Web Response design is still in the making. This is a painful thing to do, but it also means that some smart people are working on some very difficult issues that you can benefit from (if you want to know).

New things are always popping up, perhaps a new way to process response images, or a browser upgrade to support more CSS features. We recommend that developers take some time to read the latest technical tips and tricks before developing new projects. New response design tools are being developed and perfected, and when you develop the next response site, the hack you use in the previous project may have become a stable, well maintained, JavaScript library.

This article compiles from: Lin Jianguang, the original link.

Source of translation: webapptrend.com