Practical Generalities

It’s always smart to ‘borrow’ other software’s methods to solve common and uncommon UI/UX problems, but you should always avoid “practical generalities” design. This line of thinking can be very dangerous.

Just because some other software solves a problem one way doesn’t mean you should use that same method in your software. It was probably part of a larger system of features and methods that you’re not including in your overall design and you’ll cause your user to learn a sub-program inside your program.

Instead, figure out how the other software is solving the problem and offer that method in your software in a way that is using your terminologies, your metaphors, your affordances, your UI theme, etc.