Case study · Enterprise knowledge
CloudCherry SDKs
Survey collection that a developer can integrate in minutes.
- Client
- CloudCherry
- Service
- SDK development and design
- Sector
- Customer experience
- Reach
- 2,000+ enterprises, 14 countries
Impact
What the SDKs changed
Integration time fell from several days or weeks to a few minutes.
Higher response rates on mobile than the web-only approach it replaced.
Overall engagement increase across the platform.
Integrated the SDKs successfully, which is the real test of a developer product.
The brief
A CX platform is only as good as its response rate
CloudCherry serves customer experience management to more than 2,000 enterprises across 14 countries. Its product depends on two things happening: a developer at a client successfully embedding survey collection, and an end user actually answering.
Both were leaking. Integration meant complex workflows and custom code against unclear documentation, so developer friction delayed launches. And response rates on web lagged badly behind mobile, which meant the channel most customers were in was the one collecting least.
Two different audiences, one product. The developer has to succeed before the end user gets asked.
The build
Remote updates are the quiet feature
The headline is the integration time — weeks to minutes — and that came from treating documentation and default behaviour as product surface rather than afterthought. Hundreds of developers integrating successfully is the metric that validates it.
The feature that changes the platform's economics is quieter: surveys can be updated remotely without redeploying the app. Without that, every question change waits on a client's release cycle, which for a CX platform means the product moves at its slowest customer's pace.
Contextual triggering did the rest. Asking at the moment of an action rather than on a schedule is what produced 5x mobile response rates and a 20% overall engagement increase.
The two SDKs
Native and web
Android SDK
A native, open-source library supporting multiple authentication flows, both static token and dynamic credential based, so it fits whatever a client's app already does.
Microsurvey SDK
A lightweight, customisable TypeScript library for the web, designed to work with modern frontend frameworks rather than fight them.
Contextual and remote
Surveys trigger on user actions rather than on a timer, deliver in real time, and can be updated remotely without redeploying the host app.
Stack
What it was built with
Questions
The CloudCherry SDKs, answered
What did Wow Labz build for CloudCherry?
Two SDKs: a native open-source Android library, and a lightweight customisable TypeScript microsurvey SDK for the web, plus the design around them.
How much faster is integration?
Integration time went from several days or weeks down to a few minutes, and hundreds of developers integrated the SDKs successfully.
What happened to response rates?
5x higher response rates on mobile, and a 20% overall increase in engagement, largely from triggering surveys contextually on user actions rather than on a schedule.
Can surveys change without an app release?
Yes. Surveys update remotely without redeploying the host application, so a question change does not have to wait for a client's release cycle.
Let's talk
Got a developer product nobody finishes integrating?
Tell us what you are building. We will tell you how we would ship it.
