Firestore Rules Tagged Users vs Authenticated users with filters

Database & APIs

Hello everyone,
Noobie here. I have read the permission documents. Although they make sense in theory, I have a question of best practice and an issue of understanding why something isn't working.

The basic premise of the app is real estate agents order sign installations through the app.
I have a user collection and a sign installation collection.

1) I initially put
Create: authenticated users
Read: Tagger users
Write: Tagged users

When an installation was created, it added the users UID into the collection as a reference. To me this made sense because now the user would be "tagged". I created a list view and did not put a filter. I figured that it would only show the installations of the logged in user. The installation was created in Firestore, but nothing showed up in the app.

I then changed the Read and write to authenticated users, changed filter to authenticated user on the list view and it worked. Just unsure if this method (which I have seen in many tutorials) is less efficient because it might "download" everything and just filter out whatever it doesn't need and slow down the app. I had this in another app builder called glide and it slowed down the whole app.

I'm also just curious why the other way (tagged users) did not work. Logically it should, as they were tagged.

2) while I'm at it, in the "users" collection, why wouldn't I just keep it at "users collection" instead of "authenticated users". Is it because down the line an admin console account will need permission to see all users? or is it more because some apps like social media apps will need to share things like profile photo, name etc.

What have you tried so far?

filter and without filters

Did you check FlutterFlow's Documentation for this topic?
No
3 replies