{"id":54,"date":"2014-06-04T01:10:18","date_gmt":"2014-06-03T16:10:18","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/%eb%b0%98%ec%9d%91%ed%98%95-%ec%9b%b9-%ea%b7%b8%eb%a6%ac%ea%b3%a0-%ec%a0%81%ec%9d%91%ed%98%95-%ec%9b%b9\/"},"modified":"2026-11-21T22:16:36","modified_gmt":"2026-11-21T13:16:36","slug":"responsive-web-and-adaptive-web","status":"publish","type":"post","link":"https:\/\/www.studio-jt.co.kr\/en\/responsive-web-and-adaptive-web\/","title":{"rendered":"Responsive Web and Adaptive Web"},"content":{"rendered":"<h2>What Are Responsive Web and Adaptive Web?<\/h2>\n<p>Adaptive web and responsive web are both, at heart, ways to give a better mobile user experience by making a website deliver information smoothly on mobile devices and on many screen sizes.<br \/>\nHowever, adaptive and responsive web differ a lot, from how a site is designed to how it runs. Korean search engines have little information on &#8216;adaptive web&#8217;, and much of it is wrong, so we put together this summary based on information we found through international search engines.<\/p>\n<p>Reference link 1 <a title=\"New window\" href=\"http:\/\/visual.ly\/adaptive-web-design-vs-responsive-web-design\" target=\"_blank\" rel=\"noopener\">(http:\/\/visual.ly\/adaptive-web-design-vs-responsive-web-design)<\/a><br \/>\n&#8216;Adaptive web&#8217; checks, on the server or the client, which device has accessed the site and calls the markup optimized for that device. Here, optimized markup means it shows only the information that is really needed, uses images optimized for the device, avoids Flash, and uses JavaScript to analyze the device and apply the right behavior. This lets people use the website on mobile at a faster speed.<\/p>\n<p>A feature of adaptive web is that you don&#8217;t need to rebuild your existing site, and you can get optimal performance on many devices. &#8216;Responsive web&#8217;, on the other hand, uses media queries to check the screen size, and flexible images and grids resize to fit as the screen size changes. It holds the information for all devices, which is downloaded and used depending on whether it&#8217;s needed. It uses only one template, so even though the user is on one device, they have to wait until the page for every device has loaded. If you already run a site, you have to rebuild it, and you have to customize for every device it can be used on, so design and testing can be difficult.<\/p>\n<p>Features of responsive web: it is easy to add new web builds, the site has to be rebuilt, and performance may drop depending on the device.<\/p>\n<p>Reference link 2 (http:\/\/despreneur.com\/responsive-web-design-vs-adaptive-web-design-whats-the-difference\/)<br \/>\n\u300c If you\u2019ve designed your website using adaptive web design, then to do a single change you\u2019ll have to redo SEO (search engine optimization), content and linking for the entire website. Unlike this, if you\u2019ve chosen responsive web design (RWD) performing a single change will be as simple as ABC because the SEO, links and content settings get carried over via the in-tact HTML\/CSS3 and Javascript. \u300d<\/p>\n<p>&#8211; For a site designed as an adaptive website, you have to redo the content and links for SEO (search engine optimization) with every single change? We didn&#8217;t fully understand this, but looking at reference link 5, it seems to mean that a PC-based website and a mobile-based website, for example yoursite.com \/ m.yoursite.com, end up with URLs that have the same content, which most search engines treat as duplicates, so it is not SEO-friendly.<br \/>\nHowever, reference link 5 says something different on this point.<\/p>\n<p>Reference link 3 <a title=\"New window\" href=\"http:\/\/torquemag.io\/responsive-design-vs-adaptive-design\/\" target=\"_blank\" rel=\"noopener\">(http:\/\/torquemag.io\/responsive-design-vs-adaptive-design\/)<\/a><br \/>\n\u300c Adaptive web design may probably hurt your terms with search engines. For example, an article that is available at yoursite.com\/nice-article will also be available at m.yoursite.com\/nice-article. Most search engines do not appreciate identical content across multiple URLs, so it can be argued that adaptive design is not as SEO-friendly as responsive design. However, I feel that this might just be a matter of perception\u2014the identical-content-across-multiple-URLs-is-evil rule generally applies to sites that copy content from other sites. Maybe search engine bots are smart enough to figure out that m.yoursite.com is an mobile-friendly variant of yoursite.com\u2014in any case, as already mentioned earlier in this article, Google has often professed its appreciation for responsive web design, so adaptive design does lag a bit behind in terms of SEO. \u300d<\/p>\n<p>Reference link 4 \u2013 Comments<br \/>\n\u300c Dmitriy February 7, 2014 at 09:40\u300c Adaptive design is much more harder to maintain\u2026 My weapon of choice is twitter bootstrap and html5+css3 magic. \u300d<br \/>\n&#8211; Adaptive web is harder to maintain. My weapons are Bootstrap and the magic of HTML5 and CSS3. 2&gt; Bientang February 9, 2014 at 08:44<\/p>\n<p>\u300c AWD is much harder for web developer, but i think, if, AWD has separated HTML &amp; CSS that optimized for each device\/gadget, AWD is more mobile friendly, you know, fast load on mobile browser. RWD, i think, it\u2019ll load the same HTML &amp; CSS as desktop version. \u300d<br \/>\n&#8211; Adaptive web is harder for developers, but because HTML and CSS optimized for each device load quickly on mobile, I think adaptive web is more mobile-friendly. 3&gt; JTech Communications February 14, 2014 at 16:03<\/p>\n<p>\u300c This is a good article, I think that it highlights the differences between AWD and RWD quite nicely. There are two things that I would like to mention.<\/p>\n<p>1) There is a raging ongoing debate about how to make RWD faster. I think that the slow load times that are associated with RWD are likely just a passing thing; while RWD will always take a little bit longer to load I think that issue will diminish as time goes on. Also with the huge move toward mobile the speed of mobile devices will likely increase, especially in North America and Europe.<br \/>\n&#8211; There is an ongoing, heated debate about how to make responsive web faster. The slowness of responsive web will shrink over time.<\/p>\n<p>2) The second thing is that we are a web development firm, and we recommend to almost all of our clients that are building a new site that it be responsive. As you said RWD requires an entirely new website, so I think that it is likely that AWD will be a passing trend as the web switches over to RWD to accommodate the shift to mobile. \u300d<br \/>\n&#8211; We are a web development company. We recommend that almost all of our clients build a new responsive site. As you said, responsive web needs an entirely new site, and the web is switching to responsive web to accommodate the shift to mobile. I think adaptive web is likely to be a passing trend.<\/p>\n<p>Reference link 5 <a title=\"New window\" href=\"http:\/\/en.wikipedia.org\/wiki\/Adaptive_web_design\" target=\"_blank\" rel=\"noopener\">(http:\/\/en.wikipedia.org\/wiki\/Adaptive_web_design)<\/a><br \/>\nAccording to Wikipedia,<br \/>\n\u300c Adaptive web design is basically the same as responsive design and shares many of the same ideals and goals. The main difference however is that the changes are made on the server side rather than the client side.<br \/>\nWith adaptive delivery, the most significant difference is that the server hosting the website detects the devices making requests to it, and uses this information to deliver different batches of HTML and CSS code based on the characteristics of the device that have been detected. \u300d<br \/>\n&#8211; The main difference between &#8216;adaptive web&#8217; and &#8216;responsive web&#8217; is that adaptive web checks the user&#8217;s device on the server side, not the client side, and delivers different batches of HTML and CSS code based on that device.<br \/>\nHere, the scope of the definition of &#8216;adaptive web&#8217; is slightly different from what reference link 1 says.<\/p>\n<p>[\u203b All translations may contain significant mistranslations.]<br \/>\nEven on international search engines there wasn&#8217;t much information about &#8216;adaptive web&#8217;, and while the big picture was similar, the details differed a little. With the information we found so far, we couldn&#8217;t clearly separate &#8216;adaptive web&#8217; from &#8216;responsive web&#8217;. But in our brief view, &#8216;adaptive web&#8217; is not something new. It is a method that was already in use before technology grew (HTML5, CSS3, Bootstrap and so on) and before &#8216;responsive web&#8217;, and it may be little more than a trend that offers a temporary fix for the responsive web speed problems that are talked about so much right now.<\/p>\n<h2>Reference<\/h2>\n<p>&#8211; <a title=\"New window\" href=\"http:\/\/visual.ly\/adaptive-web-design-vs-responsive-web-design\" target=\"_blank\" rel=\"noopener\">http:\/\/visual.ly\/adaptive-web-design-vs-responsive-web-design<\/a><br \/>\n&#8211; http:\/\/despreneur.com\/responsive-web-design-vs-adaptive-web-design-whats-the-difference\/<br \/>\n&#8211; <a title=\"New window\" href=\"http:\/\/www.techrepublic.com\/blog\/web-designer\/what-is-the-difference-between-responsive-vs-adaptive-web-design\/\" target=\"_blank\" rel=\"noopener\">http:\/\/www.techrepublic.com\/blog\/web-designer\/what-is-the-difference-between-responsive-vs-adaptive-web-design\/<\/a><br \/>\n&#8211; <a title=\"New window\" href=\"http:\/\/en.wikipedia.org\/wiki\/Adaptive_web_design\" target=\"_blank\" rel=\"noopener\">http:\/\/en.wikipedia.org\/wiki\/Adaptive_web_design<\/a><br \/>\n&#8211; <a title=\"New window\" href=\"http:\/\/torquemag.io\/responsive-design-vs-adaptive-design\/\" target=\"_blank\" rel=\"noopener\">http:\/\/torquemag.io\/responsive-design-vs-adaptive-design\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> A look at responsive web and adaptive web.<\/p>\n","protected":false},"author":1,"featured_media":125,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[13],"class_list":["post-54","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dev"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/posts\/54","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/comments?post=54"}],"version-history":[{"count":2,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/posts\/54\/revisions"}],"predecessor-version":[{"id":2509,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/posts\/54\/revisions\/2509"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media\/125"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=54"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/categories?post=54"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}