As a product grows, new features are always being added. The interface tends to get messier. As a result, users need to apply more effort to use the interface.

Complexity harms everyone.

For developers, it leads to incidents and bugs. The service delivery system becomes less reliable.

For users, it becomes time-consuming to learn and work with. The creative process slows down.

So: keep things simple. Though simplicity is one of the most important principles behind good design, it’s still one of the most neglected.

Don’t hesitate to trade off other values for simplicity. No matter how complex the overall system is, there is no excuse for complicating simple tasks.

Features are very easy to add, but almost impossible to remove.

6.1

6.2

6.21

6.22

6.3

6.31

6.32

Simplicity doesn’t happen by itself. Simplicity has to be designed.

Simplicity comes from a thorough understanding. The point here is to know the ins and outs of the process. If you do not, the result of your efforts will be ‘simplistic’ rather than simple.

While designing a feature, constantly ask yourself: which elements convey information, which elements serve as decorations, and what will happen if you remove the element.

Get rid of anything that is not essential.

Add multiple functions to a single element.

6.4

6.41

6.42

6.5

6.6

In Readymag you can't nest groups inside other groups. Untill it becomes an absolute nesessity for users' needs, we'll keep this feature as simple as it is.

Look for universal solutions to solve general problems.

6.7

6.8

Remember: even if a way of doing things has remained unchanged for a long time, it doesn’t mean it’s still the best way. It may also mean that no one has tried to find a simpler way.