Interaction comes before speculative loading
FLEX distinguishes work needed for an interaction from lower-priority preparation. Loading concurrency and optional prefetch are bounded, rather than creating an unlimited set of background requests.
Resolved resource plans use bounded caches. Lifecycle handling focuses on changed page regions where possible, avoiding repeated work over every unchanged field after a local update. Factory registration tracks implementation identities rather than silently wrapping the same factory again.
These optimizations concern resource and initialization work. They do not make an unbounded SQL query or a full-resolution preview cheap.
Virtualization limits rendered rows. Pagination limits fetched results. Use both when your dataset calls for them:
This demonstration crosses the threshold and uses string identifiers suitable for a text attribute. It still supplies all 500 options. For large database or remote catalogs, use Select’s paginated provider with scoped search instead of fetching everything first.
Use the right image for a preview
Configure a named image conversion, then select it for previews. Selecting the preview alone does not create the conversion:
The thumb conversion must exist in your native image configuration or Spatie model configuration. Local preview generation and persisted preview selection are separate settings; see image previews.
If processing is queued, run the configured worker. Native and Spatie conversions retain the original, and a missing or pending conversion follows the chosen preview/fallback behavior.
Continue reading
Asset Manager overview · Resource sharing · Activation & cleanup · Performance · Publish & diagnoseLast modified on October 16, 2026
