How OkCredit Android App Improves UX Writing by Changing Strings on the Fly
Article Summary
OkCredit found a way to A/B test UI copy without shipping new app versions. The results? A 1.7% lift in user activation from changing just two words.
The digital ledger app serves millions across India in 11+ languages. Their product team was stuck waiting for app releases every time they wanted to test new messaging. They needed a solution that worked at scale.
Key Takeaways
- Used Philology library to intercept view inflation and swap strings dynamically
- Tested 60K users over 10 days with different payment terminology variants
- Achieved 1.7% increase in activation rate by optimizing two button labels
- Setup enables real-time string experiments without code deployments
- Custom data source integrates with A/B testing for cohort-based rollouts
Dynamic string replacement let OkCredit run UX copy experiments that improved activation by 1.7% without releasing new app versions.
Continue reading
What This Article Covers
OkCredit's localization team kept hitting roadblocks when testing string translations across 11+ languages. Every time they wanted to change terminology, they had to wait for a full app release cycle.
Rashanjyot Singh's team built an integration using the Philology open-source library. It intercepts view inflation and pulls updated strings from a custom data source tied to their in-house A/B testing framework.
The solution has held up well over two years of heavy use. They can now run real-time string experiments without deploying new app versions. One experiment with payment terminology changes led to a 1.7% increase in user activation.
This page summarizes “How OkCredit Android App Improves UX Writing by Changing Strings on the Fly” by OkCredit, published Sep 13, 2022. All credit for the original work goes to the authors.