When a user enters your app, they should only interact with the rows tied to that app.
There’s a bunch of things that contributes to this, some of them being:
- Try to use relations instead of queries where you can. Queries on large datasets can significantly slow down performance.
- Compress images: Large images take longer to load, especially when you have them on the first tab the user’s going to load when they enter the app.
- Use row owners: This limits the amount of rows the user needs to “download” when they use the app. Less rows = less calculations needed, so it also helps.
A good write up from Jeff here.