Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
User interface design isn't just about making things look pretty—it's the bridge between your digital artwork and the people experiencing it. In Digital Media Art, you're being tested on how design principles shape user behavior, accessibility, and emotional response. The best digital art means nothing if users can't navigate it, understand it, or feel empowered while interacting with it. These concepts show up constantly in questions about interactive media, web design, app development, and user experience evaluation.
Don't just memorize these ten principles as a checklist. Instead, understand how they work together: some principles help users learn an interface, others help them navigate it, and still others ensure they feel confident while using it. When you see an exam question about why a design succeeds or fails, you need to identify which underlying principle is at play—and often, multiple principles interact to create the total experience.
These concepts reduce the cognitive load required to understand how an interface works, letting users build accurate mental models quickly.
Compare: Consistency vs. Affordance—both reduce the learning curve, but consistency works through repetition within the interface while affordance works through real-world associations. If an FRQ asks why users struggle with a novel interface, check for missing affordances first.
These concepts help users understand where they are, what's important, and where to go next.
Compare: Visibility vs. Hierarchy—visibility ensures elements can be found, while hierarchy determines what gets found first. A cluttered interface might have high visibility (everything's there) but poor hierarchy (nothing stands out). Strong designs balance both.
These concepts make users feel in control and reduce anxiety about making mistakes.
Compare: Feedback vs. Error Prevention—feedback responds to all actions (successful or not), while error prevention specifically targets potential mistakes. Both reduce frustration, but feedback is continuous while error prevention activates at critical decision points.
These concepts make interfaces efficient, clean, and adaptable to diverse users and contexts.
Compare: Simplicity vs. Flexibility—these can create tension. Simplicity wants fewer options; flexibility wants more. Great design resolves this through progressive disclosure—simple by default, powerful when needed. Expect exam questions about balancing these priorities.
This concept ensures your design works for all users, regardless of ability or circumstance.
Compare: Accessibility vs. Flexibility—both expand who can use an interface, but accessibility addresses ability differences while flexibility addresses preference differences. An accessible design might still be inflexible (one way to do things, but everyone can do it), and vice versa.
| Concept | Best Examples |
|---|---|
| Learning & Mental Models | Consistency, Affordance |
| Navigation & Information Architecture | Visibility, Hierarchy |
| User Confidence & Trust | Feedback, User Control, Error Prevention |
| Efficiency & Clarity | Simplicity, Flexibility |
| Inclusive Design | Accessibility |
| Reducing Cognitive Load | Simplicity, Consistency, Hierarchy |
| Supporting Novice Users | Affordance, Visibility, Error Prevention |
| Supporting Expert Users | Flexibility, User Control |
Which two principles both reduce the learning curve for new users, but through different mechanisms—one through repetition and one through real-world metaphors?
A user completes an action but isn't sure if it worked, so they click the button three more times. Which principle is the interface failing to implement?
Compare and contrast Simplicity and Flexibility. How might a designer resolve the tension between offering fewer options and accommodating diverse user needs?
An interactive art installation will be experienced by visitors of all ages and abilities for only 2-3 minutes each. Which three principles should the designer prioritize most, and why?
If an FRQ presents a cluttered interface where users can find all features but struggle to identify what's most important, which principle is being violated—Visibility or Hierarchy? Explain your reasoning.