Interface Design Nets Policy: Don't Make This Mistake! - OpenSIPS Trunking Solutions

A common mistake when designing interfaces is to make an interface that implements everything that a class does. Read also: Craigslist Lincoln Listing: The Clues You've Been Missing

Sometimes this is correct, especially when classes are designed in a concise way (and in accordance to the single responsibility principle).

The 8 golden rules of interface design are:

Strive for consistency, enable shortcuts, offer informative feedback, design dialogs for closure, prevent errors, enable easy action reversal, support user control, and reduce memory load. Read also: FakeHub The Wish Makers: Your Questions Answered (Finally!)

Design dialogs to yield closure ensure clear task completion. Read also: 10 Chilling Facts About Ed Gein's Photos You Won't Believe!

Offer simple error handling make errors easy to understand and fix.

Permit easy reversal of actions allow users to undo mistakes.

Support internal locus of control give users control over their experience.

Website accessibility ensures that people with disabilities or limitations can easily navigate and access the content on your site.

See framework design guidelines for designing libraries that extend and interact with. net, to ensure api consistency and ease of use.

Do define an interface if you need some common api to be supported by a set of types that includes value types.

\n consider defining an interface if you need to support its functionality on types that already inherit from some other type.

Do define an interface if you need some common api to be supported by a set of types that includes value types.

Consider defining an interface if you need to support its functionality on types that already inherit from some other type.

Avoid using marker interfaces (interfaces with no members).