Rewarded video vs bandwidth: what users really pay

There is no free monetization. Every model charges the user something — the only honest question is what currency. So let's compare the two models app publishers most often weigh against each other, in the currency that matters: what the user gives up.

What rewarded video charges

Rewarded video is the most user-respectful format advertising has produced — it's opt-in, it's transactional, the user knows the deal. Credit where due. But look at what it spends:

• Attention, at peak engagement. The ad plays exactly when the user is most invested — mid-session, wanting the reward. That's the moment your app is at its best, handed to an advertiser.

• Time, in visible chunks. Thirty seconds is a real price paid in the foreground, with the user watching the countdown.

• Session flow. Every placement is an interruption by design. Interruptions compound into churn at the margins.

• Battery and data, in the foreground. Video decode and delivery happen while the user is actively on the device — often on mobile data.

What bandwidth sharing charges

Bandwidth sharing spends a different currency entirely: idle capacity. Under Clearhop's run conditions — Wi-Fi only, charging only, idle only — the cost profile looks like this:

• Attention: none. There is nothing to watch. The user sees one consent dialog, once, and can revoke with one tap.

• Time: none. Sharing happens while the phone charges overnight, not while anyone is playing.

• Battery and mobile data: none by design. Charging-only means battery cost isn't borne by the user's day; Wi-Fi-only means data plans are untouched.

• What it does spend: a capped slice of home internet capacity the user wasn't using, plus the trust the user extends by opting in. That trust is real spend — which is why the dialog has to be honest and the acceptable-use policy public.

The comparison that actually matters

The models don't compete for the same resource. Rewarded video monetizes engagement — it needs the user present. Bandwidth sharing monetizes existence — it needs the user's device to have idle hours. That means:

• High-engagement apps with natural break points (games, especially) get the most out of rewarded video.

• Apps with large audiences but modest session time — utilities, tools, casual apps — leave rewarded video mostly unclicked, but their install base has plenty of idle hours to monetize.

• And for many apps, the right answer is both: the models stack without cannibalizing each other, because they never bill the same moment of the user's life.

One warning, for balance

Bandwidth sharing done wrong — without real consent, without run-condition limits, without a public use policy — charges the user a currency no app can afford: trust destroyed retroactively. If you evaluate any SDK in this category, ours included, the checklist is the same: read the consent dialog, read the use policy, and check what is actually collected. If a vendor makes any of the three hard to find, that's your answer.