Top
Walkthrough Best Practices
  • 30 Apr 2024
  • 2 Minutes To Read
  • Dark
    Light
  • PDF

Walkthrough Best Practices

  • Dark
    Light
  • PDF

Article summary

Use Walkthroughs for product tours and tutorials

Use Walkthroughs for sequential actions. For example, product tour, tutorials, and UI guidance.

Use the Walkthrough Checklist for user training and onboarding

Use the Walkthrough Checklist for user training. Walkthrough Checklist can be used to ensure that your end users can perform all basic tasks. For example, you can use a Walkthrough Checklist to design an onboarding list of tasks for someone new to your app.

Use simple and descriptive titles for Walkthroughs

Name every Walkthrough clearly for easy retrieval during search. Use simple and descriptive words that your audience is likely to use. Keep the title short and don't use gerunds.

image.png

Use a brief description in Tooltips

Use easy-to-understand words and simple sentences. Keep the description in your tooltip simple and to the point.

Mobile_bp_keep description short.png

Use Dismissible Icon to start a Walkthrough or Walkthrough Checklist

Configure a Dismissible Icon to appear on the app screen to enable your end users to start Walkthrough, Walkthrough Menu, and Walkthrough Checklist whenever they want.

dismissible_icon

Create Walkthroughs in a stable environment

Create Walkthroughs on production/live apps that are stable and not constantly updated by code changes. If the underlying code of your app is changed, it may break any Walkthroughs that you may have created.

mobile_bp_stable site.png

Limit the number of steps to 5

Limit the number of steps in a Whatfix Walkthrough to no more than 5 steps. This helps your users understand the value proposition of your guides quickly and easily.

Set Discovery Trigger and Flow Termination Conditions

Define Discovery Trigger rules to start the Walkthrough based on different criteria. You can also define Flow Termination conditions to dismiss the Walkthrough from the app screen.

discovery_trigger_event

Ensure that your Tooltips don't hide any UI elements on the screen

Position the Tooltips so that they don't hide any elements on your app screen. In certain cases, the Tooltip could inadvertently hide certain important UI.

Mobile_bp_do not hide ui.png

Use Optional Step to ensure Walkthrough continuity

When you have a field/element in an app that does not appear to a certain set of users, configure such steps as Optional to ensure the continuity of the Walkthrough.

If the field/element does not appear, the Optional steps are skipped, and the Walkthrough continues to the next step. If the field/element is present in the UI, then the Walkthrough progresses as usual. You do not have to create a separate Walkthrough and trigger it based on the appearance of the field/element.
mobile make step optional.png

Author clear and concise content

Use simple words and sentences while creating Whatfix content. Keep the description in your Tooltip brief and to the point.
Mobile_bp_keep description short.png

Choose an appropriate theme for the Tooltip

Choose the best available Tooltip theme to ensure that the design of the Tooltip matches your app’s UI. Use contrasting colors that make the Tooltip noticeable on your app. This is to ensure that the Tooltips are not lost in your interface because they can't be distinguished from the underlying app.
Mobile_bp_consistent theme.png

Speak to your end users

Users who are new to the mobile ecosystem follow audiovisual guidance better. Provide a natural experience using audiovisual guides. For more information, see Add or generate Audio for your in-app experience.
mobile_add audio_audio


Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.