...
Below is the original drafting work carried out and coordinated by the UX Interest Group in 2021.
The final USE Design Principles are located here, USE Design Principles
...
Samvera community packages run the gamut from Ruby gems, to generators, to Rails and Elixir applications, Node modules, JavaScript UI components and more. Thinking about a meaningful purpose the UX Interest Group could serve the community in 2021, the following questions have surfaced.
What does such a wide variety of Samvera code have in common, besides serving the digital repository needs of the Library/cultural heritage community?
What does it mean to be a “Samvera application”?
What if general criteria existed which Samverians (developers, product owners, managers, designers), could reference when designing and developing an app or module?
Mission
The UX Interest Group proposes crafting a set of Design Principles, which reflect the values and goals of the Samvera Community. In addition, perhaps these Design Principles could:
Serve as a guide for application design before development begins.
For example, when creating wire-frames for a new feature, does the wire-framed content meet Design Principles standards?
Act as a reference point for applications in active development.
Be a tool to evaluate existing Samvera applications, such as:
Identify areas which might fall short of meeting Samvera Design Principles, thus becoming opportunities for improvement.
Interpretting Interpreting these Principles from Different Audience Perspectives
...
Backend Developers (current & future)
Front End Developers (current & future)
Administrative Users
End Users / Patrons (students, faculty, research, general public, etc.)
...
Samvera Design Principles (working draft)
Samvera is a vibrant and welcoming community of information and technology professionals who share challenges, build expertise, and create sustainable, best-in-class solutions, making the world’s digital collections accessible now and into the future.
...
Design Principle
...
Sub-Theme
...
Qs for All
...
Additional Qs for Developers
What are the Principles?
Human-Centered. Efficient. Unified. Sustainable. Ethical.
Human-Centered
Inclusive & Equitable |
|---|
Q: Does the app feel welcoming?
Accessible & Universal | Engaging & Unambiguous | |
|---|---|---|
|
|
|
Human-Centered
Accessible & Universal
Q: Is the app “approachable”?
Q: Does the app feel cluttered?
Q: Is the app responsive across viewport sizes?
Q: Easy to find and manipulate any accessibility features?
Q: Does the app follow WCAG requirements? At what level?
Human-Centered
Engaging & Unambiguous
Q: How does the app actively engage/empower users?
Human-Centered
Unassuming
|
Q: Are used icons universally recognized for desired function?
|
|
|
Q: How does the app adapt to various devices?
Efficient
Modular while functioning as a whole
Q: Does the app take advantage of DRY principles and is logically separated?
Efficient
Minimal (in design & latency)
Q: Does the UI display more than is needed?
Efficient
Intuitive
|
Q: Does the app assume a certain level of technical proficiency to navigate?
|
|
Q: How easy is it for users to avoid and correct errors?
Efficient
Predictable, uncomplicated and precise
|
|
Q: How does the app use consistent color and icons?
Efficient
Managed Flexibility
Q: Does the application create endless flexibility to the detriment of the workflow?
Ie. Endless top folder creation instead of applying information architecture/minimum rules for information organization/categorization.
Ie. Endless choice typically doesn’t lead to efficiency
1. Human-Centered
...
Inclusive & Equitable
Q: Does the app feel welcoming?
Q: Does the app (unintentionally) leave any users out (culturally, language, eye-sight conditions, etc)?
Q: Is it obvious where to request help? Report a problem?
Accessible & Universal
...
Q: Is the app “approachable”?
...
Q: Does the app feel cluttered?
...
Q: Is the app responsive across viewport sizes?
...
Engaging & Unambiguous
...
For Developers:
|
...
Q: Easy to find and manipulate any accessibility features?
|
|
...
Unassuming
Q: How does the app use simple language (Ie. Explains all accronyms)?
Q: Are used icons universally recognized for desired function?
Q: Does the design translate well to multiple communities and account for cultural/institutional differences?
...
|
Efficient
Modular while functioning as a whole |
|---|
...
Minimal (in design & latency) | Intuitive & Predictable | Configurability Balanced with Efficiency | |
|---|---|---|---|
|
...
|
Minimal (in design & latency)
|
Intuitive
...
|
|
...
|
Predictable, uncomplicated and precise
...
|
...
|
...
|
Flexibility balanced with Friction
|
...
|
...
|
3. Unified
Follow standards, guidelines, conventions and best practices.
...
Unified
Standards & Best-Practices | Consistent behavior patterns & functionality | Clearly documented (for designers and users) |
|---|---|---|
|
...
|
...
|
Consistent behavior patterns and functionality
|
...
...
|
...
|
...
|
...
Sustainable
Prioritise Sustainability over Trends
...
Mindful of Trends | Maintenance Demands Match Resourcing Realities | Forward Thinking |
|---|---|---|
|
Maintenance demands should match organizational commitment to a resource.
|
...
...
|
...
|
...
Ethical
Transparent |
|---|
...
Mindful of Unintended Favouritism | Digital Safety & Wellbeing |
|---|---|
|
...
|
...
|
...
...
|
...
|
Safety
|
...
|
...
|
...
|
...
Ease of Adoption for all communities
Q:
Prioritise Design choices that favour all communities.
...
...
Contribution Acknowledgements for the Samvera Design Principles:
Source:
https://principles.design/examples/the-ten-principles-of-inclusive-design
University of Virginia Library Design Principles
…
...