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

[website] Polish the pricing page #32811

Merged
merged 20 commits into from
Jun 1, 2022

Conversation

@oliviertassinari oliviertassinari added the website Pages that are not documentation-related, marketing-focused. label May 17, 2022
@mui-bot
Copy link

mui-bot commented May 17, 2022

No bundle size changes

Generated by 🚫 dangerJS against 9aaa73e

@@ -86,8 +87,8 @@ export function PlanPrice(props: PlanPriceProps) {
$0
</Typography>
<Box sx={{ width: 5 }} />
<Typography variant="body2" color="text.secondary">
– free forever.
<Typography variant="body2" color="text.secondary" sx={{ mt: '4px' }}>
Copy link
Member Author

@oliviertassinari oliviertassinari May 17, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it feels better aligned visually?

<Typography variant="body2" color="text.secondary">
– free forever.
<Typography variant="body2" color="text.secondary" sx={{ mt: '4px' }}>
– free forever
Copy link
Member Author

@oliviertassinari oliviertassinari May 17, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong punctuation?

@@ -337,7 +338,7 @@ const rowHeaders: Record<string, React.ReactNode> = {
'MUI Base': (
<ColumnHead
label="MUI Base"
tooltip="The unstyled components and react hooks available at @mui/base."
tooltip="Unstyled components and react hooks available at @mui/base."
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency with the other description. It's also less pretentious.

@@ -922,11 +931,11 @@ export default function PricingTable({
<RowHead startIcon={<IconImage name="product-core" width="28" height="28" />}>
MUI Core (open-source)
</RowHead>
{renderRow('Material UI')}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it matches our order in

Screenshot 2022-05-17 at 19 57 23

software <strong>always</strong> need an active license. So if you wish to continue
active development using the software after the end of your subscription, you will
need to renew your subscription. You can learn more about it in{' '}
<Link href="https://mui.com/store/legal/mui-x-eula/">the EULA</Link>.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have been eager to place a link to the EULA somewhere on the page for a long time. I have found one opportunity here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's nice we have it, but I was seeing this section more as a spot to advertise some advantages of using MUI X.

Like:

  • Continuous delivery of improvements and new features.
  • Effort to reach the best UX and DX.
  • Community driven (we listen the community pains)

Perhaps we can merge this section with "Perpetual in production" and use the free slot to expose some attractive outcomes of our efforts.

WDYT?

Copy link
Member Author

@oliviertassinari oliviertassinari May 17, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The initial idea of this section was to bring as much clarity as possible to avoid support questions; It was modeled after https://www.telerik.com/kendo-react-ui/pricing/. It's why the h2 is called "What to expect from our available plans". It was not meant to sell the plans but more to explain the EULA.

I'm not against addressing some of the "losses" that customers might have on the pricing page (fear of losing out) but I think that it should stay light and the page to stay clearly structured (so maybe in a new section). I believe that https://mui.com/x/ would be better suited for diving deeper in the value propositions, linked from the pricing page.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was revisiting this and what you described sounds like a special section in the frequently asked questions. I believe "What to expect from the plans" could focus on "What you get during your license term".
So maybe "Development license" and "Volume discount" could be moved to the FAQ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that these points will get less visibility on the FAQ. I have updated the h2 to "Key information about the paid plans" to encourage people to read it all.

@oliviertassinari oliviertassinari marked this pull request as ready for review May 17, 2022 18:04
@mbrookes mbrookes changed the title [website] Polish on the pricing page [website] Polish the pricing page May 18, 2022
@oliviertassinari oliviertassinari requested a review from mbrookes May 25, 2022 10:55
If you need to share private information, you can{' '}
<Link href="mailto:x@mui.com">email us</Link>.
(If you need to share private information, you can{' '}
<Link href="mailto:x@mui.com">email</Link> us.)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we decide to remove this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not against keeping it in hindsight. As of now, it doesn't feel like we receive a lot of requests by email. We could create an email template to answer automatically to lost requests. For developers, knowing that there is an email they can reach in the worse of the situations could maybe make them feel more secure.

<Link href="https://mui.com/x/advanced-components/#support">
learn more about support
</Link>{' '}
in the docs. Note that, except for critical issues, e.g. security, we release bug
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
in the docs. Note that, except for critical issues, e.g. security, we release bug
in the docs. Note that, except for critical issues such as those impacting security, we release bug

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have enough space for this suggestion, or we would need to find a way to balance it https://deploy-preview-32811--material-ui.netlify.app/pricing/

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the feedback. I hadn't looked at it in context, but do now see the problem. In this case feel free to disregard the review.

Co-authored-by: Matt <github@nospam.33m.co>
Copy link
Member

@joserodolfofreitas joserodolfofreitas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see you pulled back some changes on the plans' descriptions and +1 to that.
We already have the imperative on the CTA, so we can instead focus on the use cases for the description. I wanted to give a new try on them.

@@ -18,19 +18,19 @@ const planInfo = {
community: {
color: 'green',
title: 'Community',
description: 'Get all the MUI component libraries, MIT-licensed, open source, and open core.',
description:
'Get all the MIT-licensed MUI component libraries, including open-source and open-core code.',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should capitalize on being market leaders and also I don't think the focus on the license brings much value here.

Suggested change
'Get all the MIT-licensed MUI component libraries, including open-source and open-core code.',
'The #1 UI library for fast-developing beautiful react applications.',

},
pro: {
color: 'blue',
title: 'Pro',
description:
'Unlock essential features for building data-rich applications with complex use cases.',
description: 'Best for professional developers building enterprise or data-rich applications.',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
description: 'Best for professional developers building enterprise or data-rich applications.',
description: 'Your go-to option for building data-rich applications with complex use cases.',

},
premium: {
color: 'gold',
title: 'Premium',
description:
'Access the most advanced features necessary for data-rich applications, as well as the highest priority for support.',
'The most advanced features for handling data-rich applications, as well as the highest priority for support.',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
'The most advanced features for handling data-rich applications, as well as the highest priority for support.',
'The most advanced features for handling data in enterprise applications, as well as the highest priority for support.',

@oliviertassinari
Copy link
Member Author

I see you pulled back some changes on the plans' descriptions

@joserodolfofreitas I have reverted back to what we had in https://v5-0-6.mui.com/pricing/, mostly.

@oliviertassinari
Copy link
Member Author

oliviertassinari commented May 31, 2022

I wanted to give a new try on them.

@joserodolfofreitas +1 for the initiative, however, I have reverted back to what we mostly had in https://v5-0-6.mui.com/pricing/ so it doesn't delay this PR. I think that it was better on v5.0.0 than HEAD. This way, we can iterate on it independently of the other changes here, no need to move faster than the time it takes to explore the whole problem scope.

@oliviertassinari oliviertassinari merged commit 177af6c into mui:master Jun 1, 2022
@oliviertassinari oliviertassinari deleted the pricing-final-tweaks branch June 1, 2022 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
website Pages that are not documentation-related, marketing-focused.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants