Samuel Stern I see. My specific use-case is to show nearby posts, so I don't need accuracy but can work in clusters/chunks with customizable radius, so using geohashes would theoretically work for me. Can't wait for that documentation

See an answer on the "missing functionality for GeoPoint" Firestore issue : For those arriving here, I wouldn't hold your breath. I've been waiting for Geo Queries on Cloud Datastore (which Firestore is pretty much just a new iteration of) for over 5 years now. There are much better geo-native solutions out there if you want to get it done. Anything geo built on top of Firestore / Datastore is a hack at best, and from what I've seen vastly under-performs just picking the right tool the first time. I really wish Google Cloud would give us a nice native option for this though - I mean they certainly do have the tech for it (Google Maps etc.) but they clearly aren't open to sharing that just yet... Really sucks to see that Google isn't doing anything for that in 6 years..

Yes please! 🙏 If Firebase wants to support building real world scalable apps, then full-text-search is a requirement ! I can't think of a big app (Instagram, Facebook, Twitter, ...) without search functionality!

Is geo-search for Firestore on the roadmap? Next to full-text-search , geo-search is a requirement A LOT of apps have, and besides the added complexity of using a third party service (such as Algolia) , they're also VERY expensive. Also, because of this not being integrated into the suite I've been fighting with race conditions a lot, using transactions to mirror my data from Firestore to Algolia - please do something about that! 🙏