Using the in-app help page
In-app help should be the primary method of displaying help for users. It should be simple, clear, and use for any article that does not introduce new content to users. Guidelines, tips, and tricks are all appropriate for in-app help.
Complex instructions or tutorials are difficult to quickly refer to and take up a large amount of space. Therefore, you must host it externally and you should not integrate it into the app itself.
Users should not need to search for help to get basic instructions or find new features. If you need help educating users, use the Usage Guide UI.
All in-app articles follow the same general principles of design and usability, but they can come in many forms.
Help page
Including a separate help page within your app can help you quickly and easily display useful instructions.
It will be concise. A large library of help topics is uncomfortable and unsuited for help in the app.
Consistent: Make sure that the user can connect to the Help page in the same way in all parts of the app. You do not need to search.
Users read and search: Other help topics are on the same page as users can be looking for help, so make sure you can easily tell which one you need to focus on.
Check.
pop-up
Pop-ups are effective for context-sensitive help and display instructions and advice related to the specific task you are attempting.
Focus on one problem. Spaces are much more restricted to pop-ups than help pages. Help pop-ups should point to a single task in order to be effective.
It is important to display. The help popup is only visible in one place, so make sure the user is not obstructive to the doc. If the user does not see it, they may leave the pop-up to search the help page.
Do not use too many resources. Help should not be delayed or slowed to load. Using a video or audio file or a high-resolution image in a pop-up is more likely to cause inconvenience, not help.
Explanation
Sometimes it can be useful to provide more information about the feature as you look at it. The description is similar to the Usage Guide UI, but the main difference is that the Usage Guide UI tries to inform the user about unfamiliar features, and the detailed description is to increase user understanding of the app features you are already interested in.
Do not explain the basics. It assumes that you already know the basic concepts of how to describe the user and how to use the item. It is useful to provide a clear description or additional information. It does not make sense to explain what you already know.
Explain interesting interactions. One of the most efficient uses for the description is to educate the user on how to manipulate the features that you already know. This will help you learn more about the features you already use.
. Much like the instructional UI, you need to explain it if you do not want to hinder the user's enjoyment of the app.
0 Comments: