LinkedIn Facebook Twitter bemoko blog bemoko technical pages
Tel: +44 1256 581028 Email:

Bemoko blog > responsive design



bemoko is acquired by SDL- blog

Posted By Emily Nicholls Wednesday, March 6, 2013. No Comments

In order to deliver leading edge products your R&D efforts need to be constantly one additional step ahead of the ‘leading edge’,I have heard this called the ‘bleeding edge’ or basically predicting the future!

Since we founded bemoko in 2007 predicting the future has basically been our job, looking way out there at technology trends, consumer adoption and technical advancements in both software and hardware and assessing what’s going to shape the future technology landscape.

bemoko has been amazingly adept at getting our predictions right, which I think comes down to having immense passion for what we do. In 2007 long before the first smart phone, we built our mobile web delivery platform designed to deliver mobile web for any device. In 2007 this seemed like a bonkers idea, but we were all passionately convinced that pretty soon companies would need to take a mobile first approach to web development – a concept that is just emerging today and one that bemoko have the leading and most advanced solution to deliver against.

With all things web and especially mobile, nothing stands still for long so as we continue to innovate we continue to look ahead what we need to do to remain at the leading edge. So what does that look like? Our overarching feeling is that devices, desktop, mobile, tablet and all the other groovy things like Google glasses will soon just merge into “web” pretty soon developing in silos will be a thing of the past, we’re calling this One
Web; an environment where people will surf, shop, play, chat, and do all the other things that being “constantly connected” will deliver but the physical device will be secondary.

In this new and exciting environment the biggest challenge will be managing a customer’s experience as they move across channels and devices – their expectation will be one of a seamless experience that adapts and morphs to the specific time, place and interface. So as important as the ability to deliver content ubiquitously, the content itself will need to be highly adaptive and interpretive. This is next generation customer experience management (CXM)

This new era of CXM, which we are all approaching at break-neck speeds will require advanced technology and broad expertise drawn from what are currently slightly different but aligned technology backgrounds of content management and user experience, and cross device delivery (e.g. mobiles, tablets, cars and TV’s etc.) Bring these two elements together and the result will be at the cutting edge of ubiquitous computing (Sometimes referred to as omni-channel)

So in our quest to innovate and continue to provide leading edge services we have brought bemoko and SDL Plc an international provider of digital customer experience management solutions together in an acquisition of bemoko by SDL. Adding the bemoko multichannel delivery technology into SDL’s suite of customer experience management solutions will enhance SDL’s existing capabilities and deliver an incredible combination of products built for the next generation of web – ‘One Web’.

We are all hugely excited to be in a new home with new technology capabilities,wider expertise and an international footprint and are looking forward to continuing to be at the leading edge for many years to come.

Mobile is changing
Web content is changing
Internet is changing

For further information visit

Please feel free to comment and share

Phillip Clement – @PhillipClement

Share and Enjoy:
  • Digg
  • Sphinn
  • Facebook
  • Mixx
  • Google Bookmarks

Posted in: business, mobile, mobile design, mobile friendly, mobile search, mobile technology, mobile UX, mobile web, multichannel, public website news, responsive design, retail, web optimisation



Responsive Design “delving deeper”

Posted By Emily Nicholls Thursday, January 31, 2013. No Comments

With so much interest in ‘Responsive Web Design’ in 2012, we have delved deeper to see if this is the right approach for Web Development moving forward. For many it offers a low cost approach to a write once web development. However, there are limitations and this article tries to explain these, and how the Responsive Web Design concept can be taken to a more dynamic and vastly improved user experience.

What is it?
Responsive web design is the approach taken to ensure that the website layout adapts to the browsers viewport (the dimensions of the browser window in which the website is displayed, not including the scroll bars and address bars etc).

How is it done?
Responsive Web Design is traditionally made possible through the use of CSS Media Queries, JavaScript can then take this one step further, and can be used to modify the DOM (the structure of the markup)

