So I found this article on AIGA and
the basis for this article is to stop making UX (User Experience) so simple. I
found this article to be really useful as it really pertains to my skill
set. It also subcategorized different
aspects of UX design, stating that making something simple isn’t so simple in
fact. It states that every designer that has used an iPhone tries to base their
design off of their layout, as it is the best example of simplicity, but in
reality it is not as simple as it looks. The reality of it is, there is a
constant learning curve and is incredibly complicated. It states that every app
that apple comes out with introduces a new way of doing things, but in reality
the difference is very minimal and comes in an endless supply.
In this instance,
good design can be applied to make the complex appear simple, creating clarity
in the design. In reality, the iPhone handles a lot of different programs and
services. iPhone’s are anything but simple, but neither is a 30-page survey on
a dating website. The design may be beautifully designed, sophisticated, and
considered, but one thing they are not is simple.
As the
article states, not everything can be simple or easy to use. A lot of apps out
there are extremely complex, but it is necessary to limit the type of user who
uses the app or service. But even though they are complex doesn’t mean that
they can’t be clear, delivering the desired message to the user.
The writer
of this post states that the most common question he receives is how to apply
lessons in core web application design principles; his response is “You apply
them to each and every interaction exactly as you would in a narrow-scope
application. The principles all still apply. The system you’re working on may
be more complex, but the principles can still then be applied on a micro scale
to each screen within it”. This could not be more true, just because it appears
to be complex and difficult to navigate, does not mean it can’t be simple and
beautifully designed.