Hi — I’m Rishabh.
Mobile growth & monetization engineering.
Computer Scientist at Adobe Acrobat Android — 1B+ installs, 95M+ MAU, Google Play Billing globally.
What I do
I lead growth, engagement, and monetization engineering for Acrobat Android. My work sits at the intersection of mobile architecture and revenue.
- Payments Payments & subscriptions. I own the Acrobat Android in-app payments stack end-to-end. Most recently I led the cross-product subscription upgrade / downgrade / cross-grade rollout shipped in January 2026 — zero production incidents since launch, and the design has been adopted by other Acrobat apps in the organization.
- Growth Growth engineering. I lead the engagement charter that grew annual subscription retention 35%, and shipped the server-driven paywall surface that delivered a 15% FY24 upsell uplift. I also productionized our on-device ML personalization model for the upsell experience.
- DevEx Mobile DevEx. I build the automations that let our Android organization ship monetization changes weekly — a Figma design linter, an automated release-cherry-pick + Jira workflow, and a weekly executive KPI digest pipeline.
Mentoring engineers earlier in their careers is also a meaningful share of what I do day-to-day.
Open source
Some of what I think about subscription architecture I’m putting into open libraries. Most recent: renew-kt — a deterministic Kotlin state machine for the Google Play Billing subscription lifecycle. See all →
Writing
I write about mobile payments architecture, subscription systems, and Android developer experience. Most recent: The 12×12 cross-grade problem. Previously: Modeling Play Billing subscriptions as a state machine. All posts →
Selective consulting
Outside Adobe, I take a small number of consulting engagements per quarter — mobile payments architecture audits for consumer apps with >100K MAU.
If your subscription stack feels like it has hidden revenue leakage or instability, learn more or say hi.