# Should I use a usage meter or a hard lock to gate a feature?

Source: Lazyweb Research
Published: 2026-07-07
Sample size: n=809
Tags: paywall, upsell, monetization, ux-patterns, mobile, saas
HTML: https://www.lazyweb.com/research/should-i-use-a-usage-meter-or-a-hard-lock-to-gate
Markdown: https://www.lazyweb.com/research/should-i-use-a-usage-meter-or-a-hard-lock-to-gate.md

**Answer.** The market strongly favors hard locks: lock-icon gating appears in 12% of 809 apps (94/809) and unlock CTAs in 20% (159/809), while usage-meter/limit gating is used by only 5% (44/809).[1] Usage gating is also shallow — 44 apps across just 69 screenshots — so it's a specialist tool for consumable value, not a default. Choose a hard lock for discrete features and a meter only when a count of runs/credits is the actual product.

> Hard-lock gating (12% of apps) outnumbers usage-meter gating (5%) roughly 2-to-1 — Lazyweb Research, July 2026.

## Finding

Prevalence across 809 apps:[1]

| Approach | Apps | Share | Screenshots |
|---|---|---|---|
| Unlock CTA (hard unlock) | 159 | 20% | 658 |
| Lock-icon gating (hard lock) | 94 | 12% | 410 |
| Usage-meter / limit gating | 44 | 5% | 69 |

The usage-gating footprint is notably thin — roughly 1.6 screenshots per app — implying it typically shows up as a single 'limit reached' state rather than a pervasive metered experience.[1]

## How to apply

Default to a hard lock (lock icon + unlock CTA) when the gated thing is a discrete, binary feature: an export, a filter, a premium chapter. Use a usage meter only when consumption is inherently countable and the count is part of the value story — credits, generations, daily runs. If you pick a meter, budget for the metering infrastructure and a clear 'limit reached' upsell state; it's a heavier build than a static lock for a reason few apps take it on.

## Caveats

Usage-gating prevalence (44 apps / 69 screenshots) is flagged thin — treat it as directional and avoid per-category cuts.[1] All figures are company-deduped lower bounds from tightened LLM tags; raw %usage% was rejected for data-usage-disclosure false positives.[1]

## The numbers

| Stat | Computed from |
| --- | --- |
| 12% (94/809), 410 screenshots | lock_icon_gating_prevalence: 94/809 |
| 20% (159/809), 658 screenshots | unlock_cta_prevalence: 159/809 |
| 5% (44/809), 69 screenshots | usage_meter_limit_gating_prevalence: 44/809 |

## Methodology

Universe: 809 tracked mobile apps with 44,873 tagged screenshots. Method: app-count prevalence (COUNT DISTINCT company) over tightened LLM synonym tag patterns, July 2026. Caveat: tag-based prevalence is a lower bound; raw single-word patterns (%lock%, %usage%, %blur%) were rejected for security/media/data-usage false positives.

## Sources & citations

- [1] Lazyweb Research analysis of 809 apps (tracked mobile app corpus with screenshots), July 2026. Prevalence deduped by COUNT(DISTINCT company_name) over 44,873 tagged screenshots; tag patterns are LLM synonym phrases (tightened after spot-checking) so every stat is a lower bound.

## Related questions

- [Lock icons, blurred previews, or usage limits: how do apps gate features?](https://www.lazyweb.com/research/how-apps-gate-features-lock-icons-vs-usage-limits)
- [Where do freemium apps place upgrade prompts inside the product?](https://www.lazyweb.com/research/where-freemium-apps-place-in-product-upgrade-prompts)