Pokémon Go Got 30 Billion Scans for Free. The Growth Play: Make Your Data Collection the Feature, Not the Background Job.

The Play

Pokémon Go has 30 billion real-world location scans.

Niantic did not pay for them.

Players earned in-game rewards — items, XP, Poké Balls — for recording 360-degree videos of real locations through the Wayfarer program.

That data became a Visual Positioning System: a navigation layer that identifies location by matching a live camera feed against a 3D map model, without GPS.

In December 2025, Niantic Spatial announced a partnership with Vantor — a National Geospatial-Intelligence Agency contractor — to use that dataset for military drone navigation in GPS-denied environments.

30 billion scans. Near-zero marginal cost per scan. Enterprise licensing value.

Why this works

Direct payment for crowdsourced data is expensive and does not scale.

In-app rewards have near-zero marginal cost for the product but feel genuinely valuable to motivated users.

That asymmetry is the engine.

Niantic gave players Poké Balls for scanning a landmark. The cost to Niantic: a database row. The cost per billion scans: infrastructure, not incentive payments.

The same mechanic runs across some of the highest-value consumer datasets:

• Waze: Users report traffic incidents for Waze Points and leaderboard status — and that reporting network is why the company was acquired in 2013.
• Duolingo: Users generate translation data and sentence corrections while completing language lessons. The product and the data collection are the same activity.
• reCAPTCHA v2: Users identified fire hydrants and crosswalks to prove they were human. That work trained image recognition models.
• AllTrails: Hikers log routes and elevation data while doing something they were going to do anyway. The dataset now covers millions of trails worldwide.

In every case: the user is doing something they actively want to do. The structured data is the output.

What makes it stick

The reason most apps fail to pull this off is not incentives. It is design.

If the data collection feels like a survey or a background task, users opt out or ignore it.

If it feels like a core game mechanic or a feature with immediate in-app payoff, users do it at scale.

Pokémon Go's scanning feature worked because:

• It was embedded in the core loop of finding Pokéstops and gyms
• The reward was immediate and visible in the same session
• The social layer (Wayfarer community, rating others' submissions) added ongoing participation
• The contribution felt purposeful, not extractive

The design question to ask: "Would a highly engaged user do this even if we gave no reward at all?" If the answer is yes, the reward makes it scale. If the answer is no, you are building a survey, not a feature.

The ethical layer

The Pokémon Go story is trending partly because players did not know their neighborhood scans would end up in military drone navigation software.

The terms permitted it. But the disclosure was not clear.

One Dutch player's reaction when the news broke: "I was just playing a game."

That is a product design failure, not just a legal one.

If you build a crowdsourced data product, design your consent at the product level, not just the legal level. Users who feel deceived churn and talk. Users who understand the value exchange contribute more and refer others.

The bottom line

The most valuable datasets in 2026 were not purchased.

They were designed.

If you are building a consumer app, ask this before writing any collection code:

"What does a power user of this app generate as a natural byproduct of using it — and who would pay to access that at scale?"

That question is worth more than most growth tactics.

Source: https://dronexl.co/2026/06/09/pokemon-go-scans-niantic-vantor-military-drone-navigation/