Posted by Liler on April 29, 2025
From Metaesn docs: Design principles
Practical
Solve practical problems quickly, efficiently and effectively
We primarily follow this principle to create and design our products and the various tools (such as data model and management method, user interface and interaction, data file formats, etc.).
Not only save and manage data and resources, but more importantly, let these resources provide feedback, truly produce effects (results) and benefits, and truly offer higher value and returns to users.
Our product is more consistent with the real world and actual situations, so that they can solve users' practical problems faster and better.
Safe
Ensure and protect the security and privacy of ourselves, our products and services, and user data
If we only think about solving problems without security, the result is likely to be harmful or disadvantageous to ourselves or our users, and ultimately it will not make much sense or be meaningless for ourselves or users.
We are doing our best to use existing or create new security tools to protect the security and privacy.
This is also a major principle that we keep in mind during the design and creation process and integrate into every aspect of our products and services.
Concise
Focus only on the parts that are really needed, necessary, or most important; hide the currently unnecessary or secondary, or simply remove the truly unnecessary and secondary; remove all unnecessary
Not only are the objects of management concise data, the user interface is also concise, and the user interaction and workflow are also concise.
Entities must not be multiplied beyond necessity.
Conciseness is also part of our DNA. We keep it in mind during the design and creation process, and it is reflected in every aspect of our work.
Easy to use
Users can use our products and services naturally and efficiently without or with little learning
Products are created to be used. If they are too complicated or have many obstacles in the process of use, the product will have little or no value.
The language, user interface, user interaction and workflow should be clear, precise, correct, concise, natural, intuitive and habitual.
Have good and complete documentation.
Have smooth communication channels.
Open
We are willing and must open our eyes, minds and hearts, actively learn the outside world including users, and continuously improve ourselves, products and services
We know that we, our products and services are not perfect. We are eager to communicate with you and listen to your opinions, suggestions and ideas. We are grateful for your reasonable suggestions. We are committed to improving ourselves, our products and services based on your suggestions, combined with our own independent thinking and judgment.
We are willing to open our system so that you can use other tools to help you access, save and manage your resources faster and better.
We will open the API of our products at some point in the future.
Maybe we will create and release community versions of our products in the future.
We actively learn, research, explore or create other knowledge, products, tools, etc., and continuously improve ourselves, products and services.
While improving ourselves, products and services, we hope that you can also benefit from this process.