<?xml version="1.0" encoding="UTF-8"?>
<page>
  <content># Your business requires paying customers to function.
# Your paying customers are your users.
# Your users interact with your product through its interface.
# If your interface is bad, your customers will leave.
# You will go out of business without customers.

So why do the user interfaces for web applications sometimes feel like an afterthought much of the time? (This is especially true for corporate intranet apps.) Even if your project can do amazing things it is worthless if you don't expose the functionality in an intuitive manner through the interface. 

As I was writing this post Kathy Sierra actually "wrote something":http://headrush.typepad.com/creating_passionate_users/2006/10/oops_we_forgot_.html that directly relates to my point here. You are in business because of your customers, so don't forget about them. 

Want a great example of a web app where the UI doesn't feel tacked on? How about "Moo":http://www.moo.com/? Moo allows me to completely customize my flickr pictures that I want to go on their mini business cards, yet doing so is easy and intuitive. Heck, even with some of the handcuffs that come with being a web app it still manages to beat the pants off some desktop image editing apps.

Always make sure your UI is a central part of your development process. If it doesn't evolve with the application then you are just setting yourself up for some painful maintenance work later.</content>
  <created-on type="datetime">2006-10-04T14:21:35+00:00</created-on>
  <has-changes type="integer">0</has-changes>
  <html>&lt;ol&gt;
	&lt;li&gt;Your business requires paying customers to function.&lt;/li&gt;
		&lt;li&gt;Your paying customers are your users.&lt;/li&gt;
		&lt;li&gt;Your users interact with your product through its interface.&lt;/li&gt;
		&lt;li&gt;If your interface is bad, your customers will leave.&lt;/li&gt;
		&lt;li&gt;You will go out of business without customers.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;p&gt;So why do the user interfaces for web applications sometimes feel like an afterthought much of the time? (This is especially true for corporate intranet apps.) Even if your project can do amazing things it is worthless if you don&amp;#8217;t expose the functionality in an intuitive manner through the interface.&lt;/p&gt;


	&lt;p&gt;As I was writing this post Kathy Sierra actually &lt;a href="http://headrush.typepad.com/creating_passionate_users/2006/10/oops_we_forgot_.html"&gt;wrote something&lt;/a&gt; that directly relates to my point here. You are in business because of your customers, so don&amp;#8217;t forget about them.&lt;/p&gt;


	&lt;p&gt;Want a great example of a web app where the UI doesn&amp;#8217;t feel tacked on? How about &lt;a href="http://www.moo.com/"&gt;Moo&lt;/a&gt;? Moo allows me to completely customize my flickr pictures that I want to go on their mini business cards, yet doing so is easy and intuitive. Heck, even with some of the handcuffs that come with being a web app it still manages to beat the pants off some desktop image editing apps.&lt;/p&gt;


	&lt;p&gt;Always make sure your UI is a central part of your development process. If it doesn&amp;#8217;t evolve with the application then you are just setting yourself up for some painful maintenance work later.&lt;/p&gt;</html>
  <id type="integer">81</id>
  <is-post type="integer">1</is-post>
  <is-published type="integer">1</is-published>
  <title>"We'll Just Do The UI Later."</title>
  <url>notebook/2006/10/04/just_do_the_ui_later</url>
</page>
