Developing for Apple Watch, 2nd Edition

Increasing Performance by Removing Data

One of the examples earlier was loading complicated table data, which is something that can add complexity to an app as the amount of data in the table grows. Delaying until willActivate to load data into the table buys you time, but you still need to load the data at some point. The best and easiest way to make this faster is to simply load fewer rows. Users aren’t going to want to scroll through 10,000 rows on their watches using their finger or the Digital Crown anyway, so capping the total number of rows can go a long way toward making the app responsive. Another technique that can give the appearance of performance is to load part of the data first and then load the rest asynchronously afterward ...