Lazy loading

[gsvarovsky]

Lazy loading. Is it needed, and how to represent it? (e.g. like "faults" in CoreData.)

The answer is a solid Yes. App performance is paramount when building apps for iOS. As a developer, I need a way to quickly access a subset of data with minimal impact on the system. One example is the expectation that a native app should be loaded and interactive by the time the launch animation is complete (that is, the animation that "expands" the app from the icon when you tap it on the Home screen). That's under 400ms to load the start screen, get data and render it.
High-performance access is also preferred in cases like collection views (UIKit) or Lists (SwiftUI). Ideally, a developer should avoid implementing or even discovering faults.

How to represent it is an interesting question. My first thought is that it should be transparent, e.g., the library does what it needs to do by default. Some options to customize this can be provided, e.g., to force a query to be loaded on demand.

Originally posted by @kkostov in m-ld/m-ld-spec#97 (comment)