You want to find evidence, but the packaging of the tableware has already been thrown away. So you had to ask the waiter with a smile, "Do you want to know how whatsapp Database powerful my right hand is?" It's a story about nature descriptions and nature tasks, and it looks like a third-rate novel used to swindle royalties. Like the order of the food in a story, the vast majority of our users live without technical dictionaries. Therefore, the use of natural whatsapp Database descriptions that conform to user habits and scenarios is an inevitable requirement for accessible design. natural description This is already a well-known principle.
It has existed since I didn't know what interaction design is. Everyone understands that in general, don't use technical terms or uncommon idioms whatsapp Database for users, such as jumping out of a memory overflow. Dialogs filled with all kinds of code are not recommended. For example, when filling out a form, warning the user that "this field already exists in the database" is quite frustrating. Designers do this. That's great, and more developers who are fluent in the whatsapp Database jargon are increasingly able to actively use natural descriptions in development and communication. (Pardon me for saying this, but that wasn't the case a while ago, and it was frustrating for interaction designers.) Not much to say about that.
In addition, in some cases, natural descriptions cannot perfectly handle certain scenarios and tasks. Natural descriptions are generally wording whatsapp Database principles and techniques. For the optimization principles of task scenarios and processes, I call it "natural tasks". ": natural task Here are two examples of tossing: Case 1. The download task encountered a problem. When users start to download a task, they will encounter several special problems. From a technical point whatsapp Database of view, after the user submits the download request to the server, the feedback from the server to the user is as follows.