Before You Build
Mobile AppShut Down

Gowalla

Gowalla was a location-based social app built around check-ins and sharing real-world activity. Its original service shows that social location novelty, press, and acquisition interest still need a durable repeat-use loop and network-density advantage.

View original story

Product snapshot

What it was

Gowalla let users check in at real-world places and share location-linked activity with friends.

Who it was for

Mobile social app usersPeople exploring local placesFriend groups coordinating around real-world locationsFans of check-in and location-sharing mechanics

Problem / value

It turned local presence and exploration into a social, playful mobile experience.

Core workflow

A user opened the app at a place, checked in, and shared that location-linked activity with friends or the network.

Core dependency

The model depended on frequent check-in behavior, friend-network density, differentiated local value, and a reason to keep using it beyond launch novelty.

Product form

iOS and mobile social appLocation-based social networkCheck-in serviceLocal discovery experience

Pricing model

No durable consumer revenue model is disclosed in the public shutdown sources.

Competitors or alternatives

FoursquareFacebook Places and Facebook location featuresOther check-in appsLocal discovery appsBuilt-in social graph location sharing

What happened

Summary

Facebook acquired Gowalla in 2011 and the original standalone service was terminated, making it a useful case about location-social retention, network density, and incumbent-platform pressure.

Outcome

The original Gowalla service shut down after the Facebook acquisition.

Core risk

Location-sharing novelty and acquisition interest did not prove that the standalone product had a durable, differentiated, high-frequency use case against larger social platforms.

Timeline

  • Gowalla launched around the early smartphone location-social wave.
  • It competed with Foursquare and other location-based social products.
  • In 2011, Facebook acquired Gowalla and team members joined Facebook.
  • The standalone service was scheduled to terminate after acquisition, with user export available and user data excluded from the transaction.
  • Later reporting covered a Gowalla relaunch, so the case concerns the original service and business trajectory.

Before you build

Why it matters

Social and local products often look obvious because everyone goes places. The hard part is proving that enough people repeatedly share those places in the same network and that the behavior remains valuable after novelty fades.

Primary check

Before building a location-based social app, community check-in product, or local discovery network, prove repeated behavior in ordinary weeks, differentiated value versus incumbent social graphs, and density in one market before scaling.

Checklist

  • Track weekly repeat check-ins by cohort.
  • Measure friend-response rate after check-ins.
  • Run one-market density tests before broad launch.
  • Compare event-week usage with normal-week usage.
  • Test whether users return without rewards or push prompts.
  • Do users repeat the location behavior in normal weeks?
  • Is there one city or community with real density?
  • What does the product do that incumbent social graphs cannot copy quickly?
  • Does the product still work without badges, events, or launch buzz?
  • Is there a monetization path that does not weaken trust or frequency?

Relevant if

  • You are building a location-based social app, check-in product, local discovery network, map community, or offline-community tool.
  • Your product depends on friends using it in the same places.
  • You are relying on events, novelty, press, or acquisition interest as validation.

Less relevant if

  • Your product is a utility with clear individual value without a social graph.
  • You already own a dense local community or distribution channel.

Pre-build tests

  • One-neighborhood check-in pilot
  • Private group location-sharing test
  • Event versus ordinary-week retention comparison
  • Manual local discovery cohort test

Transferable lessons

  • Measure normal-week retention, not only event or launch usage.
  • Validate one dense geography or subculture before broad expansion.
  • Define the job beyond sharing where someone is.
  • Assume incumbent social platforms can copy simple location features.
  • Separate acquisition interest from standalone product sustainability.