If your store is built using the VTEX Store Framework and you are missing that one special storefront component, we have good news: previous authorization is no longer required to use the VTEX React builder!
From now on, develop custom storefront components in VTEX IO using the VTEX Store Framework and React technologies according to your business needs, without asking VTEX for permission.
Store Framework is the VTEX solution to build storefront in lightning speed. VTEX customers can leverage all its benefits by using the VTEX IO development platform. If you are not familiar with the VTEX IO yet, get in touch with your Customer Success, Account Manager or SI Partner Agency to know how to start!
What changed?
Before, developers interested in creating custom components using the VTEX Store Framework had to request our authorization. They had to fill in an application form sharing their project's details and wait for our approval to use the React builder.
This is no longer required as we officially move our React builder to open beta status. You can take advantage of this autonomy to further customize and improve your storefront experience using React technology.
This change applies only to the React builder. We continue to require that you fill in the Application form for development and wait for our approval if your project depends on builders that are still in closed beta. This includes, for example, back-end integrations using Node.js and GraphQL.
Why did we make this change?
We understand that VTEX IO has now reached enough maturity and stability as a development platform to support all types of React projects. This allows us to offer more autonomy and agility to our ecosystem, providing the flexibility needed for developers to address the various business needs of our customers.
What needs to be done?
No actions are needed from your side. Keep in mind, however, that VTEX does not provide support to custom components developed by third-parties. Their maintenance, performance, and quality is under the responsibility of the app's vendor.
Check out our documentation on best practices for storefront component development!