Features by SDK Versions

SDK Overview

📘

Ensure that the Sprig SDK is up to date to take advantage of new features and bug fixes

Note: In the case of mobile SDKs, your end users will additionally need to uptake the latest version of your product’s application to be compliant. Usually, this means pushing a release via the Apple App Store or Google Play.

🔧 for more technical details, check out our SDK Changelogs

Features and SDK Versions

Not all product updates require SDK updates, but certain functionality, especially related to Replay recording, question types, or the survey taker experience, often requires SDK updates.

SDK Versions by Feature

Upgrading SDKs

We adhere to Semver for versioning our SDKs so upgrading between minor versions or patches (e.g. 2.0.0 -> 2.1.0 or 3.1.0 > 3.2.1) should not present any breaking changes. You can view the release logs here

How do I upgrade my Sprig SDK to the latest version?

If you installed with HTML, Segment, or Google Tag Manager your SDK will be automatically upgraded.

For npm and Yarn install methods, reach out to your development team to upgrade the SDK to the latest version. Please note that if utilize additional Products and Environments you will need to update the in each place that the SDK is installed.

Mobile SDK installs, including iOS, Android and React Native, will require developer help to upgrade versions. Additionally, if bundled with an app store release, users will need to update to the latest version ofyour companies mobile application in order to be eligible for a Sprig survey (or Replay) that requires a minSDK version.