I recently began working with low-code apps and am not a programmer, but I want to understand the best way to structure my database collections and documents using Firestore. I built an app in AppSheet that has two tables: Artworks and Tags. Each Artwork has 20+ fields associated with it ("columns" in AppSheet terminology), one of which is tags, which refers to another table where each tag has a column that includes a list of the artworks associated with it. This is all well and good and I have it structured in a way that makes sense.
But I'm trying to build an app where many users could store their own artworks and their own tags for each artwork (and look at a particular tag and see all the artworks tagged with that tag). I could achieve this in AppSheet, but not at the scale that I'm thinking of, which is why I'm exploring FlutterFlow.
I already have a Users collection in my Flutterflow app, I've created an Artworks collection (I think), and I've successfully created a few Artworks documents with myself as the user. My question is: what kind of collections and document structure should I have? I feel like I should have Artworks, Users, and Tags as collections, but I know that a noSQL (Flutterflow) database is different from the kinds of databases that AppSheet uses (tables, columns, rows, etc.). Can anyone offer me advice? Should I have a Tags collection (or document? still learning the terms), or should each user have their own artworks and tags documents? Thanks in advance for any pointers you can provide.