These allow for a set of CSS styles to be applied when the browser is in a certain condition.

Typical queries are:
• Width & Height@media screen and (min-width: 400px) and (max-width: 700px)
• Orientation@media all and (orientation:portrait) { … }
@media all and (orientation:landscape) { … }
• Aspect Ratio@media screen and (device-aspect-ratio: 16/9) { …

Using javascript it is possible to detect if the browsers screen has changed size by listening for the onresize() event.
When a screen change has been detected, you can make the required DOM modifications to adjust the layout of your content to the new browser view port dimensions.

Problems with this approach
Responsive Web Design works best when used in small edge case scenarios, as it able to deliver rapid layout changes, without the backend heavy-weight that is device knowledge. However, when delivering sites outside of these edge-case scenarios, Responsive Web Design may not be the best approach. Particularly when targeting a wide range of devices and browsers. When using Responsive Design with the traditional methods of CSS and Javascript for this, a few problems are introduced:

Page Weight
With media queries, there is much redundant styling that will never get used by the device under any circumstance. All this redundancy dramatically increases the page weight, which in turn slows the browsing experience of your site down.

While CSS media queries are fast to adapt content upon viewport changes, the actual .css files are fairly hefty as all styling for all eventual layouts are included in the page. So you are potentially increasing the size of your style sheets by a multiple of the number of layouts you are targeting.

Depending on the size of your size, and the amount of DOM manipulation needed, your JavaScript files could also run the same issue as CSS.

CSS can hide/display/resize images, but this does not help with the actual download of the image. If an image has display:none it has still been downloaded by the browser in its original format.

Unexpected onresize() events
When using onResize(), pay caution to the many unexpected events cause the event to trigger. These are the events known to trigger this event:

• User resizes browser window by dragging the corner or edge.
• Users enters full screen or window view of browser.
• The orientation of the device switches from landscape to portrait or vice-versa.
• Modification to the DOM which causes the scroll bar to appear within the browser, in effect reducing the view port.
• When the users scroll down the page, and the address bar is hidden, this increases the size of the view port and hence fires this event.
• User changes the zoom level
• The view port meta changes

Clunky Reloads
A technique that some sites have incorporated is to refresh the page upon a change in viewport. This will reset the users page view progress, and potentially also lose input field information as the page is in effect reloaded.

On smart phones, users tend to browse the site in ‘Portrait’ mode, but when they are then asked to input details in a complex form, they prefer the keyboard display in ‘Landscape’ mode.

Unexpected User Experience
As a user is browsing the site in a ‘Portrait’ mode, and they then switch to a ‘Landscape’ mode, the layout that the user should now see should not be dramatically different. Any adjustments to the navigation may throw the user off, as they will need to readjust their ability to use the site.

Hard to maintain and improve
Having multiple style sheets for all the possible viewport groups that you wish to support which modify the layout of each, as well as handling the JavaScript interactions and DOM manipulations, can become hard to maintain. Especially when a new feature needs to be imposed on the site that requires specific JavaScript function or CSS styles, ensuring that it does not break on other devices remains a challenge.

Many solutions can be derived through client-side javascript that will “pull” content from the server, and manipulate it to display the desired layout. Although possible, this approach has its inherent problems. These mainly boil down to:-

1. Latency The time it takes to pull content via javascript over the mobile network. For example updating images from a 240px initial load, to 980px will result in an increased page load.

2. Re-rendering the user may see the “lowest denominator” version of the site while content is being pulled and manipulated by the browser, resulting in a “Clunky Reload”.

3. Slow UX Javascript intensive pages will slow down the browsing experience, causing lags in scrolling and animations and other navigation elements.
A more practical approach to Responsive Web Design is to integrate the discovery services of device recognition, the processing power of server-side mark-up manipulation and image delivery, and the final tweaking using CSS media queries and JavaScript.

Using these combination methods, here are some suggestions for Responsive Design Practice to help reduce the known issues identified earlier:

Targeted Responsive Design
Using intelligent capability discovery will, through tools such as device databases, will allow developers to deliver content that is known to be supported by the requesting device, such as:
• Only deliver responsive style sheets to devices that support it.
• Only deliver styling that will actually get used by that device (i.e. do not deliver a media query of width > 800px if that device can never achieve that width)
• Only deliver JavaScript to devices that can handle it well.
• Only deliver optimized images for that device.

Scale Up
If relying on responsive design, make sure that your page “scales up” to the highest denominator, instead of “scaling down” a PC based site to fit on a mobile.
This not only reduces page weight, but also ensures that the devices that can support the intensive DOM manipulation and enhanced CSS styling will be using their full capabilities to do so.

Ajax Reload of Selective Content
Instead of reloading the entire window, use AJAX to reload sections of content that are affected by the new viewport. This technique will keep the page weight to a minimum, as content is only loaded when needed.
A great example of this would be to just reload the images when a browser orientation changes from ‘Landscape’ to ‘Portrait’.

Adaptive Personalisation
Users should always be given the option to view you site in Full mode. Some users prefer to pinch and zoom their way around a regular designed for pc website, as they feel that the content is more complete or that they are more comfortable with that navigation technique.
Allowing the user to toggle between the Full site and the responsive site will give that user the freedom. Once their selection has been made, their preference should be saved, and so on subsequent visits, the user will have their preferred view.

Use an onresize() Margin of Error
When using Javascript to adapt the layout of a device based on the onresize() javascript event, build in an margin of error to allow for accidental give and take. A margin of error of 15% should ensure that no DOM modifications are taken when the browser makes slight adjustments to the viewport as described above causing an overuse of DOM manipulation slowing the browsing experience down. Better still, only adapt when the onresize() will cross the threshold between viewport layouts that you have designed.

Integrating a server-sided approach with client-sided responsive design has many benefits over choosing one over the other.

No Compromise
When developing a responsive site, you are taking a conscious decision to exclude devices that are unable to handle CSS media queries, javascript, or even heavy pages. Alternatively, development could follow the approach to design for the lowest common device, and so more advanced devices are suffering from lack of inclusion, rendering their technological abilities void.

Server Side Platforms
Integrating with a server-sided platform, these devices can still be treated equally, providing access to the same content through alternative means of navigation, layouts and styling.

Only delivering mark-up to devices that support it, and also delivering only relevant mark-up, not only reduces page size, but also reduces the risk of browser hangs and crashes. On mobile devices, it is common for websites with large amounts of Javascript and CSS to cause the browser to crash as the complex queries are too much for the browser rendering engine.

Easier to maintain and enhance
Using Bemoko’s hierarchy approach, breaking down your styles and JavaScript into your defined UI groups will make it much easier to know where changes need to be made, and what will be affected when that change has been made.
Through a combination of our deep mobile expertise and unique technology capability we help our clients to become class leaders in mobile.

During testing, specific devices may throw up rendering abnormalities, and implementing work-arounds for these can be done effectively by targeting the specific device. With responsive design, the ‘work-arounds’ are all included in the CSS or JavaScript which gets delivered to all handsets, not just the devices that require it.
As the capabilities of devices improve, and new technologies become available, dropping these into specific UI Groups will instantly enhance the site. These groups can be targeted to ensure that these will work, and will not break existing functionality on older unsupported devices.

Faster page loads
Page weight is comprised of markup, CSS, JavaScript, and images. Therefor it is evident that reducing page weight will increase page load speeds, the most important factor in mobile web development. Consumers losing patience with the slow mobile web and How Loading Time Affects Your Bottom Line do an excellent job on describing how important page loading times are, and how it can affect business.

Standalone, Client-Side Responsive Web Design works best when the site is targeted to a particular browser or device class. For example, if you only want to support iPhone and Android devices, manipulation of layout via media queries and JavaScript will be a sufficient approach. However, when you wish to develop a site that will work across almost any browser (PC, Tablet, Smartphone, Feature phone, etc) a combination of both intelligent server-sided adaptation and client sided responsive tweaking will be best suited to the task.

By Olaf Dunn @olafdunn on twitter

Share and Enjoy:
  • Digg
  • Sphinn
  • Facebook
  • Mixx
  • Google Bookmarks

Posted in: fundraising, mcommerce, mobile, mobile design, mobile search, mobile technology, mobile UX, mobile web, multichannel, responsive design, web optimisation



Solving the mobile conundrum

Posted By Mat Diss Tuesday, December 11, 2012. No Comments

If you are in charge of delivering your company mobile strategy, you are more than likely receiving multiple differing views on the subject from many different people. Should you go responsive, should you use a separate mobile site, should you use a platform to deliver mobile sites or should you write a separate site for each device (ok, so that last one is extreme, but I’ve seen it done) – there are a huge variety of different options, all with their pros and cons.

All of the different approaches are essentially a compromise, they can all deliver a workable solution but there is always a compromise on some aspects of the delivery. You need to choose which compromise to take and pick your route accordingly. One problem we have seen in RFP situations is that you can’t compare quotes on a like for like basis. They are all taking a different approach – some approaches cost more upfront but deliver cost benefits in the long term whilst some look initially attractive and it’s only when you are a year down the road that it becomes prohibitively expensive. Essentially, you need to be a mobile expert to decipher the RFP responses for the mobile experts you are trying to hire.

There is a solution that covers all the different techniques in one place – we’ll come on to that later. First I’d like to go through each of the main techniques and list the pros and cons.

Responsive (or adaptive) Design

This technique is getting a lot of mention recently and is viewed by some as the holy grail and answer to all their problems. Sorry to disappoint, but I’m afraid it’s a compromise. Responsive seems to make perfect sense and the idea that you can have your site respond to different devices (primarily based on screen width) and only need to develop one site sounds like a better than sliced bread moment. It’s when you stand back and think about the context of mobile where you find the compromise. Yes, it’s great writing one site and delivering to all screen widths, but is that really understanding mobile context? A mobile user with a touch interface has different needs to a PC/desktop user with a keyboard and a mouse. The navigation of the site should be different for these contexts. I’ve seen examples of responsive sites (this example is an insurance comparison site) where, on the desktop, the calls to action are clearly displayed on the homepage – this site owner really wants people to click on home, car or health insurance. When viewed on a smaller screen, the responsive elements kick in and very nicely changes the layout of the page for a smaller screen. In this case, however, it means that all the calls to action scroll off the page and aren’t easily visible. You are trying to fit a layout designed for a large screen into a small screen without accounting for the context. A better solution would be to make all the call to action buttons different so they appear on the front page for mobiles. This could be done with responsive, but it’s now getting more complicated to manage the site to cater for many different devices.

Another big issue is page size. Typically the responsive site delivers everything to the mobile and then the device ignores half of it. A great example of this is the Channel 4 news site which delivers an astonishing 2.5MB of information to the device, most of which is not used. Given that a long page load time deters users, my average download time of over a minute for this page is not encouraging.

Responsive design seems attractive initially. There are no license costs for software or middleware platforms and everything is done using standard web languages. Managing and enhancing a responsive site becomes increasingly expensive and risky as more and more diverse devices need to be supported and the stylesheets get more complicated. Your very talented web developer who knows how it all hangs together may leave, giving you a real headache managing the site.

Having said all this, responsive design is perfect for certain sites – news (aside from the aforementioned Channel 4) and content sites are particularly suited to this technique, but transactional site not necessarily so. The technique can simplify site creation with all the business logic in one place and you don’t have to manage 2 sites. You also get a single URL with no need to redirect to a mobile specific site and all the SEO benefits that has.

A mobile specific site

If you understand that mobile requires a different context to desktop, you typically end up here with a mobile specific site which gives you all the flexibility you need to cater for your mobile based users. Here you can design specific, optimised pages and manage the user journey. Your analytics will relate specifically to mobile users and you can adjust the journey accordingly to get the best from your site. Your PC site will automatically redirect to the mobile site and it will be available on an m. URL so searchability and access to the site will not hinder your users and they will get the best experience for the device they are using (with, of course, the option to view the PC site on a mobile if they want to).

All the above gives maximum flexibility, but it’s still a compromise. You have to manage 2 sites and they aren’t served from the same URL (the redirect works, but from an SEO point of view it could be viewed as a separate site). Although the separate site should not duplicate content, some of the business logic may need to be different and there is inevitably some duplication. Managing a separate mobile site without the benefit of a platform (see below) can become expensive.

Creating a different mobile site for different groups of devices

This is a handy one as it can make your life easier. If someone is suggesting this approach you can discard their response immediately.

Using a platform

There are a number of device independent platforms that deliver all the benefits of having a separate mobile site along with the added benefits of making it easy to manage the multitude of devices and ensure that the site is future proofed against new device developments. A platform will deliver cost savings on maintenance and site enhancements going forward and you will not be in the sticky situation of rushing to make the site work on a new device – the platform should manage that for you.

It’s true that there may be more upfront cost for a platform as you might have to pay for licenses to use it. But think of the platform as less than the cost of a developer for a year – it will keep the site in a manageable format that anyone can edit and it’s not suddenly going to leave. Well worth the money in my opinion.

In summary

To summarise the above, there are many different options available for delivering your mobile site and they all have compromises. In an ideal world you would like to:

  • Deliver the site from one URL without redirection
  • Respond to different devices from one code base
  • Have the flexibility to deliver mobile optimised content that may be different to the PC content.
  • Reduce code duplication and back end business logic integration effort.
  • Group devices based on a better granularity than just screen size.
  • Not just rely on complex style-sheets to deliver a different layout
  • Ensure you are delivering only the content the device needs and not extra content that will get ignored.
  • Not relying on talented, expensive developers to deliver complex responsive based solutions.

All the solutions discussed above deliver some of this wish list, but none can deliver all.

Problem Solved

There is one solution which can deliver all of the above. The bemoko development platform can deliver sites to any device, including PC and desktop and allows for comprehensive device grouping so that markup can be targeted to specific devices. Full support for HTML5 and CSS3 means that responsive design can be used where it is beneficial. Markup is automatically optimised for each device meaning the end of the 2.5MB page size.

Because the platform manages all the devices, there is one code base and one URL – there is no redirection required. The user experience for mobile/tablet/phone/TV and anything in the future can be changed to deliver the perfect experience for the device being used and not a compromised PC layout delivered to a small screen. The layout can be changed using a mixture of style-sheets and HTML code which simplifies site build and maintenance. The backend code integration can be done once for both desktop and mobile.

If you really want to deliver the best user experience for your users whilst reducing development costs on support and maintenance, the bemoko platform can help you achieve your goals and increase customer engagement by providing the best user experience for, however they interact with your site.

By Mat Diss – Managing Director of bemoko

Share and Enjoy:
  • Digg
  • Sphinn
  • Facebook
  • Mixx
  • Google Bookmarks

Posted in: mobile, mobile design, mobile search, mobile technology, mobile UX, mobile web, multichannel, public website news, responsive design, web optimisation



Responsive is not the only route to mobile, dispelling the Myth!!

Posted By Emily Nicholls Tuesday, November 13, 2012. No Comments

Ok…enough already!  If I hear the words responsive or adaptive one more time this week, I’m off to silicon roundabout with a 20ft poster and a loud hailer!

Simple fact is I don’t get it!  I really don’t get it!  The tech and agency world, not to mention the internal tech teams and digital teams in all those corporates out there are (I hope) pretty bright individuals, but for some unknown reason when it comes to mobile they seem to have lost all sense!

Ok so mobile is new, I’ll give them that, and I guess to a degree there is a learning curve to go through, but with so much innovation and expertise out there you’d have thought that at least some individuals would have realised that using techniques designed for desktop web development just can’t cut it in mobile.

Is it laziness?  Or perhaps corporate politics or is it just fashionable  and trendy to be jumping on the responsive bandwagon (aagghhh I said it! Now, where is that loud hailer!)  Maybe it is just pure and simple lack of understanding and perhaps like unruly teenagers we just have to let them make their own mistakes until they feel enough pain to come to their senses.

So who’s feeling brave?  Who’s a real innovator?  Who can break the mould and drive change?  Who can challenge convention?(probably words that appear in any one of the agency’s or corporates mission statements)
Firstly let’s bust the jargon – Responsive (aagghhh… OK just knocking up the poster) is a technical term for writing a website that delivers the same content to all devices but changes the layout according to the size of the screen, nothing more special than that, it’s certainly not an innovation for mobile web build, and here is where the problem starts.

Firstly getting a page to display on a small screen is not mobile, it’s just a miniature website, secondly using simply style-sheets to tell any one of an almost infinite number of different device combinations what to show or hide, results in a spaghetti mess that becomes impossible to fix, update and is costly to maintain.  Thirdly it means you are taking a short cut and ignoring your mobile audience and the context they are using your site in – should they have the same navigation as your PC site?  Finally it means rewriting your whole website, managing endless templates, images and content too.

The alternative is not however an – this too is not the future, generally because the stand-alone site will be built using old techniques, but just using small style sheets for small screens.

Here’s the rub… you want to deliver your site from one code -base and from one URL, but you need to understand the different user contexts for different devices and that mobile is very different, multi device is different again.   The only way to truly tackle it is to use technology and methodology founded in the mobile operators, honed and refined on leading edge multi-device projects and packaged for use by anyone open-minded enough to see that web design and build has moved on light-years from the old days PC only websites.

Enter the world of web platforms – there are many to choose from, they are designed specifically to tackle the challenges of a multi-device world, they will save time and money and they will deliver astonishing results.  Finding one is the easy bit, breaking the blinkered and entrenched mindset that seems to be gripping the developer community will be the challenge!

3wise Responsive is not the only route to mobile, dispelling the Myth!!

By Phillip Clement

Share and Enjoy:
  • Digg
  • Sphinn
  • Facebook
  • Mixx
  • Google Bookmarks

Posted in: mobile, mobile design, mobile search, mobile technology, mobile UX, mobile web, multichannel, responsive design, web optimisation



4 Easy Steps To Mobile Web Payments

Posted By Ian Homer Tuesday, September 18, 2012. No Comments

Mobile has always thrived for applications where immediacy is paramount and retailers should not fall short of allowing the customer to complete their transaction whenever and wherever the customer may be. Waiting until the user is back at their PC may push your customer to connect with one of your competitors. Taking payments is not difficult, so let’s take a look at how you can take payment on your mobile web site and complete the customer’s journey.

Payment options at your disposal include:

  • Online wallets
  • Credit card – similar to what you might expect on a PC site
  • Direct operator billing – payment taken of the customers bill
  • Premium SMS (a.k.a PSMS) – SMS sent to customer that gets

Various on-line payment service providers, such as Bango, CellPoint Mobile, Braintree and PayPal provide hosted solutions that allow you to get up and running quickly for these different payment options. Note that service providers may not give you all of the 4 payment options above.

These hosted solutions work by taking the user to a payment page provided by the payment service provider so that payment can be taken. A typical flow for this is :-

  1. The user makes the product choices on your web site filling up their basket
  2. When the user is ready to purchase the products the user is directed the payment service provider page. This is typically by an HTML form that takes the user off your site, although you should be able to customise this page so that it looks like your brand.  If you decide to take payment details on your site rather than redirecting, be sure you understand the PCI compliance rules that govern storing credit card data.
  3. When the payment has been confirmed a back-end callback can be made to your web site to confirm the purchase is OK and the user is taken to a thanks page on your side. The callback is necessary to reduce chances of unscrupulous users fooling your site into thinking that the payment has been received.
  4. Your site delivers a thank you page AND sends out email or SMS confirmation to the user that the order is on its way.
  5. Note that the callback may occur in a couple of stages 1) payment has been authorised – i.e. funds reserved and 2) payment captured – i.e. funds transferred to your account. So do be ready to handle either of these signals – if you’re dealing time sensitive products, e.g. take away delivery, then you’ll want to put the order in motion as soon as the payment as been authorised. Otherwise you may want to hold off on putting the order in motion until you’ve had confirmation that the payment has been captured.

