-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Ux Design Philosophy
Be.ing edited this page Oct 19, 2017
·
17 revisions
- The answer is not more options. If you feel compelled to add a preference that's exposed to the user, it's very possible you've made a wrong turn somewhere. (Copied from Signal.)
- Live performance is the focus. Features that are meant to be used while mixing must be easily accessible with a minimum of steps required to use them. Features whose use is not time sensitive do not need to be as easily accessible. Discoverability matters, but being intuitive and easy to use while performing is more important.
- Screen space is precious. Mixxx has a lot of features and it is difficult to fit them all on a laptop screen. Use screen space wisely, considering the above mentioned focus on live performance.
- Minimize mutable state. The more moving parts a user has to keep track of, the more likely it is they will do something accidentally.
- "Works for me" is not good enough. It must work for everyone. People use Mixxx with a wide variety of hardware for a wide variety of purposes. Your changes should not interfere with how other people use Mixxx. Minimize assumptions about how people use Mixxx.
- There are no power users. Everyone should be able to use and understand all features of Mixxx. If they cannot, the design and/or documentation are inadequate.
Mixxx is a free and open-source DJ software.
Manual
Hardware Compatibility
Reporting Bugs
Getting Involved
Contribution Guidelines
Coding Guidelines
Using Git
Developer Guide
Creating Skins
Contributing Mappings
Mixxx Controls
MIDI Scripting
Components JS
HID Scripting