As an avid user of the iPod Touch, I’ve had a lot of hands-on experience with mobile browsing. Many of the larger, frequently used sites like Amazon, Google, and even Facebook have created new versions of their sites to fit mobile phones and browsers. And somehow, these websites recognize you are using a mobile device and automatically direct you to the mobile version of the website. While this is great for users to be able to view the entire site without having to scroll using a small screen, I have found it so far to be ineffective. Many of these sites lack the full functionality of the original and are unable to maintain the same quality, and too often I find myself having to find a way out of the mobile site and to the original. And if, for instance, you are using Amazon to look up some items, switching to the original site makes you have to repeat your searches. From a user experience stand-point, I wish these places would just direct me to the original site and allow me to change to the mobile site – not the other way around. While the interface may require some scroll work or zooming, at least I can be sure I’m able to do everything I need to do and not have to repeat myself.
DDA has made a point to look at these very issues in our own website development and programming. Through extensive testing and debugging, we often provide input on what we think works and what we think doesn’t. For instance, if we developed Amazon’s mobile page, I would bring up how the search results don’t give the same information a normal search does so that our developers could make necessary changes. Alternatively, there may be design issues, functionality issues, or backend issues that we need to address before launch. It is our goal to provide an easy-to-use and engaging user experience so that from day one of launch, the user is able to gain everything they need without having to suffer through lack of support or confusing navigation.