Do not sell or share my personal information Skip to content

User Experience Best Practices

Plugin name should simply state the feature of the plugin and not use an existing core feature or extension in its’ title. The plugin name should appear at all times in the UI as a functional and original name. e.g “Appointments” instead of “VendorXYZ Bookings Plugin for WooCommerce.”

Avoid creating new UI. Before considering a new UI, review the WordPress interface to see if a component can be repurposed. Follow existing UI navigation patterns so merchants have context on where they are when navigating to a new experience.

Be considerate of mobile for the merchant (and shopper-facing if applicable) experience. Stores operate 24/7. Merchants shouldn’t be limited to checking their store on a desktop. Extensions need to be built responsively so they work on all device sizes.

It’s all about the merchant. Don’t distract with unrelated content. Keep the product experience front and center to help the user achieve the tasks they purchased your product for.

Present a review request at the right time. Presenting users with a request for review is a great way to get feedback on your extension. Think about best placement and timing to show these prompts.

Here are some best practices:

  • Avoid showing the user a review request upon first launching the extension. Once the user has had a chance to set up, connect, and use the plugin they’ll have a better idea of how to rate it.
  • Try to present the review request at a time that’s least disruptive, such as after successful completion of a task or event.

Don’t alter the core interface. Don’t express your brand by changing the shape of containers in the Woo admin.

Focus on the experience. After the customer installs your product, the experience should be the primary focus. Keep things simple and guide the user to successful setup. Do not convolute the experience or distract the user with branding, self promotion, large banners, or anything obtrusive.

Keep copy short and simple. Limit instructions within the interface to 120-140 characters. Anything longer should be placed in the product documentation.

Maintain a consistent tone when communicating with a user. Maintain the same communication style and terminology across an extension, and avoid abbreviations and acronyms.

In extensions:

  • Use sentences for descriptions, feedback, and headlines. Avoid all-caps text.
  • Use standard punctuation and avoid excessive exclamation marks.
  • Use American English.

For more, read our Grammar, Punctuation, and Capitalization guide.

Last updated: January 18, 2024