← All case studies
Case study

MyJio

Checking your remaining data shouldn't take five taps past ads.

Type
Teardown and feature proposal
Status
Proposal
Platform
Android
Note
Independent, not affiliated with Jio
Problem

Five taps past ads to check your data balance

Proposed

A home-screen widget reading cached data

Rejected

Usage on home screen Daily push alerts

Decides it

>5% adoption, ad views down <8%

01The problem

Today's journey: open the app, tap Mobile, tap Check usage, scroll, read. That's five steps past home-screen ads and a "Rate us" pop-up that appears mid-scroll.

For someone on a daily data plan, this is a number they check several times a day. The friction is small each time and large across a week.

02The proposal

A 4×1 Android home-screen widget. Data left today in large type, plan validity beside it, and a Track usage button that deep-links straight to the usage screen, skipping the ad-heavy home.

When the plan expires, the widget says Recharge needed and the button becomes Recharge now. On Wi-Fi it says so instead of showing mobile data.

It reads the same locally cached data the app already uses for the usage screen, so it needs no new server calls.

03What I rejected, and why

  • Usage on the app's home screenIt competes with the ad inventory that pays for the app. A proposal the business has to say no to isn't a proposal.
  • Daily push alertsNotification fatigue. People mute an app that pings them daily.
  • Better in-app navigationFewer taps still means going past the ads.

04How I'd measure it

Main metric target

> 5%

of eligible Android users add the widget within 14 days.

What moves it
  • Daily app opens fall 10 to 15%, because the widget answers the question
  • Usage-related support tickets fall more than 10%
  • Uninstall rate stays flat
What must not get worse

Ad views drop less than 8%. If they drop more than 15%, or uninstalls rise more than 1%, it doesn't ship.

05Rollout

  • Week 1: 1% of Android users who checked usage three or more times in the past week.
  • Weeks 2 and 3: 10% treatment against 10% control, tracking adoption, app opens and uninstalls.
  • Then full rollout, if the go criteria hold.