Virtual List or Standard List for Large Android Datasets?

A Framework7 view is expected to present 5,000–10,000 records on memory-constrained Android devices while keeping scrolling responsive. Assuming Framework7 v8 is the target major release, the unresolved design decision is between the documented Virtual List and Standard List components; the exact Virtual List options and defaults still need confirmation for that release.

Virtual List limits the number of rendered items, but fixed-height and dynamically measured items impose different layout costs. Standard List allows richer nested content and Framework7 components without virtualization-specific setup, while its DOM size grows with the dataset. CPU, WebView version, item complexity, accessibility-tree updates, pull-to-refresh, and infinite-scroll integration may affect the trade-off.

A representative evaluation would compare identical datasets on a mid-tier Android device, measuring memory use, first paint, and scroll smoothness. Which component fits this constraint, and what acceptance thresholds should determine the choice?

If Virtual List is selected, should the design require fixed item heights or permit dynamic measurement and its additional first-render overhead?