Shawn Wildermuth

Author, Teacher, and Filmmaker
.NET Foundation Board Member


Tagged with User Interface

UX is Important

I talk to a lot of people about what people call “design”. There are developers who are great at design but many are worried about not having ‘design’ skills. But I don’t think design skills are nearly as important as usability skills. Shiny buttons, rounded corners, and lovely gradients are great, but if I am guessing on what the app is doing, we’re all doomed.

I use Skype. There I said it. I feel better.

Skype had an update today and the calling UI had changed. The bar that gives you control of the call changed to this:


Are You a Designer/UX Person?

clayhands_fullI am looking for a great designer/UX person. I am in the middle of a rather large project that I can’t talk about…but I need that great designer-minded person. I am more interested in your sense of usability and flair for great looking apps. The person should be familiar with web and mobile applications and have helped out with consistent look and feel through a full project.

Of note, I am not interested in super-polished, corporate design work – I am looking for something more special than that. Usability is important, but a great sense of style and theme are more important. HTML/CSS wireframes are not nearly as important.

Be clear, if you send me a link to your blog and you have 400 links to SEO improvement and 3 samples of your design work, I’ll just ignore you.


Why Declarative UIs Are Important


Sketching a UIIf you're building Internet applications, you've probably been bombarded with lots of new technologies the last few years: Silverlight, Flex, ASP.NET MVC, jQuery, etc. While all of these technologies have their use-cases, many of them are pointing to something that is new and important.

The central idea of separating concerns is not new. Back in SmallTalk when Model-View-Controller was born, the benefits of isolating layers of an application were pretty apparent. The problem was that it wasn't easy to implement. The problem with implementation was never the code...or was exactly the code. The problem is that when you are working on a problem in the user interface, it is far to easy to try and solve it directly in the code. Its not laziness or lack of talent.  Its simply a matter of focus sometimes. Under the timeline gun its easy to be myopic about a problem. Its simply too easy to just try and solve a problem by writing code in the user interface (or the View).