Using plugin pointers, much like pointing, is rarely appropriate

Categorized under:

Photo of author
Written By Brian Krogsgard

5 thoughts on “Using plugin pointers, much like pointing, is rarely appropriate”

  1. I agree with you, that they should rarely be used. I skimmed the article and jumped to the comments, and noticed they mentioned Yoast as one they like. His implementations is one of the ones I dislike the most. I once activated his plugin and was greeted with two overlapping pointers. I was so annoyed I started grabbing screenshots for a ranting blog post, but never published it. So, thanks for saying this.

  2. I agree 100% the pointers can be really annoying. A perfect example is the recently-ish updated WordPress SEO plugin, if you’ve used it, you know exactly what I mean. Pissed off a lot of people from what I saw on social media networks.

  3. Yoast is a perfect example of a need to rethink all those options. I feel like pointers are a developer solution to a design problem.

    As a designer I can write php and most devs will laugh at it, its not pretty but it gets the job done. The same is true when the rolls are reversed.

  4. I agree that they are very annoying in most uses. Before sending a site for review, I’ll log in as them to clear out the pointers if we have a plugin that overuses them (WordPress SEO).

    But there is one way I do use them. If I want a client to do a specific thing when they log into their site for the first time, I’ll use a pointer. My only real use case here is my Password Pointer plugin. I create a random, strong password for clients and encourage them to change it. Most clients don’t know where they can do this, so I have a pointer to show them.

Comments are closed.

A2 Hosting