Theme Builder Pro not included in Bundles

1 Answer 395 Views

Theme Builder Pro

1 Answer, 1 is accepted

answered on 20 Oct 2022, 05:51 AM

Hello,

One of the main reasons is that ThemeBuilder Pro is currently, not supported for all web products.

We are planning to add support for those products Kendo UI for jQuery, UI for ASP.NET MVC, UI for ASP.NET Core, UI for PHP, and UI for JSP early next year. Then we are planning to start the process to add it as part of the Ultimate bundle.

This is definitely something we are already discussing and it is in our plans.

Regards,
Stefan
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

RainMaker

commented on 24 Oct 2022, 09:28 PM

I find this odd, as basically what you are saying is while the feature set is limited you are charging for it. Once you complete the feature set you will include it already purchased bundles. I understand that companies need to charge for their products, but this really feels like nickel and diming customers. The bad part is I can just lower my subscription level and purchase the theme builder and be cheaper than ultimate, and I would still get everything I need.

Stefan

commented on 25 Oct 2022, 06:25 AM

Hello,

Apologies if my statement was unclear. I will try to provide more details on this.

The feature set is not limited, the product has all of the main features available from day one and we will add new ones based on community requests.

The support for other products is something mainly related to product rendering. Our main goal is to have the same core rendering between all web components, so customers do not have to style the button N times if they support multiple frameworks. With the same rendering, you will be able to style the components once and reuse the style in other frameworks if they follow the same company style guide or design system. The reason the ThemeBuilder is not support for some of the other frameworks is that we need to make changes to some of the components in those frameworks to unify the rendering.

We never intend to just charge more, even the opposite, our concern was that if we add it to the bundle now, people may assume it is supported for all web products in the bundle. Then that could be one of the reasons they go for the more expensive bundle, just the later realise, ThemeBuilder is not supported for their framework of choice.

As for the change in subscriptions, this is why we have many purchase options to ensure that everyone can pick the best combination based on their personal/company needs.