I am considering the option to change my firestore collection structure to include geoquery in my application. geofirestore needs a specific structure :
interface GeoDocument {
g: string;
l: GeoPoint;
d: DocumentData;
}
I know that geofirestore does not allow using where clause to retrieve documents. however, I would like to give the users options to see information based on the location or search ( using standalone queries) in my existing application, I have many queries using different indexes to search in my collection. Can I still be able to use my existing queries and indexes without any performance issues if I use geofirestore document. :
interface GeoDocument {
g: string;
l: GeoPoint;
d: DocumentData;
}
As most applications, you might face performance problems, in case you have a lot of documents and the queries are returning too many of them. In case you have a situation like this, your application might have a performance problem.
In case the searches are individual and you will be expecting specific and not thousands of returns of data, you should be fine. In addition to that, I would recommend you to take a look at this article here, where there are some examples and methods to avoid performance issues.
Let me know if the information helped you!