Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blocks: differentiate premium blocks from free ones when customer doesn't have paid plan #11875

Closed
thomasguillot opened this issue Nov 29, 2018 · 13 comments
Labels
[Focus] Blocks Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack [Pri] Normal [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it

Comments

@thomasguillot
Copy link
Contributor

thomasguillot commented Nov 29, 2018

Update 9th August 2019: premium blocks now discoverable for free customers in the block picker, I've changed this issue to be more specific about the presentation of these blocks in the block picker since that's what these designs are concentrating anyway. - @simison


As stated in the documentation:

The feature is available to Premium and Business plan subscribers on WordPress.com and on Premium and Professional plans for Jetpack sites running version 5.2 or higher.

Which makes this block completely hidden for other users.

Here, I suggest:

  1. Show the block button but disabled
  2. Attach a tooltip to it (different content depending on Jetpack or WPcom user)
  3. Link the tooltip to an upgrade screen

screenshot 2018-11-29 at 11 09 55

And use this pattern for all future blocks requiring a plan.

@simison
Copy link
Member

simison commented Nov 29, 2018

How should it look like for touch screens?

image

@thomasguillot
Copy link
Contributor Author

How should it look like for touch screens?

I see this to behave just like the tooltip menu: https://cloudup.com/cYHt14ThyJR

@marekhrabe
Copy link
Contributor

Adding one more question: What should it look like if user ends up with this premium block (which they don't have rights to use) already inserted into the post?

This could happen in many ways: copy&pasted block from another site with this feature active, handwriting its code, site export+import flow etc…

@thomasguillot
Copy link
Contributor Author

At the moment, this is what a user would get if they downgrade/don't have the correct plan but have a SP block:

screenshot-2018-12-13-at-17 06 55

Instead, we could use a placeholder, encouraging users to upgrade. Also, we wouldn't have to show the shortcode!

x wrong plan

@marekhrabe
Copy link
Contributor

marekhrabe commented Dec 13, 2018

I'm not familiar with the Gutenberg block picker and how easy it is to disable a block there and add the popover with upgrade link. If that's something that is not ready out of the box now, wouldn't it be easier to always allow the block to be inserted and decide inside the block edit() whether to show the upgrade screen or its real UI?

@scruffian scruffian transferred this issue from Automattic/wp-calypso Apr 3, 2019
@scruffian scruffian added [Pri] Normal [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it [Focus] Blocks Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack Simple Payments labels Apr 3, 2019
@simison
Copy link
Member

simison commented Aug 9, 2019

Why is this important? It saves customers from disappointing surprises and feeling of uncertainty about other blocks.

A couple more ideas that have been floating around:

  1. Separate categories were explored in Gutenberg: Add a premium block category #12431
    Screenshot 2019-05-21 at 13 59 20
    Note that categories are greyscale in latest Gutenberg, so icons as separating factor won't work anymore.

  2. Show different icon color
    Screenshot 2019-08-09 at 09 32 15

  3. Show colored border
    Screenshot 2019-08-09 at 09 32 33

  4. Add "Premium" suffix to block name (hat tip to @ockham)
    Screenshot 2019-08-09 at 09 33 51

  5. A ribbon around the block name in the block picker (hat tip to @ockham, see PR Blocks: Add Ribbon to indicate Paid blocks in block picker #13490)
    image

Note that this menu also would need similar mechanism:

image

@simison simison changed the title Simple Payments: Make the block more discoverable for non-Premium users Simple Payments: differentiate premium blocks from free ones when customer doesn't have paid plan Aug 9, 2019
@simison
Copy link
Member

simison commented Feb 10, 2020

Idea via @mtias:

Don’t mind the presentation, but using the block description card for this could be interesting
image

(PR for help panel in core WordPress/gutenberg#16813)

@jeherve jeherve changed the title Simple Payments: differentiate premium blocks from free ones when customer doesn't have paid plan Blocks: differentiate premium blocks from free ones when customer doesn't have paid plan Feb 10, 2020
@obenland
Copy link
Member

More ideas via @lessbloat:

image

@WunderBart
Copy link
Member

WunderBart commented Feb 11, 2020

I really like the idea of the badge icon from #11875 (comment). To address the currency issue (cc @lessbloat), maybe instead of the dollar sign, we could use e.g. a star icon as an indication of a premium entity? I also think that explaining what that icon means as suggested here #11875 (comment) would be a good idea. The premium icon would also be convenient as an indication in the / triggered list (re: #11875 (comment)).

Together, it could look more-less like this:

jetpack paid blocks selector design

@davemart-in
Copy link
Contributor

I really like that @WunderBart. The only minor change that I would make would be to make the orange border around the paid plan description in the block preview the same color green as the icon. Nice work! Let's do this! Let me know what you need from me to make this happen.

@obenland
Copy link
Member

@WunderBart @jeryj Based on the latest comments on paYJgx-rs-p2#comment-659, let's also separate these premium blocks out into their own category.

@WunderBart
Copy link
Member

WunderBart commented Feb 24, 2020

Thanks for the update, @obenland. To summarize the initial direction we've decided to take - we're going to:

cc @davemart-in, @jeryj.

@jeherve
Copy link
Member

jeherve commented Aug 7, 2023

This has now been built, so this issue can be closed. Thanks everyone!

@jeherve jeherve closed this as completed Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Blocks Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack [Pri] Normal [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it
Projects
None yet
Development

No branches or pull requests

8 participants