A change of look but not only!
We've reorganized the documentation, it's had a facelift but that's not all; it also includes examples of JS implementations and a new search function for all documentation.
And, because we like to hear feedback from our users, you can now share your comments and suggestions in the documentation. So get to your keyboards and let us know what you think!
Want to see it?
👉 Consult the Developer documentation
Handling data cached on Android, Java, JS & React SDKs has never been so easy.
To improve the development experience, we have streamlined and optimized the Android, Java, JS & React SDK architecture and the way data is cached on SDKs.
You can now customize the way the cache is managed. You (or your developers) can implement your own cache and tailor what it does or does not cache.
A quick reminder on what the cache offers natively:
Prevent user reassignment as the assignment is stored in the cache: a visitor will always be assigned to the same variation.
Prevent data loss as the cache stores the hit and returns it later in case of an issue.
Manage Offline moments. No connection, no worries, the SDK will take the last stored value.
Want to know more?
👉Check out the Android user documentation
👉Check out the Java user documentation
👉 Check out the JS user documentation
👉Check out the React user documentation
Managing flags just got easier.
Making developers' lives easier is in our ADN. This is why we updated the Flag management and revamped the getModification, getModificationInfo, activateModification and synchronizeModification methods to make it easier to understand.
From now on, the following method will be swapped:
- getModification() -> getFlag(“newRelease”).value()
- getModificationInfo() -> getFlag(“newRelease”).metadata()
- activateModification() -> getFlag(“newRelease”).userExposed()
- synchronizeModification() -> fetchFlags()
This redesign of the methods allows for easier implementation, more self-service and better accessibility of information ("all in one" method).
PHP was updated to v2, and therefore is now compatible with experience continuity and Bucketing mode.