@b.ramzi – I personally would avoid the long lists. A few things to think about, based on my understand of how Bubble works…
- Bubble server-side searches which are straightforward are very fast and scalable. Also, Bubble will index data so that it can find the relevant data faster.
- If you have a list of 10,000 items attached to the user, then the uniqueid’s for all 10,000 records will be downloaded to a page whenever you access information from that user record. That’s a lot of downloading taking place and on-page memory being used.
- In addition (I’m pretty sure I read this)… if you have to do any sort of filtering or sorting of those 10,000 records that you are working with via the user list field, it happens client-side (on the browser), meaning that Bubble will have to download ALL of the data associated with each record until it finds enough results to fill whatever RG container you have. That can lead to some serious, app-killing slowdowns.
- This is all on top of problems that massive list fields like this would cause if you ever needed to search and display user records.
A couple of resources that go into a lot more detail…
Alternative approach to the Bubble’s recent tutorials for list of things - Tips - Bubble Forum