On Tuesday March 25th, 2025 we hosted a webinar on the evolution of the developer experience for website developers on Wix and Wix Studio. This informative session covered recent improvements to the developer experience and the shift from Velo to SDK.
In case you missed this session, you can watch the replay here.
Here are all the questions you asked during the session with answers. Some questions may have been shortened for clarity.
-
What is the future of $w?
A: There is no set in stone answer yet. We are planning on having $w as part of the sdk eventually, but the final form this will take is yet to be determined. -
Does SDK support treeshaking?
A: Yes. -
Why are frontend SDK methods asynchronous?
A: This was done so that the methods will work the same for applications as well as sites. -
I would like to know which CRM app or feature is recommended to manage customer experience and communications throughout website interactions such as chat, email forms, WhatsApp chary etc.?
A: Wix has its own CRM solution you can utilize and customize using our APIs. The solution includes control over site members as well as sending out Triggered Emails. Whatsapp and its features are possible to integrate into the Wix platform using our 3rd party integration solutions and APIs. -
Any plans to have a dedicated staging environment as opposed to the test site URLs? When a client site is live, its virtually impossible to test new features and functionality if the client now also has access to editing.
A: We have a feature in the works called “site branches”, which allow you to continue and maintain your live site, while working on a new revision of your site’s UI or backend functionality that you can test without publishing. This way you’ll be able to work on alternate versions of your sites without it being reflected on the live site until you decide! -
If I use my own original code, will I have ownership or will Wix have ownership of the code?
A: Any original code that you write on the Wix platform remains your property. Wix does not claim ownership over the code you create. -
Does using the SDK improve web site performance?
A: SDK and Velo API have no performance differences, however we are working on other performance improvements. -
Is the SDK for the Wix Studio editor only, or available in the Classic editor too?
A: The SDK can be used anywhere you build on Wix which includes Classic Editor, Wix Studio, Apps, and Headless. That’s one of the main benefits of using the SDK as it applies everywhere you develop on Wix. -
What’s the benefit to migrating existing projects to use SDK?
A: There is no need to migrate existing projects to SDK. Velo will continue to work, however, Velo API will no longer be updated. So, as you start new projects or need new features, you will want to adopt the SDK. -
Is there a SDK product roadmap with features and release dates that we can refer to?
A: We do not currently have a roadmap specific to SDK. To keep up with updates, check the release notes and join the Discord community for news and conversations. If there are specific features you are interested in, please let us know. -
Previously, you mentioned that existing applications built on the older SDK would continue functioning without the necessity to migrate to the new SDK. However, we’ve observed that new features are no longer being added to applications utilizing the older SDK, effectively pushing developers towards migration. The challenge is that the new SDK does not offer the same level of flexibility and control that was available in the older version, significantly limiting our ability to maintain and enhance our application’s functionality. Could you please clarify if there are any plans to either extend feature support for applications built on the older SDK or address the flexibility issues present in the new SDK? Any insights or guidance you can provide would be greatly appreciated.
A: The move to SDK is to increase the velocity of releasing API enhancements, while providing a predictable and highly reliable release process and better control to developers. If a site is being actively maintained for the long run, then we do recommend migrating to use the SDK. If you have feedback for a specific SDK that is not meeting your needs, please let us know in Discord, the forum, via customer care, or through your partner success managers. -
What’s happening with realtime? For a blocks environment?
A: Thank you for the request. We do not have a specific timeline for the release of realtime in the blocks environment. You can see any open feature requests for Wix Blocks here and follow their status. -
Can we have some examples on the readme files for SDK packages?
A: We love this idea. Thank you for the suggestion and we will consider how to do this. -
If I start a new project today, will it be based on SDK or do I need to do anything?
A: SDK is available wherever you build. You do not have to do anything specific and we do recommend using it for any new projects you start. Here is a video that can introduce you to using the SDK -
I would love to see ODBC Connectivity, the ability to create Queries, and run VB Script?
A: Thank you for the request. To ensure feature requests are routed appropriately, the best place to submit feature requests is through our product roadmap. -
One follow-up question regarding the SDK…the documentation includes several comments like: “This function is in developer preview and is subject to change.” Could you clarify the expected timeline for moving these functions from developer preview to stable please?
A: Developer preview APIs are opened to give developers the ability to test upcoming features and provide feedback during the development process. In general, these APIs will be production ready within 6 months. You can read more about Developer Preview APIs in the documentation. -
Is there any plan to move away from the Wix editor?
A: No. Classic Wix and Wix Studio are two separate products and are intended for different uses. You can use whatever serves your clients best. -
I’m only getting started with the coding part of Wix. Do you have any resources that can help me as a beginner in this?
A: Our documentation is a great place to start learning. -
Do we get a notification when a new NPM package version is released within the editor?
A: Currently you can see if an NPM package you have installed on your site has a newer version by opening the package manager in the editor and filtering by “installed”. Keep in mind that you do not need to update a package version unless there is a feature that you need that is not available in the version you have installed. We are always working on improvements and appreciate this idea.. -
I’m curious to know how Wix came up with Velo Package Manager instead of using NPM in the first place. I feel the SDK is the obvious solution and I welcome the change but I’m curious to know why it was not done like this in the first place.
A: Support for “any npm” was added in late 2023. Prior to this, we only supported Velo packages and NPM packages that were evaluated and certified by our team. The Package Manager facilitated this process. It also takes care of configuring the site so the necessary packages are readily available when the code has to be loaded and run in the most performant way possible. As more professional developers started using Wix and Velo to build sites, better support for NPM was a frequently requested feature. With the introduction of Wix SDK into Velo, we’re also introducing autocomplete for any npm.
Thank you to everyone who took part in the webinar today. If you have any more questions, please feel free to comment on this post.