Making location easier for developers with new data primitives (Ep. 505)
SPONSORED BY FOURSQUARE
When Foursquare launched in 2009, the app was consumer facing, letting you know where friends had checked in and what spots might appeal to you. People competed to be the “mayor” of certain locations and built guides to their favorite neighborhoods., The service expanded to allow merchants to offer discounts to frequent guests and track foot traffic in and out of the stores. While you can still use the Swarm app to find the best Manhattan in Manhattan, the company realized that real estate and data share the same three key rules: location, location, location.
On this sponsored episode of the podcast, Ben and Ryan talk with Vin Sharma, VP of Engineering at Foursquare, about how they’re finding the atomic data that makes up their location data—their location data—and going from giving insight to individual app users about the locations around them to APIs that serve these location-based insights to developers at organizations like Uber, Nextdoor, and Redfin, who want to build location based insights and features into their own apps.
If you still want to check in at your local bakery and remember all the place you’ll go, the original Foursquare app is now Swarm.
If you’re looking to build on their data instead, you can start with their developer documentation.
They have almost 70 location attributes that they are starting to deconstruct and decompose into fundamental building blocks of their location data. Like data primitives—integers, booleans, etc.—these small bites of data can be remade with agility and at scale.
Through the recent acquisition of Unfolded, Foursquare allows you to visualize and map location data at any scale. Want to see patterns across the country? Zoom out. Want to focus on a square kilometer? Zoom in and watch the data move.
Today’s lifeboat shoutout goes to Rohith Nambiar for their answer to Visual Studio not installed; this is necessary for Windows development.
You can find Vin Sharma on Twitter.
The Stack Overflow blog is committed to publishing interesting articles by developers, for developers. From time to time that means working with companies that are also clients of Stack Overflow’s through our advertising, talent, or teams business. When we publish work from clients, we’ll identify it as Partner Content with tags and by including this disclaimer at the bottom.Tags: api, data primitives, location, partner content, partnercontent, the stack overflow podcast