users use publishing forms, just like a trip. Whether the purpose of the trip can be reached or whether the process is satisfactory depends on whether the user will come here again.
one, so why is it from the user’s point of view,
as a designer, have you ever had this kind of situation:
· we add an extra entry to collect user information;
·: our form is complex because we want users to fill in more content that is useful;
· our form should appear in this most important step, so that more users can see it…… .
do you think so when you fill out a form,
· we fill out the form just to get what I want, not for you to collect information;
· if I can, I want to fill in less information or fill out the form for the same purpose;
· when I wanted to do A things, I didn’t want to see the B form at all…… .
the above situation may be exaggerated, but it is undeniable that sometimes when we do the form design, and not from the user’s perspective, to see what they want, but from where we are end point of view, allowing users to do what we want them to do.
two: how do you see post forms from a user’s perspective?
now, let’s take the previous steps into the post form design, and we can get the following idea:
, we can see that the two processes seem to be easier to ignore before and after release. And how should the design points in the process be done? As a user, take a look.
three, as a user, see the form
already exists, so let’s start as user and explore post forms.
as a user, I’m going to do something for the tools I need — the post form.
first of all, where do I enter the form?
the question is where the user will be guided to the post form in the context of the situation. See this example: