Twilio started updating the Helper Libraries to an improved platform starting mid-2016. This will be a much improved experience for developers and how they build with Twilio. A gradual roll-out will be done to ensure we have supporting documentation for the new libraries. The legacy Helper Libraries will get sunsetted in the timeframe outlined below.
The scheduling for each language is as follows:
|Language||Go Live Month||Documentation||RC Candidate Link|
|PHP||August 2016||Docs, Migration Guide, Blog Post||Released|
|Java||October 2016||Docs, Migration Guide, Blog Post||Released|
|C#||February 2017||Docs, Migration Guide, Blog Post||Released|
|Python||April 2017||Docs, Migration Guide, Blog Post||Released|
||Docs, Migration Guide, Blog Post||Released|
|Ruby||July 2017||Docs, Migration Guide, Blog Post||Released|
Important Note about Release Candidates (RC):
Install RC candidates at your own risk as their documentation is still in progress. New and updated features will be available in the RCs at launch. If you want to use the RCs with your existing Twilio built app, all of the features that are available in Next Gen that are not available on Legacy are in Developer Preview.
Why is Twilio changing the libraries?
We learned from our customers’ feedback and improved what works well where we can do better. There are several major improvements that we made with the new libraries.
- The new libraries are auto-generated. That lets us rapidly add new features, it adds consistency across versions and languages.
- We added stronger typing for languages that support it
- Modernized the helper-libs. Languages like PHP evolved a lot since we first launched the SDK.
What’s new in the new libraries?
See the blog posts linked above for language specific details.
What will happen to the old libraries?
Going forward, new functionality will only be added to the new GA libraries (PHP 5.x, Java 6.x etc). The old libraries (PHP 4.x, Java 5.x) will be officially supported for 90 days after the new version gets announced. After that day, Twilio will stop providing bug fixes and Support might ask you to upgrade before debugging issues.
Will the deprecation of the libraries break my application?
No. The helper-libraries are client side code and the depreciation will not change how applications behave. It is up to the developer to upgrade to the Current (see definition above) libraries to receive the latest bug fixes and support.
What are the Helper Library version numbers?
|Language||Legacy version||Next-gen version|
|PHP||<= 4.x||>= 5.x|
|Java||<= 6.x||>= 7.x|
|C#||<= 4.x||>= 5.x|
|Python||<= 2.x||>= 3.x|
|Node||<= 2.x||>= 3.x|
|Ruby||<= 4.x||>= 5.x|