by Faith
15. June 2011 20:26
| User Experience Concepts |
 |
Used to crystallize the key messaging, positioning, essence, and user experience that will be associated with the proposed brand concepts. |
| |
 |
|
Answers the following questions:
- What is the key message for the proposed concept?
- What does the proposed concept make the target audience feel about the client’s brand?
- How should we visually represent the client’s brand?
|
 |
Provides the following benefits:
- Provides a visual representation of the client's brand essence and experience
- Ensures that the different brand concept proposals are differentiated
|
 User Experience Brief (DOC) User Experience Brief (PDF)- Coca Cola Use Cases (DOC)
- Coca Cola Use Cases (PDF)
|
by Faith
10. June 2011 21:49
The Model View ViewModel (MVVM) is an architectural pattern used in software engineering that originated from Microsoft as a specialization of the Presentation Model design pattern introduced by Martin Fowler.[1] Largely based on the Model-view-controller pattern (MVC), MVVM is targeted at modern UI development platforms (Windows Presentation Foundation, or WPF, and Silverlight) in which there is a user experience (i.e., user interface) (UXi) developer who has requirements different from those of a more "traditional" developer (e.g. oriented toward business logic and back end development). The View-Model of MVVM is "basically a value converter on steroids"[2] meaning that the View-Model is responsible for exposing the data objects from the Model in such a way that those objects are easily managed and consumed. In this respect, the View-Model is more Model than View, and handles most if not all of the View's display logic (though the demarcation between what functions are handled by which layer is a subject of ongoing discussion[3] and exploration).
MVVM was designed to make use of specific functions in WPF to better facilitate the separation of View layer development from the rest of the pattern by removing virtually all "code-behind" from the View layer.[4] Instead of requiring Interactive Designers to write View code, they can use the native WPF markup language XAML and create bindings to the ViewModel, which is written and maintained by application developers. This separation of roles allows Interactive Designers to focus on UX needs rather than programming or business logic, allowing for the layers of an application to be developed in multiple work streams.
by Faith Warren
15. June 2010 20:23
by Faith Warren
15. June 2010 20:20
| Rogaine Website |
 |
The Rogaine website was a simple site in itself, but each product is driven by a different team whose marketing initiatives ran congruently to one another.
Once it was determined that a product was drven by whatever entrance site we kept a string that showed the user only the male or female color based on the entry designation. The tabs allowed users to surf over into the alternative route thus hijacking the color string based on the "sex" of product they were buying. It was quite an ingenious compromise for a client whose marketing drives were so diverse from one another.
This site has since changed it's overall look and feel, but this is what it looked like when I developed it in 2002.
|
|
|