imp / collective / tags / ui

Tagged with “ui” (4) activity chart

  1. Kathy Sierra talks about creating passionate users and helping our users to kick ass and not suck!

    While at #FOWA08, Adam and Josh spoke with Kathy Sierra (@KathySierra) about creating passionate users, building web apps, allowing your user to “kick ass”, community building and more.

    This podcast is awesome regardless of its age. The conversation, in my opinion, was a very intimate take on what Kathy does to allow her users to “kick ass”. Kathy is by far an authoritative figure when it comes to community building, and learning how to treat and think about our users. Regardless of your role in the creative process, you need to be in touch with the importance of this relationship and the part you play.

    —Huffduffed by briansuda one year ago

  2. How Progress Bars Change the Way We Live

    Once upon a time slow connections begat the Progress Bar - bloated sites would taunt us with ‘15% loaded’ screens. High-speed promised to kill the beast and free us from their tyranny but yet it lives! Progress bars are being used MORE lately to direct user actions. Look to Farmville and LinkedIn which push their users to collect 100% of their personal information. Incomplete progress bars are an itch that needs to be scratched. They carry the implicit language that declares ‘You are here’ but more importantly ‘The end is in sight’. Game design motivates us through incremental, measurable progress towards a tangible goal but is this the way real life works? Is the progress bar’s ubiquity in technology starting to affect the way we measure progress in meatspace? This panel will reach far across time and space to look at the story of progress bars, why they hypnotize us and what we need to do - slay the beast once and for all, or throw ourselves into its partially-complete embrace…

    —Huffduffed by briansuda 2 years ago

  3. Don Norman on living with complexity

    Don Norman, a former Apple vice-president, co-founder of the Nielsen Norman Group, and one of the world’s most influential designers, discusses his new book, Living With Complexity. Norman talks about differences between complexity, something being complicated, and simplicity, and suggests that people who bemoan “technology” don’t actually seek simplicity. He also discusses differences between designing a product and designing a system, using examples of iPods and iTunes, the Amazon Kindle, and BMW’s Mini Cooper — products whose success depended upon the success of larger systems. Norman also notes the difference between a forcing function and a nudge, explains how complicated rules can weaken security, and comments on sociable design in realspace and on the internet.

    http://surprisinglyfree.com/2011/01/18/don-norman/

    —Huffduffed by briansuda 2 years ago

  4. Christian Crumlish: Designing Social Interfaces: 5 Principles, 5 Practices, 5 Anti-Patterns

    As we use social tools on the web, design patterns are emerging. Social design must be organic, not static, emotional, not data-driven. A social experience builds on relationships, not transactions.

    In 2008, Yahoo!’s Christian Crumlish introduced the idea of social design patterns to BayCHI. He returns in 2010 to share what he learned over two years. With his Yahoo! colleague Erin Malone, Christian created a wiki to gather social design patterns and published a snapshot of the wiki in book form.

    Among the many principles of social design, Christian presents five:

    • Pave the Cowpaths: Watch what people do, then support and adapt to that behavior.
    • Talk Like a Person: Use a conversational voice. Be self-deprecating when an error occurs. Ask questions.
    • Be Open: Embrace open standards. Support two-way exchange of data with other applications.
    • Learn from Games: Give your application fun elements, like collecting and customization.
    • Respect the Ethical Dimension: Understand the expectations people have in social situations and abide by them.

    Christian then describes five practices:

    • Give people a way to be identified and to characterize themselves.
    • Create social objects that give people context for interaction.
    • Give people something to do, and understand the continuum of participation, from lurkers to creators to leaders.
    • Enable a bridge to real life.
    • Let the community elevate people and the content they value.

    Finally, he discusses five anti-patterns, commonly-used design choices that appear to solve a problem but that can backfire and pollute of the commons. Examples:

    • The Cargo Cult: Copying successful designs without understanding why they are successful.
    • Breaking Email: Sending an email alert, but rejecting or silently discarding the reply.
    • The Password Anti-Pattern: Asking people for their password to another service encourages poor on-line hygiene.
    • The Ex-Boyfriend Bug: Connecting people who share a social circle but who have reasons to avoid each other.
    • The Potemkin Village: Building groups with no members. Instead, let people gather naturally.

    Christian stresses that social design is an ecosystem in which designers must balance many trade-offs. Not every design pattern applies to every application, but good designers can use patterns to strike a balance that works.

    http://chi.conversationsnetwork.org/shows/detail4459.html

    —Huffduffed by briansuda 2 years ago