How Starscriber uses Unlaunch to roll out changes to its Chatbots faster

Intelligent Messaging Solutions

Starscriber is a multinational company headquartered in California, focused on making high value mobile prepaid services easier to access and use. Today, millions of users use its product every month to buy services, borrow credit and add funds to their mobile accounts. They realized the potential of using feature flags to launch new features quickly, allowing early access to their worldwide QA developers. After trying out various other services and considering building it in-house, they decided to stick to their core competencies and use Unlaunch to power new features and delight their users.

“What's interesting with Unlaunch is that we can launch new features rapidly into production to our teams and get quick feedback. It was hard to get this sort of feedback before as the new feature would sit in a different environment and it wasn't accessible to everyone. There was an added friction point - "hey, switch to this server to check out the new feature and give feedback." Now, we just launch it targeted to our team and the feedback starts flowing in. ”
Lukasz Piwowarek

Lukasz Piwowarek

Head of Operations, Starscriber

Confidence to Release Faster

With hundreds of thousands of daily users using its product, new releases were risky and required a lot of coordination between product, engineering and QA teams. What really set Unlaunch apart from the competition was how easy the team was able to integrate its Java SDK, and use Percentage Rollout to show features only to a small number of users initially. This allowed Starscriber to get early feedback, monitor the load on its systems and gradually ramp up the feature to include more users.

“Our engineering team was able to integrate with Unlaunch using its SDKs quickly and shipped the first feature within the first week. The UI and SDKs were intuitive and developer friendly. Before Unlaunch, releases were risky business and questions like 'what if something goes wrong and we end up losing sales' made them extra stressful. Now, we have the flexibility to instantly disable a misbehaving feature in production and apply changes in real-time.”
Lukasz Piwowarek

Lukasz Piwowarek

Head of Operations, Starscriber

Sticking to Core Competencies

After trying out various other services and considering building it in-house, they decided to stick to their core competencies and use Unlaunch to power new features and delight their users.

“We did consider building a simple feature flag system in-house. But then we decided not to go that route because it will be another thing for us to maintain. Also, a simple on-off flag is probably easier to build in-house but as you want to get complex and target by attributes, times of days, etc. it gets complex. The team was not willing to invest in something that's not our core focus. ”
Lukasz Piwowarek

Lukasz Piwowarek

Head of Operations, Starscriber

Start Releasing Features Faster Today!

Free Account