The Consumer Electronics Show (CES) yet again, shows us the future of consumer tech.
Google has yet again updated it Android and iOS apps, but this time it's Uber integration that's the big feature.
Responsive web design is the buzz word at the moment, but what does it actually mean? How do you decide if a website is responsive? Before we answer these questions, we need to step back and define the word 'responsive'.
Samsung has launched the Samsung Galaxy Gear, a smartwatch that not only connects to one of two Samsung devices, it carries a list of annoyances that fail to define the smartwatch as 'necessary'.
Oppo and people who brought you CyanogenMod, now called Cyanogen Inc., have partnered together to release an Android phone with very best of the Android romming community.
When we scope a website, we need to define what browsers we will optimise the website for versus those browsers that the website will operate satisfactorily. It really comes down to budgets.
User testing new website design, features, functions and processes is one of the best ways to understand whether you're on the right path or not. The only better way to understand what users think is to launch your work to the masses...
The biggest problem with this statement (apart from the excessive title case), is ‘may’ is a weak word. What does ‘may’ mean?
When we started designing mobile websites, 320px wide was definitely ingrained. It was all fun and games until Apple released the iPhone 4 and upped the resolution.
In April of 2010 (well into the widescreen era), a company in Cupertino, California called Apple Inc. decided to release their iPad with a screen resolution of 1024 by 768 pixels. Forever locking in the 960 pixel wide web site.
Due to the development of Google’s Chrome OS, it was unsure if Chrome (the browser) would make it to the Android platform. However, for whatever reason, it has. And it’s fast!
I’m starting my series of blogs by heading back to basics…
I’m putting myself on the path to find this better way and it’s going to be an adventure. Over the next couple of months, I’ll be looking into a range of user interface delivery methods that satisfy the client, our designers and our developers.
As one of the office’s many Android phone users (and maybe one of the more passionate ones), I consider myself an advocate of the benefits of open source software. While the iOS vs Android debate will never die between myself and some of the hardline Apple fans in the office, I’m always interested to see where the decision to go ‘open source’ takes other platforms.
As an interaction designer, a large proportion of my time at work is spent using Axure. Axure is a strong tool, helping us maintain consistency across our prototypes by utilising masters and dynamic panels. However, during the course of prototyping a web site, your Axure prototype can easily resemble a mash up of colours, panels and masters.
I titled this blog so blatantly because it sounds like an oxymoron. A huge alphanumeric jumble of characters and the notion of increasing the usability of a web site doesn’t sound right.
We recently had some discussion regarding where button belong at the bottom of forms. If you don’t have time to read this whole post, here’s the quick answer: There isn’t one.