Note that Braintree has a nice variation on this where you can handle this payment integration with a javascript client library.

Do compare the commission that each of the service providers takes on each payment as this can vary significantly from one provider to another and from one payment option to another (e.g. credit card vs PSMS).

When it comes to 3D secure, the user experience has not yet been optimised for mobile, although it does work. If you choose to disable it then you may improve the user experience, but you will be taking the risk that payment is fraudulent since 3D secure does give you extra security for your payment.

As always – monitor your site. When you start taking payments, ensure that you monitor how much your site takes every hour and send out alerts if orders drop off during an hour.  This can be an early warning signal that something is misfiring.  If you are using a platform to deliver your site, such as bemokoLive, then these alerts and the monitoring come built in, making it much easier to ensure that every order gets fulfilled.

If you want to talk to us about how to start taking payments on your mobile web site and take use of some of our existing payment integrations modules then please get in touch, feel free to share or comment on this blog

Share and Enjoy:
  • Digg
  • Sphinn
  • Facebook
  • Mixx
  • Google Bookmarks

Posted in: business, iphone, java, mcommerce, mobile, mobile design, mobile search, mobile technology, mobile UX, mobile web, multichannel, public website news, responsive design, smartphone, social, tablet, transactional, web optimisation



Is developing for a small screen, developing for mobile?

