There have been a lot of good explanations by Jeff about app performance. I wish I had bookmarked some of his posts.
A few ideas.
Data Editor: send only needed data to the user’s device and if possible keep things in Glide
- If possible, use Glide Tables over any other 3rd-party data source (Google Sheets, Excel, Airtable, etc.)
- Avoid Airtable. The amount if troubleshooting and questions in the forum are a good indicator that Airtable is to be avoided. This is my personal view only.
- When appropriate, use Row Owners. Less data will be downloaded to user devices, pages should load more quickly.
- (Relation vs Query. When you set up a Query column, Glide will let you know when using a Relation instead would enhance performance. I wouldn’t worry about this too much, but it’s worth noting that Glide itself has a warning message at times.)
- (Single Self Relations seem best avoided.)
Layout Editor: don’t load too much on a single tab
- Avoid duplicating collections on the same tab yet displaying different information via visibility conditions or sorting.
- Avoid having too many images load on a single tab.
- Performance in the builder and in production on a device can be different: test outside of the builder.