Most product dashboards treat a pin drop as a decision. We teach Location-Based App Analytics as a craft: how people actually move through districts, malls, BTS corridors, and permission screens — and how to instrument that movement without inventing certainty.
Evening light over the old city. Movement is the product, not the background.
11cohorts taught since 20192,180practitioners through the desk38city datasets used in labs7 wksflagship studio length
From the room
What people say after they ship a location event they trust
The geofence overlap module stopped us from double-counting Rama IX mall visits. We had been celebrating a conversion rate that was really two polygons arguing with each other.
I still wish the indoor telemetry week had a fallback dataset for teams without Wi-Fi probes. We finished the capstone on GPS-only traces and it was slower than advertised — useful, just not as tidy as the syllabus promised.
★★★★☆
Consent-state tracking was the piece we had skipped. After week two we stopped treating “location off” as missing data and started treating it as a segment.
Studio artefact: corridor sketch before any dashboard is opened.
Flagship
District Signal Studio
A seven-week lab for analysts and PMs who already ship an app with location permission and still cannot explain drop-off between “entered zone” and “completed action”. You leave with an event schema, an attribution window that survives sparse GPS, and a capstone on a Bangkok F&B funnel.
Informational seat price from ฿48,900. No checkout on this site.