Posted By Emily Nicholls Thursday, September 13, 2012. No Comments

Responsive design certainly has it’s appeal, based upon if what you read is true that is ie: people spending more time on your site, content display etc… It initially looks like it is the panacea to solving the growing problem of delivering content to different devices.

What responsive design misses is that mobile users have different needs and context from someone using a 21″ desktop computer. Trying to squeeze a desktop site into a mobile sized site is not necessarily the most optimal experience –the Channel 4 site as an example is over 2MB in size. Not only does this take a long time to download on a phone (over 2 minutes on a test I did), the phone then throws away half the content as isn’t displayed. To top it all, the site didn’t display properly on my Samsung S3 after I’d waited all that time. Setting something to display:none doesn’t mean it doesn’t get downloaded.

Adapting content based solely on screen size versus users needs overlooks usability issues and differences between touch and click based interfaces.

Responsive design definitely has its place, but if assuming the only difference between desktop and mobile is screen size is not a strong basis for building a lasting and long term mobile strategy that will enable your brand to thrive.

There are common misconceptions around responsive design that will ultimately undermine the capabilities and the power of mobile devices, so we appeal to you to think carefully about the savings you may gain at the start and think about 6-12months from now when changes, development and where you want to see your business and brands positioned.

If you recognise and harness the strengths of mobile and it’s platform and ensure that you design the User Experience, Navigation and develop for your customers/users then you will quite simply create something that’s not just good but outstanding.

Please feel free to share and follow us to read more about this and  other topics around mobile web

Share and Enjoy:
  • Digg
  • Sphinn
  • Facebook
  • Mixx
  • Google Bookmarks

Posted in: business, mobile, mobile design, mobile search, mobile technology, mobile UX, mobile web, multichannel, PC website, public website news, responsive design, tablet