{"id":914,"date":"2013-02-07T18:14:38","date_gmt":"2013-02-07T18:14:38","guid":{"rendered":"https:\/\/cookandkaye.com\/projects\/?p=914"},"modified":"2013-02-07T18:24:06","modified_gmt":"2013-02-07T18:24:06","slug":"websites-for-smart-phones-take-centre-stage","status":"publish","type":"post","link":"https:\/\/cookandkaye.com\/projects\/websites-for-smart-phones-take-centre-stage\/","title":{"rendered":"Websites for smart phones take centre stage"},"content":{"rendered":"<p><img loading=\"lazy\" src=\"https:\/\/cookandkaye.com\/projects\/wp-content\/uploads\/2013\/02\/flexible_design01.jpg\" alt=\"Your website might not work well on smaller displays.\" width=\"300\" height=\"350\" class=\"alignright size-full wp-image-921\" srcset=\"https:\/\/cookandkaye.com\/projects\/wp-content\/uploads\/2013\/02\/flexible_design01.jpg 300w, https:\/\/cookandkaye.com\/projects\/wp-content\/uploads\/2013\/02\/flexible_design01-257x300.jpg 257w\" sizes=\"(max-width: 300px) 100vw, 300px\" \/><\/p>\n<p>Since the start of the world wide web there has been a problem that the devices your visitor uses to view your website can be very different in their basic capacity for displaying your site. Over the last ten years this problem reduced, as visitors adopted a fairly standard &#8216;web-enabled-device&#8217; configuration consisting of a desktop computer, with a &#8216;modern&#8217; browser, and a screen of about 1200x800px in dimensions.<\/p>\n<p>Over the last five years, however, this situation has started to change again with the growing popularity of mobile devices, such as tablets and smart phones:<\/p>\n<blockquote><p>Global internet usage through mobile devices, not including tablets*, has almost doubled to 8.5% in January 2012 from 4.3% last year according to free web analytics company <a href=\"http:\/\/gs.statcounter.com\/press\/mobile-internet-usage-is-doubling-year-on-year\" title=\"Mobile access to websites.\" target=\"_blank\">StatCounter<\/a>.<\/p><\/blockquote>\n<p>While the stats above indicate that we need to start paying attention to these small-screen devices, the actual numbers of mobile browsers out in the wild is probably greater than that of our traditional desktop driving visitor \u2013 but browsing the web on a phone is, lets face it, painful.<\/p>\n<h3>HTML5 to the rescue?<\/h3>\n<p>The widespread adoption of HTML5 \u2013 which is not a recognised standard \u2013 is in part because it allows web-designers to adapt their designs for smaller screens, to smoothly simplify their sites, so that it works on a smart phone.<\/p>\n<p><strong>This approach is not without problems<\/strong> \u2013 the main smart-phone vendors are well aware that to be any use their browser must do a reasonable job of a &#8216;traditional&#8217; website, allowing visitors using their smart phone full access to the web. <\/p>\n<p>Often web designers actually make their sites worse by hacking out bits to simplify the site. This is particularly true if we try and adapt our sites for tablets \u2013 our philosophy (CookandKaye) is that these have large enough screens to manage all but the most bloated web layout, so generally we would leave well alone! <em>(This is also cheaper for you!)<\/em><\/p>\n<h3 id=\"back1\">WordPress 2012 theme \u2013 the web on its head<\/h3>\n<p>We use WordPress themes very extensively<a href=\"#go1\" title=\"More on the world's most popular content managment system.\">*<\/a> \u2013 with a small amount of customisation they offer a solid entry-level website for many of our clients. We therefore follow the latest theme developments with a great deal of interest. Over the last couple of years WordPress templates have attempted, with moderate success, to scale their layout to the smaller screen. <\/p>\n<blockquote><p>The latest template, however, changes everything by designing for the small screen, and then &#8216;going large&#8217; for desktop and tablet displays.<\/p><\/blockquote>\n<p><object id=\"back2\" class=\"center aligncenter\" type=\"application\/x-shockwave-flash\" data=\".\/wp-content\/uploads\/2013\/02\/flexible_design2.swf\" width=\"500\" height=\"280\"><param name=\"movie\" value=\".\/wp-content\/uploads\/2013\/02\/flexible_design2.swf\" \/><iframe loading=\"lazy\" src=\"https:\/\/cookandkaye.com\/projects\/wp-content\/uploads\/2013\/02\/design_for_smartphone.html\" width=\"500\" height=\"280\" class=\"aligncenter center\" align=\"center\"><\/iframe><\/object><\/p>\n<p><strong>Above:<\/strong> Movie showing the &#8216;smartphone first&#8217; approach to web design. It focuses on what you need on your page first, and makes this available to a small-screen display. This may then be enhanced in an all-singing and dancing large screen version<a href=\"#go2\" title=\"more on this topic\">**<\/a>.<\/p>\n<p>This really is a daring piece of design, taking on board the probability that in a relatively small space of time a lot of people&#8217;s main browser will be on their phone. This may already be the case with the traditional WordPress market \u2013 instant news from the blogs you follow should be available instantly, wherever you are, and on whatever device you have to hand (usually your phone). Where the cutting edge leads, however, it is likely that the rest of the web will follow. This may be a couple of years down the road, but still an important decision for a new website design.<\/p>\n<p>The advantages of the new WordPress design are obvious \u2013 in focussing on the mobile site first, you help ensure that a mobile user has everything they need from your website. There are, however, a number of downsides:<\/p>\n<ol>\n<li>Without enhancement the site looks a bit minimalist on a traditional display (and with a better processor). Thus we still have a two layer design, adding background images and multi-column layouts where these can be appreciated on a larger screen. The second layer is activated using HTML5.<\/li>\n<li>The bugbear is, however, Internet Explorer (as ever). Unfortunately a lot of people out there are still using older versions of IE, and these don&#8217;t understand HTML5. As a consequence we need a third layer \u2013 essentially an entirely independent set of styling instructions for these dinosaurs.<\/li>\n<\/ol>\n<p>The advantage of this design philosophy is that you only have one website to manage, and the clever 2012 theme delivers the appropriate styling for the device. The problem is that there is quite a lot of extra work required to follow this design practice.<\/p>\n<h3>Conclusions &#8211; where to with your website?<\/h3>\n<p>The WordPress 2012 theme is a great, future (and past) proof, all-round theme for basic sites. As long as you like grey, which is apparently the new black, again. If you can use it &#8216;as is&#8217; \u2013 go for it!<\/p>\n<p>Adapting the design philosophy to create bespoke sites will, however, add to the price (but probably not as much as a second mobile site). In deciding whether or not this is a good move for your business, you need to take into account the type of service you are offering. For many businesses and academic institutions, we expect the conversion to mobile browsing to be a bit behind the curve, so for a website lifespan of three to five years, the added cost may not be justified. <\/p>\n<p>If you have an existing site, you can check on the numbers of people using mobile devices on your site now (if you have these statistics), and work out where you are on the adoption curve. This may well indicate that a competent mobile site must be considered essential.<\/p>\n<p>======<br \/>\n<strong id=\"go1\">* We are not alone<\/strong> in recommending WordPress for a lot of our work. It accounts for over half of all CMS driven websites, and one in six of ALL websites (Feb 2013 <a href=\"http:\/\/w3techs.com\/technologies\/overview\/content_management\/all\" title=\"Content management strategy statistics\" target=\"_blank\">w3techs.com<\/a>) (<a href=\"#back1\" title=\"Back to WordPress 2012 theme.\">BACK<\/a>)<br \/>\n<strong id=\"go2\">** Now with HTML5 movies<\/strong> &#8211; these are rather larger than the old Flash movies, but can play on mobile devices, though prone to jitters as the graphics processor on mobile devices is very under-powered compared to desktop machines. <em>This may be one reason Apple chose not to support Flash, as Flash movies have to be re-generated on the fly &#8211; making for tiny downloads, but lots of graphic processor work&#8230;<\/em> (<a href=\"#back2\" title=\"Back to the design for smartphone first movie\">BACK<\/a>)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Since the start of the world wide web there has been a problem that the devices your visitor uses to view your website can be very different in their basic capacity for displaying your site. Over the last ten years this problem reduced, as visitors adopted a fairly standard &#8216;web-enabled-device&#8217; configuration consisting of a desktop [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[7],"tags":[],"_links":{"self":[{"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/posts\/914"}],"collection":[{"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/comments?post=914"}],"version-history":[{"count":27,"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/posts\/914\/revisions"}],"predecessor-version":[{"id":943,"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/posts\/914\/revisions\/943"}],"wp:attachment":[{"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/media?parent=914"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/categories?post=914"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cookandkaye.com\/projects\/wp-json\/wp\/v2\/tags?post=914"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}