In this one hour tutorial workshop, you will become skilled in CSS3 selectors, transforms, transitions and animations. We will work through an animation examples, creating different paths, timing and effects, exploring linear gradients opacity, alpha transparency, border-radius, text-shadows, transforms, transitions and mostly animations. The code example will be provided participants can play with the code, going from novice to skilled without heavy note taking.
There is a power for loading data that will be manipulated within the interface by user action. Templates also let you chunk your interface into manageable, re-usable pieces.
Beginning of a project, we understand it completely. Then we begin (and quickly realize that it is more complex than we initially thought, we add features, we hit constraints). We get to a “feature complete” state (top of bell curve): a product is maximally complex and feature complete but not really finished.
If you don’t design something, don’t be surprised if you have a crappy product.
A design system is anything that turns an idea into a form (a specific embodiment). Design systems can be channel-based (print design system, web design system, mobile design system, etc.)—different in the details but still sourced from the same idea.
Unfortunately, we tend to go from an original form to a new form without a new design system tied back to a core idea. Don’t imitate forms: translate ideas.
Let’s talk science! We’ve all been putting links on pages, but do we know how to design them well? After studying clickstreams, only 42% of users find the content they are looking for on average websites.
“Content strategy is just content planning or common sense.” Content strategy quickly begins to touch on organizational change. It’s easy to say we should be doing these things, but actually making them happen in an enterprise organization is a different story altogether. Content strategy integrates multiple disciplines, which means you should plan but also immediately start doing. “Everyone wants a seat at the strategy table.”
Matching academic thinking on behavior and motivation with practical web projects. Where in my product/service do I effect behavior change? Where am I persuading users to change their behavior or motivating the user to use my product in a particular way? How do I balance customer/user value with business value (both implicitly and explicitly) and how transparent am I being about my techniques and constraints?
“We should look at what kind of impact people’s behavior should have on our designs.”
We need a better design artifact than the comp / mockup (because iterating against a mockup is too much work). How can you develop buy-in for design decisions early and carry that support to the end of a project? How can you maintain client trust throughout the process and end up with few-to-no changes at the end (when you have implemented an interface)?
We have to design for multiple contexts (situation people are in while they are using a particular product/service): location, time, form and technology, relationship, and product ecosystems. Challenge for designers: solve problems for those contexts.
[ SXSW Bios ] #leanux @jboogie Brief Traditionally User Experience Design has been a deliverables practice. Wireframes, sitemaps, flow diagrams, content inventories, taxonomies and “The Spec” defined the practice of UX Designers (IxD, UX Design, whatever, etc). While this work has helped define what UX Designers do and the value our work brings to the […]