Social interactions and WU

hola10 · 2024-08-03T12:40:00.384Z

Hey bubblers, Jack here, Im a real noob on bubble, been about a month since I started, but starting to feel like Im understanding how Bubble works.

Im about to launch my QR restaurant menu system, that generates QR codes for restaurants to display their menu in a Social Network style app, where customers can comment and like all the dishes.

I have realized that commenting and liking plates consumes LOADS of WU, well…Not loads, about 3 WU per comment and 2WU per Like (about…). If we scale this to 10 restaurants using the app + 300 page loads per restaurant then of course the WU would skyrocket… I am just wondering if I am following the right track for implementing this system, I wonder if there is a cheaper way to achieve this…

Right now, each restaurant is a “user”, each user has a list of “Categories” and each category has a list of “plates”, and finally each plate has a list of “comments” and “likes”.
So when a customer writes a comment, a "New Comment " is created and later “Make changes to Plates” is executed to Add this comment to the plate. Pretty much same thing with likes…

So my question to the community is, am I doing this the best way? Or can you think of a way to achieve this using less resources…

¡Thanks in advance! Jack

hola10 · 2024-08-03T12:45:50.726Z

Captura de pantalla 2024-08-03 a las 13.40.581722×178 9.07 KB

Captura de pantalla 2024-08-03 a las 13.41.53750×932 56.8 KB

georgecollier · 2024-08-03T15:07:35.601Z

You shouldn’t have a list of users that have liked it on the meal, because that will become very long very quickly.

A Like should be a separate data type with a field for Plate.

Comments should not be stored as a list - they should be found using Do a search for Comments where Plate = (the relevant plate)