Using List of Things vs Own Object – Performance, Usability

Questions
1

Hi!
I am building an app for climbing gyms to document climbing routes and user ratings for every route.
For every route there could be many ratings (one per climber). I want to show the average rating for every route within a repeating group (each line has type Route).
First I build the rating with a reference to the route and did a search for all ratings for each route (per line). This was quite slow on the testenvironment. The list of routes is there but the ratings take some seconds to appear.
Then I had the idea to put the rating as an attribute to the route as a list of things and aggregate the ratings not after a search but as “Current line Route’sRatings…” This works also fine but doesn’t seem to be faster than the first version.

Now my question:
Is there a performance difference since it is not a “Search for…”?
Is there any other difference between the two variants or is more a personal taste because of the different usability in this case?

In my first app I have got already three cases, where I can choose between these two design variants.

Thanks in advance for your answers!

Best regards from Germany
Roman

PS @ Bubble Team: Your service is AWESOME!!! :slight_smile:

2

Hi @Safroman,

I am facing the same exact question. What route did you go eventually? Any feedback?

Thanks,
Jules

3

Hi!
I did some simple tests and could not see any performance difference. It is more a question on design since you have more options with the separate key (change reference) but the other way is faster to build at UI.
I still use both variants depending on the scenario!
Cheers
Roman