Foursquare's Hypertrending app uses Pilgrim, its SDK used by thousands of apps on millions of phones, to show where people congregate in Austin, in real time
Where 10 Years of Foursquare Has Led Us — It's been 10 years since we launched Foursquare at SXSW in 2009.
Context & Ripple Effects
Hypertrending is a decade-later answer to the question Dennis Crowley posed when he said Foursquare would shift toward making its data useful to other appmakers (that 2016 pivot): after launching the Pilgrim SDK with tiered pricing in 2017, the company now runs its own showcase app on top of it, timed to the tenth anniversary of Foursquare's SXSW debut.
The demo also sets up the harder question the next day's coverage takes up — how a company tracking millions of phones across 100K+ clients like Snapchat and Uber keeps that data from being misused (Foursquare's own explanation of its safeguards) — and it foreshadows an arc that ends with Foursquare sunsetting City Guide in 2024 to concentrate on Swarm.
First-order effects
- Thousands of apps running Pilgrim turn their users' phones into a live census of Austin foot traffic during SXSW, with Foursquare itself as the visible client proving the SDK works at event scale.
- Prospective SDK customers get a reference implementation: Hypertrending demonstrates the real-time congregation product they could build with tiered Pilgrim pricing rather than just read about.
Second-order effects
- The showcase sharpens Foursquare's pitch against any rival selling location intelligence, because a self-run consumer app is more persuasive marketing than documentation alone.
- Real-time crowd visibility invites the privacy scrutiny Foursquare addresses directly in follow-up coverage, making misuse-prevention part of the sales conversation with clients like Snapchat and Uber.
Third-order effects
- If the pattern holds, the consumer app becomes a loss-leader for the data business — consistent with Foursquare later retiring City Guide and consolidating on Swarm while keeping the SDK as the core asset.
- Passive SDK telemetry gathered through third-party apps becomes the industry's default location-data source, displacing first-party check-ins and raising the stakes on how data-rights obligations flow through thousands of embedded clients.
The trend: Location companies are shifting from consumer check-in apps to licensing passive SDK telemetry through other developers, with privacy governance becoming the differentiator.