USER INTERFACE DESIGN PHILOSOPHY
Clarity is the first and most important job of any interface. To be effective using an interface you’ve designed, people must be able to recognize what it is, care about why they would use it, understand what the interface is helping them interact with, predict what will happen when they use it, and then successfully interact with it.
While there is room for mystery and delayed gratification in interfaces, there is no room for confusion. Clarity inspires confidence and leads to further use. One hundred clear screens is preferable to a single cluttered one.
“There’s way too much talk about CSS and XHTML and Standards and Accessibility and not enough talk about people. CSS and Standards Compliant Code are just tools. You have to know what to build with these tools. Great, I’m glad your UI doesn’t use tables. So what? Who cares if it still doesn’t, let people achieve their goals. Web standards are great, but people’s own standards include getting things done (and that’s still too hard to do online).”
UI designers are making the same old fundamental mistakes, and forgetting about the human being on the other side just so their code looks better. Humans, not code validators, use interfaces.”
When working with layers of code for weeks on end, it’s hard sometimes to step back and remember that our sites are being used by humans, no robots. This isn’t implying that we shouldn’t worry about standards altogether. Standards are great and should be adhered to. We just can’t assume that standards compliance is all that’s needed to create a good UI.
UI DEVELOPER
Building user interfaces that support the exchange of information between an application’s users and its back-end processes and databases. This could be either a fully dedicated role on a development team or a hat a developer who is also responsible for coding the back-end processes might wear.
A UI Developer’s output is functional, testable, shippable code that lets users accomplish their goals when using an application. The UI Developer is also responsible for documentation that allows others to maintain their code.
USER EXPERIENCE DESIGN
I am certain to provide a wide range of the quickest, most practical, compatible, consistent, and search engine friendly website development performance as possible. Development techniques include (X)HTML, CSS, JavaScript, AJAX, PHP, MySQL. I can handle virtually anything related to static website elements including the appearance of a website, dynamically generated server-side websites, client-side dynamic websites, interactive “Web 2.0″ style functionality. The way a website is programmed or “coded” is vital to a web site”s recognition, function and operation.
Technologies and programming used to develop a website in the end determine how visible the website is on search engines, how the website will appear and function each range of computer, how fast the website will function, how much time and money the website will take to update, and how well it will operates overall.
UX DESIGNER
One who designs the user experience for applications after doing user and workflow analysis, producing user-centered design artifacts such as persona, site maps, taxonomies, prototypes and wireframes. A UX Designer may also conduct usability testing on prototypes or finished products to assess the quality of a user experience.
One of the main tenets of User Experience Design is simply incorporating user feedback in to the design evolution process. That is, co-evolving the system with its user’s. If the design process is not managed for timely collection, experienced interpretation, and judicious application of user input in to the system’s design revision cycles, then it is not a User Experience Design process. In my view this is the most difficult aspect of User Experience Design.
It cannot be achieved without consistent management support. And it is why UX Management, and management by any name, is tightly coupled with UX Design.
UX IN ORGANIZATIONS
Evangelizing subjective individual experience and co-evolutionary (life) processes in organizations that are still anchored in industrial age models of hierarchy and achievement is no small feat. Commercial enterprises are organized for self-reinforcement. But a shift is occurring.
Some organizations, especially those who produce web-based software primarily, accept the idea of equal, or nearly equal, provider-user and external-internal interchange and symbiosis. Networks are nothing if not reciprocal. Businesses that recognize themselves as a network node often have a flatter organizational structure, and are more informal in style in order to support collaboration. What’s more, the ‘network-ification’ of work may relate to a growing awareness of the merits of qualitative metrics of success. Regardless, only by utilizing such metrics can we ensure a desirable user experience, as well as a functional and efficient one. Or, as one respected supervisor once put it, “the better part of design is empathy.” -uxdesign.com